Bad requests meaning unanswered requests or returning with 4xx code?
Can you send a wider screenshot? Two containers seem to be restarting...
Try doing sudo docker ps and see what's up
Sure, no problem - I'll go think of something that will help us get this error more easily next time 😄
Hi SuccessfulKoala55 , I believe I was only given one option in my region (EU Stockholm) which was the 0.16.1 version with the AMI location:
aws-marketplace/allegroai-trains-server-0.16.1-320-273-c5c210e4-5094-4eb9-a613-a32c0378de31-ami-06f5e9f4dfa499dca.4
I used the Trains AMI, and I am not sure whether it was the auto-updated or static one
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)?
OK - this looks like either the server is down or there's a communication issue (FW most likely)
A lot of bad requests and connection refused
(BTW - in the AMI distributions, the docker-compose-yml should reside in /home/ec2-user )
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
Indeed. Try sudo docker logs trains-apiserver - let's see what's bothering it 🙂
Probably the apiserver component and the fileserver component...
Might be a typo in the new configuration?
Hang on, It was the static - No auto update AMI:ami-0d6f44a1a7145a9f8
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?
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
😄 - nothing's embarrassing, we all have typos 😄