Hi DilapidatedDucks58 ,
I'm not aware of anything of this nature, but I'd like to get a bit more information so we could check it.
Could you send the web-server logs ? either from the docker or the browser itself.

this is how the interface looks

Please hit Ctrl-F5 refresh the entire page, see if it is till empty....

I've done it many times, using different devices. sometimes it works, sometimes it doesn't

working on the logs

dnk if it's relevant, but I also added a new user to apiserver.conf today

web-server seems okay, could you send the logs from the api-server?
Also if you can, the console logs from your browser, when you get the blank screen. Thanks.

I decided to restart the containers one more time, this is what I got.

I had to restart Docker service to remove the containers

I'll get back to you with the logs when the problem occurs again

as a sidenote, I am not able to pull the newest release, looks like it's not pushed?
"Error response from daemon: manifest for allegroai/trains:0.14.2 not found"

Hi DilapidatedDucks58 ,
If the issue returns, please post the browser console logs as well as the trains-apiserver container logs - we'd really like to get to the bottom of it - I tried upgrading a server here as well as installing a new server and so far couldn't reproduce 😢

DilapidatedDucks58 if you get this error, what container version did you start?

hmmm allegroai/trains:latest whatever it is

Apologies - it seems we've had an issue with pushing the docker container to the allegroai/trains dockerhub repository (it's also mirrored in the allegroai/trains-server repository into which the push did go as expected) - we're fixing that now. Since the docker-compose file points to the allegroai/trains repository, you received the aforementioned error...

I assume, temporary fix is to switch to trains-server?

Yeah, although I hope the image will be in allegroai/trains shortly 🙂

DilapidatedDucks58 the image is there - please try again and let me know

I've already pulled new images from trains-server, let's see if the initial issue occurs again. thank for the fast response guys!