Within our appliance, we use ingress to do internal routing between the docker images. In some instances, you might be using the subnet we use for ingress. This is subnet 10.255.0.0/16.
This will cause the web interface to be unreachable, and that launchers will not authenticate. To change the subnet of ingress, you can change the configuration using the following commands.
(Note; to enter these commands you have to enter the "maintenance menu". To do this, please refer to the following KB article; https://support.loginvsi.com/hc/en-us/articles/360001278860-4-Maintenance-Menu)
# remove the gateway service
docker service rm VSI_gateway
#remove the docker ingress network
docker network rm ingress #yes we're sure
# check that docker ingress network is not in the list
docker network ls
#if it's still in the list, try removing it again, if that also fails restart the docker daemon: service restart docker
#create the new ingress network with a different subnet ip
docker network create --ingress --driver overlay --subnet 203.0.113.0/24 --gateway 203.0.113.1 ingress
# start the loginvsi daemon to get the start the gateway again
It can take a moment for the web interface to be reachable again, so be patient.