@djwujek 

 

Normally no problem, but you also have to change the IP on the controller, you also have to change Port forwarding to the new IP address if you have it.

 

The controller was restarted. After the restart, the controller received an IP from the changed subnet, but it still does not connect to the controller.

  @djwujek 

 

I don't know anything about Docker but I know it has a firewall, have you checked that it's ok?

 

  @djwujek 

 

Do you have any switches and access points in your network? Are they working properly?

No device after changing the IP is no longer adopted whether it is a switch or an access point. No firewall settings are made, this is a default configuration. I even tried to put the controller on Linux Ubuntu, the same situation.

  @djwujek 

 

are you using the router as a dhcp server?

are you getting an ip from the router?
can you ping your router?

 

Try from your PC and from the SSH console on the controller.

 

 

are you using the router as a dhcp server? - yes are you getting an ip from the router? - yes can you ping your router? - yes

  @djwujek 

 

hmm, sounds strange, normally there shouldn't be any problem changing the IP, did you get a ping from the console to the controller to? then there's nothing wrong with communication.

 

 

  @MR.S 

The controller changes the IP, the computers connected to the router also change the IP, the ping goes to the router's address and the controller does not adopt. And this error has been going on for some time, it did not happen before.