@MR.S 

Unfortunately, ssh is disabled, but I have just discovered that I setup, and forgot about it, an automatic daily reboot.

So assuming the reboot happens every day, rebooting is not working :(

  @Birillo 

Ok, yes then a hard reboot is probably the only solution.
if the router is offline, rebooting from the controller will not work either, the router must be online with the controller.

Then unfortunately I can't help you.

I hope tp-link puts in a reboot command on the router in the future, either via ssh or via the web interface.

  @Birillo 

if you have a router in a fairly remote location, I recommend the tp-link tapo P115 power plug.
it requires you to have internet but it has the option to turn on after a number of minutes.

so when I have a problem I set it to turn on after 1 min. then I turn off the device. the clock runs even if the internet is gone and it turns the power back on after 1 min.

it can also be programmed to turn on and off daily or weekly..
just a tip. a cheap device worth its weight in gold :-)

 Hi  @MR.S 

I managed to send someone to switch off and back on the router together.

Unfortunately, nothing has changed.

I can remotely access the network via VPN (configured in Omada), but in the controller, it still appears as disconnected.

Do you have any idea of what else I check and how I can reconnect it, please?

Note, that i managed to connect via ssh if this could help

Thank you

  @Birillo 

Birillo wrote

 Hi  @MR.S 

 

I managed to send someone to switch off and back on the router together.

Unfortunately, nothing has changed.

 

I can remotely access the network via VPN (configured in Omada), but in the controller, it still appears as disconnected.

 

Do you have any idea of what else I check and how I can reconnect it, please?

 

Note, that i managed to connect via ssh if this could help

 

Thank you

I have no idea what happened to your router.

the only thing I thought about is if there are any DNS problems, you probably have a dynamic IP and something has happened on the remote router's DNS server so that it cannot find the controller. to fix the problem you have to take a forget and readopt router when you get the chance.

I have done that many times and it is a relatively simple process, the problem is that you have to be physically at the router to enter the controller info.

  @Birillo 

SSH, there are very few commands but ask TP-Link if there are any commands that can help you with this problem.

  @Birillo 

SSH, there are very few commands but ask TP-Link if there are any commands that can help you with this problem.