Can't fetch sourcemaps - wrong ip ranges?

1

Hi,

I’m deploying my sourcemaps to S3 and I set a policy (according with https://docs.sentry.io/ip-ranges/) to allow sentry IPs to correctly fetch the sourcemaps.

Issue is: looks like it does not work, however I granted others IP in the policy, so I’m sure that my policy rule is not wrong.

Did sentry change IP ranges ?

2

It’s possible that we’ve outgrown and the range needs to be updated.

Can you provide the config you’re using? I’ll check today if the range has changed.

3

I took the IP ranges from this page: https://docs.sentry.io/ip-ranges/

{
	"Version": "2012-10-17",
	"Id": "PolicyId2",
	"Statement": [
		{
			"Sid": "AllowIPmix",
			"Effect": "Deny",
			"Principal": "*",
			"Action": "s3:*",
			"Resource": "arn:aws:s3:::my-sourcemaps-repo/*",
			"Condition": {
				"NotIpAddress": {
					"aws:SourceIp": [
						"169.53.228.176/28",
						"173.193.138.208/28",
						"173.193.154.224/27",
						"208.101.49.96/27",
						"208.43.20.192/27",
						"67.228.250.96/29",
						"75.126.189.224/28",
						"75.126.194.48/28"
					]
				}
			}
		}
	]
}
5

Hey Matt,

news about this?

6

Oops, sorry, we’ve updated that page with our latest IP ranges.

1 Like
7

@matt I don’t see sentry making requests for the .map files…
Even when they are absolute urls:

//# sourceMappingURL=http://www.stackshirts.com/static/js/main.0507b600.chunk.js.map
8

@matt I still don’t see sentry requesting sourcemap files in my logs… any chance you don’t make them if the initial request fails?

9

Actually I am seeing requests from two ips that aren’t on your list:
34.68.183.85
35.223.158.218

Any idea why?