Hi,
I created a Container on my PVE server (ip 192.168.1.106) , specifying an ip (.111/24) during its creation. this ip was not in use in my network before (or by any of my VMs or CTs). however after the installation was finished and a web server was spun up by the application in the CT, to access the web server I had to use the PVE servers IP (.106) instead of the containers IP:
The IP I want to use is set for this container:
BUT I can ssh to .111.
a bit later I created another container, specifying another ip (1.112/24). this container did not have that issue, I can access the web interface using its own IP (.112).
does anybody know what may be going on here?
I created a Container on my PVE server (ip 192.168.1.106) , specifying an ip (.111/24) during its creation. this ip was not in use in my network before (or by any of my VMs or CTs). however after the installation was finished and a web server was spun up by the application in the CT, to access the web server I had to use the PVE servers IP (.106) instead of the containers IP:
The IP I want to use is set for this container:
BUT I can ssh to .111.
a bit later I created another container, specifying another ip (1.112/24). this container did not have that issue, I can access the web interface using its own IP (.112).
does anybody know what may be going on here?
Last edited: