Root Domain 403ing, but other domains working

46 views
Skip to first unread message

Brandon Wirtz

unread,
Aug 12, 2018, 2:46:29 PM8/12/18
to Google App Engine
As of about 3 days ago, my w34.us domain started 403ing on Appengine. Other root domains linked to the same app work, and www.w34.us works. 

I checked the DNS settings and they match what Google tells me to use, and the fact that it makes it to the 403 with a Google Error implies it is not a DNS issue.

The domain is mapped in App Engine, as root, and www, and the settings match other domains that point to that App.

Because it is a .US domain I feel like it is something related to that, (or because it is only 6 characters?) 

Any suggestions?

Jordan (Cloud Platform Support)

unread,
Aug 13, 2018, 9:02:19 PM8/13/18
to Google App Engine
I am seeing a 404 Not Found for a GET request to your domain. This means that your App Engine service that is serving your custom domain does not have a handler configured to serve that exact GET request.  It is recommended to follow the documentation to ensure that your code is properly configured to serve that type of request.  Also ensure that you do not have a dispatch.yaml redirecting requests to a different service. 

- Note that Google Groups is reserved for general product discussions and is not for technical support. For further support in getting your application to serve at your domain, it is recommended to post your detailed questions to Stack Exchange using the supported Cloud tags. 

Brandon Wirtz

unread,
Aug 15, 2018, 1:20:45 PM8/15/18
to Google App Engine
Error changed sometime after posting.

Nothing in the code/routes points to the specific domain. Also no code changes were made when the issue occurred.

Lastly, it has worked intermittently in the past 24 hours as traffic was logged. 

Stack exchange sent me here, as "this was a General question about the service not my configuration" 

Jordan (Cloud Platform Support)

unread,
Aug 15, 2018, 2:48:13 PM8/15/18
to Google App Engine
Looking at your CNAME and A record configuration for your domains, they do indeed look to be correct as you originally mentioned. The domain length or the top-level domain '.us' should not be an issue since your 'www.' subdomain is working. 

http://w34.us is always returning a 404 for me and never works. I am not able to see your logs so I cannot confirm what you are seeing unfortunately. But since www.w34.us works and http://w34.us does not, this points highly to the configuration of your actual web service code as mentioned above. 

I am not sure why someone on Stack Exchange routed you back here since this forum is not for technical support, but you can find similar issues to this on Stack Exchange which were fixed via proper web server code configuration. It is therefore recommended to provide further details about your actual code setup on Stack Exchange in order to follow their best practices for receiving the best technical help. 
Reply all
Reply to author
Forward
0 new messages