Google Cloud Platform renewed SSL cert stops app from serving - google-app-engine

Our GAE app has been serving from a custom domain for a year, using a GoDaddy SSL certificate that we uploaded a year ago. A few days ago they sent me an email saying we needed to renew it, so I did, and then I received an email on how to download it. They offered various server type choices, and since none were GAE, I chose "Other".
Next I tried to follow the instructions at https://cloud.google.com/appengine/docs/python/console/using-custom-domains-and-ssl#obtaining_a_certificate, the section "Obtaining a Certificate". (I started with https://www.digicert.com/ssl-certificate-installation-google-app-engine.htm, but that seemed useless to me because I have a Mac, not a PC).
The instructions under "Obtaining a Certificate" don't explicitly describe renewal. I was pretty sure I shouldn't create a new CSR, since I have to assume the renewal cert used my old CSR given that GoDaddy didn't ask for a new CSR. But I had saved the files from a year ago when I obtained the original cert.
So jumping to step 5, I proceeded as follows:
I unzipped the renewal certificate ZIP file I had obtained from GoDaddy.
I had already done step 6 a year ago and still had that file, so I skipped step 6.
I concatenated the CRT files from the renewal cert that had been inside the ZIP file.
I went to the "SSL" link in step 7. On that page:
I used the "Upload a new certificate" link, sending the two required files.
I tried pointing my browser to the domain, and it returned a warning page that that page was unsafe because the certificate was out of date.
So I deleted the old certificate.
Again I tried going to my domain, and now I'm getting a page that says "This webpage is not available." Presumably all the users of my app are getting that as well. :0(
I also used the "To verify that the private key and certificate match..." steps under "Obtaining a Certificate" and the two hex values matched.
I've tried a variety of online searches without finding anything that addresses my issue. I'm sorry if it's out there, but I couldn't find it. Anyone know how I can get my app serving again?

The solution was given in step 6 of a different section on the same page of my first link. After I had done everything else I described above, I still needed to do the following:
Click the name of the new certificate, which takes you to a new page.
Click the name of the domain.
Click Save.
None of this info appears on the SSL page, and the name you assigned to the uploaded certificate doesn't look like a link, but it is.

Related

Notes Federated Login not downloading in memory ID file - Entry not found in index

We have setup Notes federated login to provide a single-signon for Notes clients from Active directory. and there seem to be a problem when getting the "in memory" ID file from the Vault.
Here is the scenario
User start Notes (tried both v9 and V10) for the first time
Enter password in the Login screen for the local id file.
Message prompt "ID file is now downloaded for Notes Federated Login"
User click "OK" and a new message show up "Server Error - Entry not in index"
User click "OK" and then the passsword prompt for the local id file is displayed.
So, in short there seem to be a problem when downloading from the Vault but the error message do not really say much.
We have enabled all the client debug options and checked the server logs but nothing really tells us what is wrong.
All we get is this:
An issue that failed to authenticate was reported from the server / domain server: Entry not in index
Id-file is already in use and can't be changed
I can't diagnose the issue from reading your problem description. I suggest you open a support ticket with the steps to reproduce. ERR_NOT_FOUND (not found in index) is a very common return value in Domino, often even being benign. But in the benign cases it is handled by the calling code.
So it's hard to know what method/function threw the error or what the stack was at the time. Hence the advice to open a support ticket.

GAE Delete Domain Mapping not working

I have an old AppEngine project which is mapped to my domain. I recently transferred this domain to Google Domains.
I created a new AppEngine project which I now want to map to my domain instead of the old project. When I attempt to do so I get the error "my-domain-name is already mapped to a project." That makes sense.
However, when I attempt to delete the mapping from my old project (console.cloud.google.com/appengine/settings/domains?project=my-old-project-name) I get an error:
"Error
Sorry, there’s a problem. If you entered information, check it and try again. Otherwise, the problem might clear up on its own, so check back later.
Tracking Number: xxxxxxx
Send feedback
"
I've tried this several times so this is for sure not clearing up on its own. (I've also tried sending feedback but not gotten any reply)
Any idea on how I can move the mapping from my old AppEngine project to the new AppEngine project?

Verifying a domain for Google App Engine

We're having trouble verifying our domain for our Google App Engine application.
We have a domain registered with Hostek, where our name servers are currently:
ns-cloud-c1.googledomains.com
ns-cloud-c2.googledomains.com
ns-cloud-c3.googledomains.com
ns-cloud-c4.googledomains.com
I created a DNS zone in Google Cloud and added the TXT record with the value given to me by Google App Engine, but when click "Verify" on the Google side, I get the error
Verification failed for cbcdashboard.com using the DNS TXT record method (less than a minute ago). We couldn't find the verification token in your domain's TXT records. You might need to wait a few minutes before Google sees your changes to the TXT records.
Below that, if I click "Show found DNS TXT records", I see
google-site-verification=<the token I was given>
It seems to see the value, but to not think it's correct. I tried adding it with and without quotes. Any ideas?
I just did a dig and got this:
"google-site-verification=PDmOnhweMP0C1aXpkNh-4kG-Mlhg3o22viWjGm_gn3U"
So it seems like that it's a propagation issue. When you make changes to DNS it does not spread out on the DNS for a while. If you try again to verify does it now work?

Why is my website still not working with HTTPS?

I have been following the steps in Adding SSL to your custom domain but I am not seeing any changes yet. My website is still running with HTTP only.
I have entered all DNS information under Custom domains and I have a valid my-cert-1 under SSL Certificates but my site is not getting loaded if I go to https://www.my-unsecure-website.com
What could I be missing?
I have verified that I own this domain weeks ago, so it cannot be that I just have to wait 24 hours.
The process is really simple. Verify that you own the domain, upload your SSL certificate and assign a certificate to that domain.
Generally people miss the process of assigning certificate. Make sure to follow step 5 (documentation).

How make the Google Cloud Storage Bucket as a static-website Visible With and Without www?

Hello to everybody after all correct configurations as I followed at the "Documentation of Google Cloud Storage - Configuring a Bucket as a Static Website" my bucket it work as a website but the problem is about the prefix WWW in fact when I visit the bucket http://www.pieropretti.net I can see the content of the public bucket, but if I visit (from the browser Chromium version 42.0.2281.0 (64-bit) and same problem from the browser FirefoxESR 31.4.0 (Tor Browser 4.0.3) without the prefix WWW I receive the error server not found. This is the screenshot of the domain name DNS configuration in the picture here http://tinyurl.com/ncoc9y5
"www.pieropretti.net" and "pieropretti.net" are different domain names, and thus also correspond with different buckets. If you want to serve content from "pieropretti.net", you will need to create a bucket named exactly "pieropretti.net" in the same way you created the "www.pieropretti.net" bucket.
From what I can see, the DNS setting for "pieropretti.net." doesn't seem to have a CNAME, despite what your panel is telling you. Perhaps it just hasn't propagated to me yet.
From DNS records I notice that you are on OVH, if it is you can use the OVH Redirection Technology to redirect from naked to WWW.
If you are on other maintainers don't worry all offers service like OVH for redirect the naked to the www.
For top-level domain name we can't add CNAME, we can add A record, so I goto my Terminal and ping c.storage.googleapi.com to get the IP address, then I use the IP address to add into the A record, it works for me, just not sure whether it's an appropriate way to do it this way or not, but it just works for me.

Resources