I am facing the same problem and my situation is a bit different
I have a mikrotik that has the public ip, and that is the one I can get, then i have another mikrotik in the private network
the one who has the public ip has also a private ip in another interface and is making nat masquerading
I also have another nat rule
ip firewall nat add chain=dstnat protocol=tcp dst-port=8292 action=dst-nat to-addresses=192.168.10.2 to-ports=8291
and when i go to winbox and write
ip public:8292
username:…
password:…
I get the error..and all of ther service are with 0.0.0.0/0 what could be the problem??
Three-plus years after first posting to this thread I have the problem again - on an RB532A running RouterOS v5.8
I can say the problem is nothing to do with Windows as I can Winbox through this router to Mikrotiks on the subnet behind it. I can ping the wireless interface and Telnet to it but any attempt to Winbox to it brings up the “Could not get index. Fatal error”, message. Attempting to Webbox to the router with this address causes a “The connection to the server was reset while the page was loading” error message.
However both Winbox and Webbox will work normally to the wireless interface/ip address on the ‘far’ side of the router, even passing through the router to get there, and once in by this method I can find absolutely no problem with its configuration - and indeed it is functioning perfectly well.
(ie Me (10.1.0.10/24)<>(10.1.0.1/24)Dodgy Router(10.1.1.1/24)<>10.1.1.0/24 = Me Winboxing to 10.1.0.1 just seems to hang. Me Win/Webboxing to 10.1.1.1 works normally.)
As the interface is the functioning gateway to the 10.1.1.0/24 network I assume it’s working OK at the IP level, and it responds to pings and traceroute. There’s nothing in firewall blocking ports 80 or 8291, services are OK.
I have absolutely no idea what is going on, and that worries me. Can anyone shed any light on this/suggest any further diagnostics?
Had the same problem, very annoying.. If you change the default Winbox port 8291 to something else in ip/services. you should then be able to access via Winbox with wan ip address & port number.
I’m hoping this will help others with this problem.
Today I had my laptop internet go out while connected to our office Mikrotik (RB450G running ROS5.25)via winbox it closed my connection to the mikrotik obviously.
I ended up unplugging then replugging my laptops network cable and my internet came back up. then upon attempting to reconnect to our office Mikrotik via the Primary WAN IP(force of habit) I received the same error message Winbox: Could Not get Index: Fatal error.
After scratching my head for a bit I tried logging into the same Mikrotik via its private ip address(default gateway for my laptop’s lan) this worked without issue, Our Mikrotik also has a secondary Public Ip on a different providers circuit for failover I was able to connect to it by this IP address as well. Another test I did was I tested logging into winbox from several other internal network pc’s and a few outside computers utilizing the same primary WAN public ip that stopped responding to my winbox connection attempts, all of these other devices had the same exact error so I knew it wasn’t specific to my laptop.
Still not able to connect to the device by its Primary WAN ip i reenabled the www service and tried loading webbox on the Primary Public ip , it loaded and I simply deleted my old winbox shortcut on my laptop and downloaded from the router’s webbox interface a new winbox executable, and was able to connect via winbox to the Primary WAN’s public ip I previously was having the issue connecting to, after I was able to connect to the primary WAN’s public ip address using my new winbox executable all the other devices i previously tested with were able to login without the error… by far the strangest thing I’ve ever seen.
Sorry about the lengthy post however I wanted to see all I went through with this situation.
Hi!
The same problem! Done all what is in post! Nothing is helping!
In begingin try to restart router, it worked! But now even restart wont work!!
Any ideas! Mikrotik boys??? It is real problem my 500pc is sitting on router what i cant normaly administrate!!
Same Problem!!!
I am using RouterOS in a PC pentium 4 and 384 ram
when i was trying to connect by ip appear this message: "Could not fetch index from 10.0.0.1:80: Bad Gateway
and when i was trying with mac, this message: Could not connect to xx:xx:xx:xx:xx:xx (port 20561) - time out!
Had the same problem, very annoying.. If you change the default Winbox port 8291 to something else in ip/services. you should then be able to access via Winbox with wan ip address & port number.