Exactly, so that remapping of port 8080 should not be the reason for this issue

The only change I made in the .yml file was:
` ports:

• "8080:80" to ports:
• "8082:80" `
  I already had something running on 8080, but since it's the trains-apiserver and not the webserver, this shouldn't be an issue.

Hi DefeatedCrab47 , can you share the reason for trying to use --build ? I'm not sure this is something that was previously tested...

First I tried without build, but same problem. --build just means that it will re-download all layers instead of using the ones already cached.

Port 8080 is used for the trains-webserver , not the trains-apiserver

Ah my bad, it seems I had to run
docker-compose -f /opt/trains/docker-compose.yml pullonce. I quickly tried trains like half a year ago, so maybe it was using the old images? However, I thought --build would take care of that.

Now it's working 🙂

Remapping 8080 will probably mean the web-app won't be able to locate the apiserver on port 8008 since currently it uses substitution to do that, but as you said, this doesn't seem to be related to the error you've sent. The seems to be related to the fact the apiserver can't communicate with the Elastic instance