2

Three days ago, I was able to access my website deployed onto Google App Engine with no issues. Since that time I haven't changed anything in the files for my project, but when I deployed recently I was given a site can't provide a secure connection error, and the website was sent an invalid response.

I'm not sure whether this is an issue on App Engine or my code, as this only occurs with the most recently deployed instance of the website on App Engine. For example, I have deployed once, been given this error, then deployed again a couple minutes later, and that initial instance that is now second in line (with 0% traffic) works fine, while the new most recent (active) instance with 100% traffic, has the same error.

enter image description here

I am working with a Flask framework with the correct file structure, including static & templates folders, app.yaml and main.py files. I'm happy to post specific code snippets as requested in comments, I just don't know what code would be helpful to diagnose since there haven't been any changes since it was working fine a couple days ago with the same code.

Any ideas and advice is greatly appreciated.

UPDATE: Removing the 's' from https takes me to the following page... clicking 'proceed anyway' takes me to the website just fine though

enter image description here

Improve this question

1 Answer 1

Reset to default
2

Couple of things to try to diagnose:

  1. Check for errors locally, on your dev server. May have a 5xx error in your new code.

  2. Navigate to http(without the 's')://your-app-and-version.appspot.com to see if that loads.

Improve this answer
Sign up to request clarification or add additional context in comments.

4 Comments

I just tried removing the 's' - have added the results in an edit on the original post. Looking into local errors on the dev server now
The site loads fine here in the US. Your ISP is what is blocking it. They are sensing some suspicious code. Hopefully, your local server sheds some light.
This is very confusing... it works fine now! Must have been when I clicked proceed anyway from safebrowse. I will still check under the developer tools on chrome for anything unusual, since all my deployments are launched online and not on a local server. But it seems that it solved itself with such a minor solution. Thank you for your help!
I'll also look into figuring out how to make sure this doesn't happen again, especially for visitors to the site. Most likely looking into certificates and security to make sure the site isn't deemed 'suspicious'

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.