I have configured my live server at “eramba.mynet.domain.com” and have completed a backup of the DB.
I have also installed a copy of the software on a different host at “eramba-dev.mynet.domain.com” where I’ll be running training sessions and creating items as part of creating the user documentation.
Both are docker installs started with something along the lines of
docker compose -f /home/docker/docker-compose.simple-install.yml down
where I’ve tweaked the compose file by changing the default ports
ports:
- 443:443
so that end users don’t have to put the port number on when typing in the address
eramba-dev worked fine until I restored a DB backup made on eramba to it so that I didn’t have to recreate all the settings
Now when I point my browser at
it redirects to
adding the port number and removing the sub domain “mynet”
((the names of the domain and sub domain have been changed in this post))
where and trying to browse results in the browser saying :
This site can’t be reached
the container is still up and running
Could this be something to do with the backup restored from the other server or is it just coincidence?
Is this something that is set in the database? (eg the public address from settings maybe? )
As I don’t have the web interface I can’t restore a previous db backup to see if it reverts…
I would restart the container to see if that helped but since today I can’t restart docker containers it says “permission denied”. I’ve asked IT to look into that.
Any help or pointers appreciated.
Chris