Webfig unavailable after update

RouterOS RouterOS beta
1

I am not able access webfig. After login it kicks me right over to console. When clicking back on webfig i get a 404 error.

routerboard: yes
model: RB4011iGS+
serial-number: D1270B83A96A
firmware-type: al2
factory-firmware: 6.45.8
current-firmware: 6.47.2
upgrade-firmware: 7.1

The only log files after attempting to acces are as follows:

 09:50:20 system,info,account user [REDACT] logged in from 192.168.2.62 via web
 09:50:20 system,info,account user [REDACT] logged in via local
 09:50:23 system,info,account user [REDACT] logged out via local
2

I Factory-Reset and updated my RB4011 from 6.49.1 to 7.1
I wasn’t able to reproduce the Error.

Did you try disabling the Web-Service and restarting the Router (/ip service set www disabled=yes)
After the Reboot, try to re-enable the Web-Services and connecting to it.

3

I just tried that and that did not change anything. I just started using zerotier, and I am wondering if that’s the cause.

Pic:
tik404.PNG
From the debug console (on browser):

XML Parsing Error: not well-formed
Location: http://192.168.2.1/jsproxy
Line Number 1, Column 1:
4

Try this :

http://192.168.2.1/webfig/#Terminal

5

That works fine… That’s the page it brings me to after webfig error’s out when I first login. Sorry if I wasn’t clear on that.

6

I am having the same problem with Webfig going to the terminal after login and giving a 404 error if I click on the Webfig button.

Recent changes to my RB3011:

  • Update to v7.1.1
  • Reset the Router
  • Imported .rsc config file.
  • Created a skin without the Quick Set button (I would assume that caused the problem)

I can get to Webfig if I manually change the URL to /webfig/#Interfaces

7

I can confirm going directly to #interfaces gets me to webfig. I have not created a skin.

I do have a support ticket in, though I have not received any actual “support” I thought ubiquiti had bad support, but then I met Oskars K. from mikrotik.

They did finally aknowledge the problem, and said it will be fixed in a upcoming release.