two VMs, running docker on each. and on each VM a App-Server and a Lora-Server running as container.
now i can login to both App-Server websides. when i try to register (or change) a network-server in the webinterface its only possible form the other VM
Example: VM 1 -> App-Server can register NS-Server from VM2, but not from VM1
The loraserver-docker repo only exposes ports for the App Server web UI, gateway bridge, and mosquitto. If you want to access the network server from outside the docker compose network, you will need to expose the appropriate ports (and verify connectivity, etc).
thx for your replay. Sorry for my late answer - i had some days off.
i dont know if i made my scenario clear. i am not using docker compose at the moment - just the docker image for appserver and ns-server.
i have 2 Hosts with docker installed:
Host 1:
Docker: LoraAppServer
Docker: LoraNsServer
Host 2:
Docker: LoraAppServer
Docker: LoraNsServer
Now:
I can Register or Rename (for example) the NS-Server on Host 1 from the App-Server on Host 2
I can Register or Rename (for example) the NS-Server on Host 2 from the App-Server on Host 1
I can’t Register or Rename (for example) the NS-Server on Host 1 from the App-Server on Host 1
I can’t Register or Rename (for example) the NS-Server on Host 2 from the App-Server on Host 2
So out of my view, the port (8000) is exposed - then a appserver on a different host can access, but not on the same host. any idea? the bind is on 0.0.0.0:8000 - is this a problem, if the ns-container and the appserver container is on the same docker-host?
i think now i am one step further. i linked the two containers on the same host.
then i can add the ns-server with the docker internal ip address.
but if i use the hostname (and i added it as entry in the hostfile) it still uses the public ip address instead of the internal docker ip. any further help would be great.