OK, and what do you see now in the UI?

I see it seems OK now... 🙂

Well, it was OK for a second, now it's not 😞

Yes looks great, thanks!
First thing though is I am going put it behind an nginx-proxy because there seems to be no ACL

Does it still seem OK?

I'm not sure form the link I have here

Or maybe you just blocked access 😄

Yes it seems so

OK - please let me know if anything seems wrong again

Question, I see at the end of the docker-compose file:
networks:
backend:
driver: bridge
I want to change it to:

networks:
default:
external:
name: nginx-proxy

Will that break it?

Because I need it on the same network to go in the reverse proxy

Well, I must admit I didn't try it - but you're welcome to try and let us know :)

By the way, if you get that same UI error message (there might be an issue with migration detection), you can disable it in the server using the apiserver.elastic.upgrade_monitoring.v16_migration_verification flag set to false

Thanks!

Happy to help 🙂

Ok, running now from:
https://trains.shapedo.com/dashboard

When the DNS populates it will also have letsencrypt sign it. so I have https and a password protected login

Nice 🙂

Happend again after restarting the container.

Where does one add apiserver.elastic.upgrade_monitoring.v16_migration_verification flag set to false?

In the docker-compose.yml file, under the services.apiserver.environment section, add:
TRAINS__APISERVER__ELASTIC__UPGRADE_MONITORING__V16_MIGRATION_VERIFICATION: false

You can also put this configuration value in your opt/trains/config/apiserver.conf file, in which case the value is:
elastic.upgrade_monitoring.v16_migration_verification: false

Needs quotes:
ERROR: The Compose file './docker-compose.yml' is invalid because:
services.apiserver.environment.TRAINS__APISERVER__ELASTIC__UPGRADE_MONITORING__V16_MIGRATION_VERIFICATION contains false, which is an invalid type, it should be a string, number, or a null

Does not work with domain name:
Blocked: The Same Origin Policy disallows reading the remote resource at http://trains.shapedo.com:8008/v2.9/users.get_current_user

ah no, same issue with IPS:
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://108.128.174.211:8008/v2.9/auth.fixed_users_mode .

Where do you see that error?

Perhaps this is a result of your different network configuration? Trains Server's default CORS origins configuration is "*" by default

Investigating

Ok - how do I set the API server to a on the web-UI to a different path? Because the api-server needs to be also https, you can't mix calls

You'll need to configure ELB and use sub-domains

See the example here: https://allegro.ai/docs/deploying_trains/trains_server_config/

In the sub-domains section