continued 502 bad gateway

[djhurlburt]

I fell to the problem of not logging into the the freeDNS enough. So I fixed that and then found that my status page indicated “Startup Dependence on FreeDNS” so I (re) ran Install Nightscout phase 2 and was able to get my "status" screen to look like it is supposed to (https://navid200.github.io/xDrip/docs/Nightscout/Status.html)

I rebooted the server, but am getting "502 Bad Gateway" error, and following the instructions on this page: https://navid200.github.io/xDrip/docs/Nightscout/502BadGateway.html - after doing it a few times, it says to "contact us". I hope I am doing that by sending this discussion.

Just in case, I just (re)ran “Install Nightscout phase 1” from the Google Cloud setup submenu and then did another reboot; verified status was still good....but am still getting the 502 bad gateway.

[Navid200]

Can you run phase 1 again?
Does that solve the problem?

[djhurlburt]

Hi. I did rerun the phase 1 again, and it did not fix it . Wait, to be clear, do you want me to re do it? Should I do phase 1 and then phase 2?

[Navid200]

When you log into your FreeDNS account, is the subdomain look in regular font instead of bold?
If yes, you need to create a new subdomain and use it instead of your old subdomain. Sometimes, a subdomain is disabled and the only way to know is the font!

[djhurlburt]

it looks like it is "regular"

although as I post this, the pic looks like the domain is bold, but it isn't....

[djhurlburt]

So for the heck of it, I just did phase 1 yet again, and now it is working. The system must know you are engaged.

[Navid200]

LOL

You should delete the image that shows your hostname just to keep it confidential.
I know that you have not disclosed your API_SECRET.
But, still. I always suggest to everyone to also keep their hostname private.

I am pleased it is working again.