I have a RB951G-2HnD running v6.27.
Previously, when browsing to the system’s IP address, I would be presented with a web GUI allowing for system configuration or access to the graphs, etc. Basically, I used to see something similar to this page here (image is representative, and not up to date):
I now see that any attempt to use the web interface results in a “Connection refused” message. The entire web GUI interface will not load.
I have rebooted and A/C cycled the device multiple times to no avail.
I would love to be able to see the statistics for my interfaces – which is fully functional from within WinBox – through the web interface.
Is there a way to restart the web interface - or even debug why it’s refusing connections?
For what it’s worth, I have a second device (RB951Ui-2HnD) that has a very similar, if not identical, configuration, and I can access its WebGUI just fine.
The Sophos device is the 10.50.0.1 address listed in the log file. It is the core router for the network. It does not serve WiFi.
Checking as you say, I disabled all security features of the Sophos device, and still cannot connect. Not surprising since the second box works with all security features enabled. I have also changed IP addresses a few times during debug to ensure that no stray policies were being applied somewhere. No change.
The Sophos router, Mikrotik devices, and hard-wired-client I’m trying to access the Mikrotik from, are all connected to the same Gigabit switch.
Mikrotik1-(gigabit ports)- No WebGUI access, ping successful, WinBox mgmt OK
Mikrotik2-(10/100 ports)- WebGUI works fine, ping successful, WinBox mgmt OK.
Even when the failing Mikrotik device is on the same subnet as the client, no web access is available.
Using the default 192.168.88.1 with client on the 192.168.88.0/24 subnet, no WebGUI.
Usually, a firewall rule blocking you would result in [waiting], [waiting], [waiting], [timeout]
“Connection Refused” sounds like the service isn’t running on whatever host your request ends up hitting. I assume the Winbox screenshots you posted are from the Mikrotik in question. The logs show the Mikrotik refusing the connection as well, so it doesn’t look like you’re beingdirected transparently to another device.
Look in IP > Services to make sure “www” is enabled, and set to port 80, and doesn’t have an “available from” setting that conflicts with your IP address.
It was disabled under IP/services. Thanks for the info. I had checked the “Service Ports” under the firewall for a ‘www’ entry, and forgotten about this area. Thanks again!