Login details to? You mean the user/password you use to login into Trains UI?

Might be a typo in the new configuration?

A lot of bad requests and connection refused

Try doing sudo docker ps and see what's up

Cool!

I just changed the login details prior the restarting of the server, could this be at fault? I changed the trains-user to a different one

You were absolutely right

Hi TrickyRaccoon92 , did you install it yourself or did you use the Trains AMI (if so, was it the auto-update AMI or the static one)?

Oh god

😄 - nothing's embarrassing, we all have typos 😄

OK - this looks like either the server is down or there's a communication issue (FW most likely)

Indeed. Try sudo docker logs trains-apiserver - let's see what's bothering it 🙂

I assume you have an SSH to the server?

Thank you 😅 Very much

The question is whether the server is there but refusing to handle the calls, or whether its down or blocked due to some network issue

(BTW - in the AMI distributions, the docker-compose-yml should reside in /home/ec2-user )

Sure, no problem - I'll go think of something that will help us get this error more easily next time 😄

Well, before we start debugging this inside the server, maybe a few simple check to make sure we know whats going on externally... Try opening a new private browser session, open the Dev Tools ( F12 ) on the network tab, and than try to browse to the Trains UI - what do you get?

Can I force the login window?

Can you send a wider screenshot? Two containers seem to be restarting...

Probably the apiserver component and the fileserver component...

And now it works

Bad requests meaning unanswered requests or returning with 4xx code?

That’s embarassing

Hang on, It was the static - No auto update AMI:
ami-0d6f44a1a7145a9f8

Yes, the login details to the Trains UI