Was given http, but I'll try https!

Yeah no idea why it said https there, the trains.conf has http for everything for sure.
And oops yeah the port it said there was :8010 which seems strange to me as well

We have the server running on a GCP instance and haven't changed anything there for a long time

yeah no luck with either

trains_agent: ERROR: Connection Error: it seems *api_server* is misconfigured. Is this the TRAINS API server https://<<trains-server_ip>> ?

Yeah, that makes sense. So could this be an issue with how we've configured our trains server then?

hmm yeah seems very strange to me too.
So does the fact that trains-agent list gives
trains_agent: ERROR: Connection Error: it seems *api_server* is misconfigured. Is this the TRAINS API server https://<IP>:8010 ?or that curl http://<IP>:8008 gives nothing
give us any useful info? Or are those relatively normal?

Also of interest:
curl http://<IP>:8008/ gives a response when we run it locally, which I think gives further support to the idea that this is firewall related.

We've opened a ticket with our IT dept to see if they can help us, but not super optimistic there lol.

I'll update here if we figure out anything more on this. Thanks again for your help!

No, I meant with setting up trains agents -- stuck on trains-init

yeah that's in the ~/trains.conf both locally (which works) and on the remote machine I'm trying to set up (which doesn't work)

Yeah that's what I would expect!
Neither https nor 8010 appear anywhere in ~/trains.conf, but yeah trains-agent list gives
trains_agent: ERROR: Connection Error: it seems *api_server* is misconfigured. Is this the TRAINS API server https://<IP>:8010 ?

Yeah the web UI is working fine on 8080, and we've been able to run things locally on our laptops fine; only encountering this issue on when trying to set up on our remote machines

Yeah definitely seems odd -- that's not actually coming from trains.conf though:
` api {
api_server: http://<IP>:8008
web_server: http://<IP>:8080
files_server: http://<IP>:8081

credentials {"access_key": <ACCESS>, "secret_key": <SECRET>}

} `Maybe it's something on the server side?

I wasn't the one who configured the server, so I don't know much about that process, but I can ask for details if we need

(btw thanks so much for all your help debugging this, really appreciate it 🙂 )