I've followed the steps on https://cloud.google.com/appengine/docs/ssl and https://support.google.com/a/answer/2644334. I have a custom domain, have correctly uploaded the certificate. Everything seemed to be working, but then an hour later every https: connection fails with ERR_CONNECTION_CLOSED (in Chrome). How can I debug this?
My www CNAME record is ghs.googlehosted.com
I'm accessing the site via the www subdomain https://www.example.com
Google Apps shows as serving SNI only for the assigned url www.example.com
Billing is enabled
www.example.com is set as a custom domain in cloud console
http://www.example.com works fine
https://app-engine-id.appspot.com works fine (but I think this is irrelevant)
there are no errors in cloud console logs
Related
Okay So I am trying to host a react application with Heroku using a Godaddy domain
I am facing 3 Issues
Issue 1: Site is not secure when visited through some address.
Here are the different addresses
https://www.example.com This is SECURE.
www.example.com This is NOT SECURE. And on safari browser does not put https in front of it automatically.
Issue 2: : Forwarding the following domains to main domain: https://www.example.com
http://example.com
http://www.example.com
example.com
www.example.com
https://example.com
Issue 3: After setting up the forwarding in the steps above, the pages with addresses like example.com/getstarted does not get forwarded to https://www.example.com/getstarted
I have looked at all the solutions currently available on Docs as well hundreds of stackoverflow posts.
I have a CNAME set up as www to the example.herokudns.com
I also have a forwarding setup in godaddy to permanently forward example.com to https://www.example.com
I am also using ACM (Automatic Cert Manager) SSL in Heroku (Paid Version)
Any advice is welcome and fast please.
I am having trouble mapping the Google App Engine with Google Domains. I have a domain registered, let's call it example.com. What I want to achieve is both example.com and www.example.com can access the web application I deployed on Google App Engine. Also, I would like urls starting with either http:// or https:// able to visit the web application as well.
Therefore, there are four different urls I need to take care of: 1. http://example.com, 2. http://www.example.com, 3: http://example.com, 4. https://www.example.com.
What I have done is verify example.com and www.example.com on the Google App engine, obtained the records, then added the A, AAAA, and CNAME record to the Custom resource records in Google domains. After that, I use the Synthetic records on Google Domains to forward the subdomain #.example.com to https://www.example.com with SSL enabled, so I thought it should take care of the four cases I mentioned above.
However, after all thoses steps, the A and AAAA records are move from the custom resource records to the synthetic record. Recently, I am experiencing bugs in which webpages cannot be opened on the https:// url but are able to open on the http:// url.
I wonder if my subdomain forwarding is causing the issue I am seeing? If so, ow should I map all 4 urls to the web-application on Google App Engine and redirect them to the https://www.example.com?
Map 'example.com' to your app engine domain. Enable the free SSL certificate from app engine
Map 'www.example.com' to your app engine domain. Enable the free SSL certificate from app engine
In your app.yaml file, set the attribute for 'secure' to always. This means that when a user types in 'http//example.com', they will automatically get redirected to 'https://example.com'. This means you don't have to do anything extra on your end (i.e. no need for any forwarding)
Note that with the above setting, you will still end up with 2 sets of urls - the naked domain https://example.com and the subdomain - https://www.example.com. It is good practice to have only 1 set i.e. either forward all naked to the sub or vice versa. You can do it at the domain registration point or have your code do it (in your app).
I have had a custom domain pointing to my appengine app for a long while now. Today the naked domain stoped working (get google's 404 page). ie mydomain.com no longer works where as www.mydomain.com works. DNS entries are correct ( I have multiple domains attached to the same appengine app and they all work except for one).
I have the following scenario:
Website is hosted in AppEngine and we want to force it to always load in https. (we use secure:always in app.yaml)
Domain is managed in Google Apps. We have uploaded SNI certificate and all looks good
In Google Apps we set the redirect of the naked domain to the www version of it
The following URLs all work:
http:// website.com (redirects to https:// www.website.com)
http:// www.website.com (redirects to https:// www.website.com)
https:// www.website.com (the URL of the app)
However this URL does not redirect and gives an error:
https:// website.com
Is this a bug or is this a settings issue?
As it is right now, SSL for naked domains does not work directly and this is an expected behavior. This is being tracked as issue 10802. Also, have a look at this question, where they found a workaround to use Naked domains and SSL through Google Apps. An alternative solution is proposed here.
Is it possible to point a domain to my custom domain?
domain1.com --> myapp.com --> myapp.appspot.com
domain2.com --> myapp.com --> myapp.appspot.com
I successfully pointed www.myapp.com to myapp.appspot.com
creating a CNAME and and pointing it to ghs.google.com
Google will redirect a bare domain for you, it's described at http://support.google.com/a/bin/answer.py?hl=en&answer=2518373.
In this case, mydomain.com would have an A record pointing to a Google IP address, and requests for http://mydomain.com delivered to that IP address would get an HTTP response redirecting the browser to http://www.mydomain.com by Google; www.mydomain.com would have a CNAME DNS entry that points to ghs.google.com; user requests arriving there are routed based on their Host: header to App Engine and then to an instance of your app. The user would see "www.mydomain.com" in their address bar.
I don't know if I fully understand your explanation of the two domains, but if you want users who try to go to http://myotherdomain.com to end up at the app, as well, you should be able to do this with a Google Apps domain alias: add myotherdomain.com as a domain alias for mydomain.com and repeat the steps to get the naked domain redirected and www.myotherdomain.com to go to ghs.google.com, and you can make your app available on www.myotherdomain.com.
I just discovered today (as of 2014-04-11) a new custom domain settings page is available from Google Developers Console:
Go to https://console.developers.google.com/project
Click on your project
On the left click "App Engine"
Click "Settings"
There you go! You can configure custom domain without the need of Google App account!