I’m able to login to the web interface on the WAN port just fine, however, on the LAN interface it brings up the login page, but will not access my username and password.
I’m using the same user/pass that I can login using the WAN interface.
Situation:
StarLink RouterOS PC
If I connect to the StarLink directly, I can login to the Web interface of the RouterOS just fine.
WAN IP is 192.168.1.4/24
LAN IP is 172.16.240.1/24
This is running the default setup except for the bridge1 and WAN settings.
I have attempted to replicate your config in our office lab on a hAPac lite and have been successful in accessing WebFig with the default user/password combination, when a direct ethernet connection is established between the PC and physical ports ether2/ether3 (not the reassigned name values).
May I ask what IP addresses you are accessing WebFig from on the WAN and LAN?
What interface is your PC connected to?
If no successful login can be made from your LAN side then it is likely your device is not receiving an IP address within the LAN subnet.
It actually brings up the login screen, I'll enter the credentials, and hit login. It will then blank out the two fields and act like nothing was entered.
If I connect the same laptop up to the WAN port (via a small switch), I'll access it via the WAN IP the RouterOS received. It will then login just fine.
Another oddity is that I set up Ether3 on a separate bridge and connected it to a desktop PC. Bridge IP is 172.16.241.1 and the PC is 172.16.241.50. The PC was working, but now it gives me the login screen and after entering credentials, it gives me "Can't reach this Page"
I'm posting a current config as it has changed a bit.
2025-07-27 18:13:07 by RouterOS 7.19.4
software id = 3DD1-XXXX
/interface bridge
add name=bridge1
add name=bridge2
/interface ethernet
set [ find default-name=ether1 ] disable-running-check=no
set [ find default-name=ether2 ] disable-running-check=no
set [ find default-name=ether3 ] disable-running-check=no
/interface list
add name=LAN
add name=WAN
add name=LAN2
/ip pool
add name=dhcp_pool0 ranges=172.16.240.50-172.16.240.200
add name=dhcp_pool1 ranges=172.16.241.50-172.16.241.200
/ip dhcp-server
add address-pool=dhcp_pool0 interface=bridge1 name=dhcp1
add address-pool=dhcp_pool1 interface=bridge2 name=dhcp2
/port
set 0 name=serial0
set 1 name=serial4
/interface bridge port
add bridge=bridge1 interface=ether2
add bridge=bridge2 interface=ether3
/interface list member
add interface=bridge1 list=LAN
add interface=ether1 list=WAN
add interface=bridge2 list=LAN2
/ip address
add address=172.16.240.1/24 interface=bridge1 network=172.16.240.0
add address=172.16.241.1/24 interface=bridge2 network=172.16.241.0
/ip dhcp-client
add interface=ether1
/ip dhcp-server network
add address=172.16.240.0/24 dns-server=172.16.240.1 gateway=172.16.240.1
add address=172.16.241.0/24 gateway=172.16.241.1
/ip firewall nat
add action=masquerade chain=srcnat out-interface=ether1
/system clock
set time-zone-name=America/Anchorage
/system identity
set name=Starry-Mikro
/tool mac-server
set allowed-interface-list=LAN2
Again, I've set up a duplicate config on a hAP ac lite and I have successful WebFig access.
Can you confirm that the laptop has a direct ethernet connection to the Ether2 port on the MikroTik?
If so, considering that you are connected with a 240.X IP address and can access the WebFig site, meaning for at least bridge1 we're not looking at a connectivity issue, it could potentially be session/browser related.
Have you cleared the browser cache and site cookies?
Have you attempted to login via WinBox to isolate the issue to WebFig only?
Has the router (and other connected devices) been rebooted after each set of configuration changes?
What's your Windows Defender up to? Could any config there possibly be playing a part?
Your login works on WAN, so the credentials are fine. Check RouterOS IP service settings to allow HTTP/HTTPS on the LAN IP, and review firewall rules to ensure the 172.16.240.0/24 subnet isn’t blocked.
okay, this was frustrating. I had tried both a Mac and PC to connect directly to ether2 and verified the IP address. Again, it was connecting, but would not accept the password. Like you guys suspected, it really pointed to a problem with the PC/Mac. Since I had tried 4 different browsers on 2 different computers, I was concluding it was something in the MikroTik authentication. I tried with another, newer Macintosh, and it works fine.
The PC is running Windows 10 and has all the latest updates. Pretty vanilla install. No extra firewall or virus protection other than what comes with the OS as it is fairly isolated from the internet.
The older Mac is running Catalina and really hasn't had any problems until this.
The newer Mac is running Sequoia (15.5).
I did try clearing history and cache on the PC and older Mac. The older Mac I can understand if there might be some certificate issue or encryption that needs to be update, but the Windows 10 PC has me puzzled.
Since this is an obvious PC issue, this thread can be closed. I'll figure out the Windows 10 issue. Might be defender or a firewall issue. I'll probably put it on the internet to download all the latest updates first. It has been over 6 months since doing that.
Thanks for the help. Hope I didn't waste to much of your time.
So it's time to start as it is the proper tool to manage MT's devices. MAC access is a lifebuoy.
If you have problems with WWW access why not to try it?
