Sure, no problem - I'll go think of something that will help us get this error more easily next time ๐
๐ - nothing's embarrassing, we all have typos ๐
Might be a typo in the new configuration?
Indeed. Try sudo docker logs trains-apiserver
- let's see what's bothering it ๐
Probably the apiserver component and the fileserver component...
Can you send a wider screenshot? Two containers seem to be restarting...
Login details to? You mean the user/password you use to login into Trains UI?
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
Try doing sudo docker ps
and see what's up
I assume you have an SSH to the server?
OK - this looks like either the server is down or there's a communication issue (FW most likely)
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
Bad requests meaning unanswered requests or returning with 4xx code?
(BTW - in the AMI distributions, the docker-compose-yml
should reside in /home/ec2-user
)
A lot of bad requests and connection refused
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?
Hang on, It was the static - No auto update AMI:ami-0d6f44a1a7145a9f8