How do I access my golang app in the flexible env, when the server returns 404, yet not errors are shown anywhere?

[mister render]

Hi all,

I am quite new to appengine, but have managed to get an app of mine working on the standard env.

I am building a new app which requires filesystem access, so I switched to the flexible environment.

The deployment and build work without errors (or, the logs at least show all is in order). How come I am getting a 404 when trying to access my app?

I cannot diagnose an issue that is not shown anywhere. I would be grateful for any assistance.

Also, I tried linking to the app in question before, but my post never showed, so I am wondering whether that may not be permitted, so I am omitting a link for now.

Many thanks

[Attila-Mihaly Balazs]

When running AppEngine Flexible you can connect to the instances using SSH: https://cloud.google.com/appengine/docs/flexible/go/debugging-an-instance

So you can check out directly on the instance where the issue is.

Also, does the app work as expected locally?

Attila

[mister render]

Hi, thank you for your reply, I really appreciate it :)

Yup, works locally.

Now, when I try to follow the SSH tutorial, I am shown the following:



I wonder whether I am really missing the trick here somewhere.

[Attila-Mihaly Balazs]

Sorry, I have very limited experience with AppEngine Flex (been doing AppEngine standard work mostly).

Given the fact that you see no instances seems to indicate to me that the 404 is not coming from your code, but rather the Google load balancer and it didn't start any instances of your app. I would assume that it fails to start instances because they don't respond to health checks or some similar issue?

Can anyone with more experience with AppEngine Flex weigh in? I'm assuming that there should be something in the logs about starting/trying to start instance.

Attila

[mister render]

Actually, I managed to resolve this by deleting all my app engine apps, starting a new one and following the tutorial right at the beginning. The mistake was to start with deployments from my local machine (rather than going the github route).

Thank you very much for your help!