Can you use https with a port other than 443 on other devices? If you are using https, doesn’t the certificate expect to see port 443?
I use HTTP on the LAN, not secure, but I use a different port unlikely to be guessed.
Yes. HTTPS is not bound or required to operate on 443. It can operate on most any port in fact.
I tested this and it works. You must be doing something wrong.
Specifically, I allowed everyone to get at web UI and then logged on to an SSID associated with a VLAN. From that VLAN/SSID, I was able to get into the router admin web interface via HTTPS and a port number over, 20,000. This with a hardware version 1 Surf SOHO.
Best guess: Maybe you used the wrong IP address. From each VLAN, the IP address of the router is different. Next guess: Maybe you have internal firewall rules.
1 Like
Ok Michael now try changing the port assignment for that VLAN. Change it from say VLAN whatever on port 1 to using port 2 instead (“Access” mode not trunked) and reprovision router. Try to login again. Let me know.
My testing only involved a WiFi SSID assigned to a VLAN, I did not test with Ethernet. Moving a LAN port from one VLAN to another is a big change. I don’t know exactly when it kicks in, but I would certainly reboot the router and computer before testing anything after making such a change. I am not going to test this.
Well I have to move LAN ports between VLANs pretty frequently in my testing/lab environment. It’s not that big of deal, and it should not be locking me out of the router.
So I did this yesterday afternoon for the 100000th time. Locked right out, as usual. Got fed up and purchased a subscription to InControl2 and miraculously, it is able to log me right in and administer my router remotely. For a small fee, of course. One almost has to wonder if this is intentional behavior - job security and planned obsolescence if you will. (I kid, I kid - but the issue needs to be fixed.)
ALSO: I did this with a fresh factory default install. No firewall rules setup, and the secure admin port was left at the default 443 (I didn’t even try a non-standard port.) Locked out on FIRST attempt, as usual. It’s not me, and it’s not my SOHO devices. It’s a bug in the code Michael.