It shows 502 initially as the services inside the container are starting up. It should go away within 30 seconds. If it doesn’t it is possible that your server’s CPU is under extreme load and it is causing slowdown.
I’ve just cloned the repository and run the setup commands, so I guess it just has the default plugins? Not sure where to check, but I’m sure I’ve added none.
Using a traditional hard drive versus an SSD drive should not cause a 502 error. That’s not really plausible, as your question indicates @elopio.
Here is a little writeup which might be helpful:
The best thing to do, in my view, is to open up some terminals and run tail -f on your both your Rails and nginx log files, including the error logs and access logs; and then try to access and make sure when you see the 502 error you have your eyes on the tails of the log files.
Do you know where those logfiles reside and how to run tail -f commands on them in terminals?
Note, you asked earlier:
Rails run on port 3000 inside the Docker container and that port is not exposed outside the container. That is why you are not seeing port 3000 outside the container when you run netstat outside the container.
Wooo, looking at the rails logs I found that the unicorn log was huge, complaining about some permission errors. I deleted rm -rf tmp/cache/bootsnap-compile-cache/, and now I see the congratulations screen!!!
Thank you friends. I’ll play with this a little more before deciding to recreate it in an SSD server.
Ok, this is working brilliantly. I want to show what we are doing:
It’s the migration of the Costa Rican hackerspace from Telegram to Discourse We still have to do sooo many things, but this time I’m sure we’ll be able to get rid of the chat for sure. Thanks a lot discourse people!