If a remote web admin connection cannot establish, first check if the device can resolve the InControl server address.
Go to System > Ping on the web admin GUI and ping ra1-1.peplink.com.
If you get a reply, but the Remote Web Admin connection still does not work, make sure you don’t have any firewall or outbound policy that blocks or incorrectly routes outgoing TCP port 443/5246 traffic to a wrong WAN or PepVPN connection.
You an ask the provider if the above ports are blocked, but this is unlikely since TCP 443 is a commonly used port.
They might block certain traffic to ra1-1.peplink.com ?
Note that ra1-1.peplink.com is only 1 of the InControl server hostnames,ra1-2.peplink.com is another hostname used for Remote Web Admin servers.
The original source of this article is this FAQ on the Peplink forum.
Leave A Comment