Hey Folks, If anybody could capture the requests and response of a consistently-failing link (what Evan has said about certificates, HTTPS and static file paths is interesting) using wireshark <https://www.wireshark.org/>, using HAR capture <https://toolbox.googleapps.com/apps/har_analyzer/> from the browser, or using curl <https://curl.haxx.se/> with the -v (verbose) flag set, this information could be included in a Public Issue Tracker <https://code.google.com/p/googleappengine/issues/list> report which might allow us to look deeper into whether something we could fix might be involved.
Feel free to let me know if you have any questions about this! We're here to help. Cheers, Nick Cloud Platform Community Support On Friday, October 28, 2016 at 5:09:57 PM UTC-4, Evan Jones wrote: > > Sorry I should clarify: We have a slightly different symptom. Our affected > customer gets timeouts connecting to https://(projectid). > appspot.com/(static path), but it works fine if they use HTTP. > > > > On Friday, October 28, 2016 at 5:09:21 PM UTC-4, Evan Jones wrote: >> >> Funny, I've been dealing with the same issue this week. We have a >> customer who is on their corporate network, and they cannot access our >> static resources if they use https://(projectid).appspot.com. If they >> use HTTP, or our domain alias (https://www.bluecore.com/) it works. I >> haven't been able to track down the cause, but there are minor certificate, >> DNS and IP differences between *.appspot.com and ghs.googlehosted.com. >> >> This is a long winded way of saying: I've run into similar issues, I >> don't know how to fix them, but try plain HTTP or a domain alias as >> potential workarounds. Good luck, and if you figure out anything, please >> let me know. >> >> >> >> On Friday, October 28, 2016 at 3:08:41 PM UTC-4, Nick (Cloud Platform >> Support) wrote: >>> >>> Hey xBy, >>> >>> This issue is a bit difficult to comment on in the abstract. There could >>> be many reasons why a network link would experience failure. The best >>> advice I can give is to use traceroute >>> <https://en.wikipedia.org/wiki/Traceroute> or mtr >>> <https://en.wikipedia.org/wiki/MTR_(software)> from their machines to >>> the machine they wanted to connect to and this might help diagnose the >>> network issue. >>> >>> Cheers, >>> >>> Nick >>> >>> >>> On Monday, October 24, 2016 at 9:32:40 AM UTC-4, xBy Tez wrote: >>>> >>>> Hi everyone, >>>> >>>> Lately I've noticed that some of our clients email us saying they are >>>> unable to connect to our Google App Engine domain. (It's CNAMEd to >>>> ghs.googlehosted.com) >>>> >>>> This seems to happen for Russian people. Some will get a 403 Forbidden. >>>> >>>> "Your client does not have permission to get URL (...) from this >>>> server. " is the error message they will get. >>>> >>>> Another Russian customer got "ERR::CONNECTION_RESET" errors when trying >>>> to access our GAE domain. >>>> >>>> What should we do in order to resolve this and make this page available >>>> for everyone? >>>> >>>> -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/3465136b-36ac-401f-8f30-1a8a155167df%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
