Incorrect Geolocation lookup resulting in 403 errors
69 views
Skip to first unread message
Cody Rowland
Oct 27, 2015, 12:50:39 PM10/27/15
to Google App Engine
Hello,
We have a WordPress plugin that makes an API call to App Engine and a few days ago we started getting reports that a handful of customers were receiving Forbidden errors. After looking into the issue we discovered that all of the affected customers use InMotion Hosting and that all of the affected systems were connecting to App Engine from a specific block of IP addresses managed by InMotion: 198.46.80.0/20. According to InMotion support all of the affected servers are physically located in the greater Los Angeles area.
When we run a curl that makes a simple api call from one of the servers having issues this is the response we get. Note: I've highlighted the text that makes me believe this might be a geolocation error of some kind:
Am I on the right track in thinking this is a geolocation issue of some kind? If so, how can we resolve it? Any help or guidance you can provide would be greatly appreciated!
Thank you,
Cody Rowland
Technical Support Specialist
LeadPages.net
We have a WordPress plugin that makes an API call to App Engine and a few days ago we started getting reports that a handful of customers were receiving Forbidden errors. After looking into the issue we discovered that all of the affected customers use InMotion Hosting and that all of the affected systems were connecting to App Engine from a specific block of IP addresses managed by InMotion: 198.46.80.0/20. According to InMotion support all of the affected servers are physically located in the greater Los Angeles area.
When we run a curl that makes a simple api call from one of the servers having issues this is the response we get. Note: I've highlighted the text that makes me believe this might be a geolocation error of some kind:
* About to connect() to my.leadpages.net port 443 (#0)
* Trying 72.14.249.204... connected
* Connected to my.leadpages.net (72.14.249.204) port 443 (#0)
* Initializing NSS with certpath: sql:/etc/pki/nssdb
* CAfile: /etc/pki/tls/certs/ca-bundle.crt
CApath: none
* SSL connection using TLS_RSA_WITH_RC4_128_SHA
* Server certificate:
* subject: CN=*.leadpages.net,OU=IT,O="Avenue 81, Inc.",L=Minneapolis,ST=Minnesota,C=US
* start date: Nov 07 00:00:00 2014 GMT
* expire date: Apr 11 23:59:59 2016 GMT
* common name: *.leadpages.net
* issuer: CN=Symantec Class 3 Secure Server CA - G4,OU=Symantec Trust Network,O=Symantec Corporation,C=US
> POST /api/ HTTP/1.1
> User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.19.1 Basic ECC zlib/1.2.3 libidn/1.18 libssh2/1.4.2
> Host: my.leadpages.net
> Accept: */*
> Content-Length: 80
> Content-Type: application/x-www-form-urlencoded
>
} [data not shown]
< HTTP/1.1 403 Forbidden
< Date: Wed, 21 Oct 2015 17:45:08 GMT
< Content-Type: text/html
< Server: Google Frontend
< Content-Length: 2046
< Alt-Svc: quic=":443"; p="1"; ma=604800
<
{ [data not shown]
* Connection #0 to host my.leadpages.net left intact
* Closing connection #0
<!DOCTYPE html><html lang=en><meta charset=utf-8><meta name=viewport content="initial-scale=1, minimum-scale=1, width=device-width"><title>Error 403 (Forbidden)!!1</title><style>*{margin:0;padding:0}html,code{font:15px/22px arial,sans-serif}html{background:#fff;color:#222;padding:15px}body{margin:7% auto 0;max-width:390px;min-height:180px;padding:30px 0 15px}* > body{background:url(//www.google.com/images/errors/robot.png) 100% 5px no-repeat;padding-right:205px}p{margin:11px 0 22px;overflow:hidden}ins{color:#777;text-decoration:none}a img{border:0}@media screen and (max-width:772px){body{background:none;margin-top:0;max-width:none;padding-right:0}}#logo{background:url(//www.google.com/images/errors/logo_sm_2.png) no-repeat}@media only screen and (min-resolution:192dpi){#logo{background:url(//www.google.com/images/errors/logo_sm_2_hr.png) no-repeat 0% 0%/100% 100%;-moz-border-image:url(//www.google.com/images/errors/logo_sm_2_hr.png) 0}}@media only screen and (-webkit-min-device-pixel-ratio:2){#logo{background:url(//www.google.com/images/errors/logo_sm_2_hr.png) no-repeat;-webkit-background-size:100% 100%}}#logo{display:inline-block;height:55px;width:150px}</style><a href=//www.google.com/><span id=logo aria-label=Google></span></a><p><b>403.</b> <ins>That’s an error.</ins><p>Your client does not have permission to get URL <code>/api/</code> from this server. (Client IP address: 198.46.81.10)<br><br>
We're sorry, but this service is not available in your country.
<ins>That’s all we know.</ins>
Am I on the right track in thinking this is a geolocation issue of some kind? If so, how can we resolve it? Any help or guidance you can provide would be greatly appreciated!
Thank you,
Cody Rowland
Technical Support Specialist
LeadPages.net
Nick (Cloud Platform Support)
Oct 27, 2015, 6:02:08 PM10/27/15
to Google App Engine
This sounds like an issue which should be reported to the Public Issue Tracker as "type-production", since it affects specifically your deployment and needs a close look by engineers. Feel free to make a posting and it'll be triaged quite quickly.
Cody Rowland
Oct 27, 2015, 6:16:31 PM10/27/15
to Google App Engine
Thank you very much Nick! I appreciate the assist.
Reply all
Reply to author
Forward
0 new messages