SSL error when accessing router remotely using TPLink’s own DDNS service
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
SSL error when accessing router remotely using TPLink’s own DDNS service
Does anyone else experience these two issues?
1. In the Tether app, I name my routers, and on router restart **only some** of them revert back to their base name "Archer_A7". 90% of them the custom name remains, but for a few it reverts. Oh, and **alll** Archer A9's custom Tether app names revert to "Archer A9" on restart.
2. The DDNS setting to allow me to login to my browser remotely using *.tplinkdns.com doesn't have a wildcard SSL certificate (they're free so I don't see why not). So I get an error **every** time I log in remotely.