Error 502

jpbodet

I've been running an experiment through JATOS in a Docker through DigitalOcean. I followed the directions in the link below in order to get it set up with Traefik to be HTTPS. Usually, it works fine. Unfortunately, a couple of times over the last few months, the website returns an Error 502 - Bad Gateway randomly.

https://www.jatos.org/JATOS-on-DigitalOcean.html

I saw in a previous thread that this may be an issue as of the May update?

I've looked through alternatives but am hesitant to deviate from the JATOS documentation's instructions, since web security isn't my forté. It went down again today and I'm hoping it'll recover soon, but I'm more hoping to resolve the issue so it'll stop happening!

Please, I'd love any suggestions!!

kri

This is unusual. It seems that in those times that JATOS doesn't respond anymore. This can have many reasons. Since you are on DigitalOcean: can you have a look at the 'Graphs' of your 'Droplet' (which is what DO calls monitoring of your server). How is your memory, disk etc doing? Maybe you just run out of resources?

jpbodet

Hi Kri, thanks for responding! DigitalOcean is showing negligible use across the board. It's really just me testing it, I pulled the experiment until I could figure this out.

jpbodet

Hi @kri , a couple of days later and it's still down -- any thoughts? Like I said, I started it up with the instructions on the website and am not sure how to proceed.

kri

Sorry for not replying earlier. `Error 502 - Bad Gateway` usually means that Traefik still works but JATOS somehow not or at least Traefik can't reach it anymore.

Did you try turning it off and on again? Sounds funny but often solves those problems.

Do you have access to the server's terminal? You can always get access in DigitalOcean -> Droplet -> Access -> click on 'Launch Console'. There you can check if JATOS' Docker container is still running. If not restart it manually or just turn off and on the Droplet. Traefik' and JATOS' container will auto start.

And if JATOS is back up again, I'd recommend having a look at JATOS logs. Log in with an admin user and call myjatosdomain/jatos/log. It's reversed: top most is the most recent log. Look for any errors or exceptions.

Best

Kristian

jpbodet

Hi Kristian,

This error has cropped back up a couple of times and each time I've restarted the server to fix it. At the moment, I'm preoccupied with trying to make the experiment itself work but, once that's done, I plan to put a little more time into its next crash and try to figure out why it's happening.

Thanks again and hopefully it'll just go away :)