Your data. Anywhere you go.

New Relic for iOS or Android


Download on the App Store    Android App on Google play


New Relic Insights App for iOS


Download on the App Store


Learn more

Close icon

How to whitelist Synthetics to get around Captcha


#1

Hello,

We’ve whitelisted the following IPs so we can bypass Captcha for one of our tests:
“Washington, DC, USA” : [ “34.224.255.169”, “34.201.89.115”, “52.44.71.247”, “35.168.185.185”, “35.168.141.9”, “52.21.22.43” ], Our test is setup to use the Washington DC datacenter.

(We pulled the list from:https://s3.amazonaws.com/nr-synthetics-assets/nat-ip-dnsname/production/ip.json)

However when we’re setting up the test, when we preview in the “Script your steps” we see the Captcha widget. Do we need to whitelist an additional set of IPs? ie. even though we selected the Washington DC datacenter, maybe the “Script your steps” is actually originating from a different datacenter?

Thanks.


#2

Hi @justin34, this looks like the full list of IP’s for the Washington location so that should not be an issue. When validating the script during that step it will actually run from one of the locations you have checked in the previous settings menu, so if you have only selected Washington DC the validation test will run from there. Would you mind sharing a permalink to the monitor so I can take a closer look? :slight_smile:


#3

Sure thing:
https://rpm.newrelic.com/accounts/1417463/applications/48933931?tw[end]=1568112502&tw[start]=1568101702


#4

@justin34 thanks, this looks like a link to an APM application rather than a Synthetics monitor, could you share the link to the monitor you are having issues with? :slight_smile:


#5

Oops - https://synthetics.newrelic.com/accounts/1417463/monitors/504c15e5-836b-42bc-963a-60fb3eebdc4c?tw[start]=1568228197.257&tw[end]=1568229997.257


#6

@justin34

Thanks for sharing that monitor link and letting us confirm that just the Washington, DC. The IPs you shared earlier from https://s3.amazonaws.com/nr-synthetics-assets/nat-ip-dnsname/production/ip.json are indeed the only IPs you’ll need to whitelist.

Although I wont be able to assist with configuring the whitelisting you are attempting here, I found another post where someone was attempting a similar strategy with a PHP based web application, which it appears the one you are monitoring may also be:

It seems they ran into some trouble initially but were able to figure it out, it might be worth reaching out to that thread to see what solution they came to.