Wow, what's going on at Cisco. This firmware upgrade causes (once again should I say) issues to access the device. In my case, this is what I get instead of the usual configuration pages :
"The requested server-side-includes filename, /usr/local/EasyAccess/www/htdocs/startpage.htm, does not seem to exist."
This is just becoming a big joke and I'll probably switch back to my cheap LRT224 Linksys dual WAN Router
Hi all, having same issue here. Working hard "to change nothing and save" did not help "forbidden" bug.
With my privilege i can't view CSCvg42801 so ... but now it's available firmware release 126.96.36.199. hope this release correct this bug.
RV320 - Edited VLAN's, changed nothing, was then able to log back in from VLAN's. Thanks @alippiatt
I still have one RV325 that appears to be bricked after upgrading to 188.8.131.52, and I have another RV320 on 184.108.40.206 that we cannot login to. Resets do nothing.
UPDATE - RV325 - After numerous resets and reboots I was able to TFTP and downgrade to 1.3.2.02. Still working on the other RV320.
Cisco - How on earth did this update make it out of quality assurance? I have a nephew with a few crayons that could have done better. I will make it my duty in life to bash Cisco at every opportunity. Thanks :)
Better question - What router should I replace all of my RV320's with?
I highly recommend you contact Cisco Technical Support for this issue. If you have difficulty i can help you.
Thanks and sorry that you're experiencing this issue.
Just purchased it. Just flashed it. Just broke it.
And that was fast.
I've been playing around with this bug for two days already an it
just comes back every time I reboot the unit.
Wasted time, really.
I have 3 vlans, a couple of routing entries and easyvpn configured.
The bug is affecting ALL vlans (default included), so I have to connect
via easyvpn in order to access the configuration page again.
I then change few random things here and there such as the
cisco password, enable/disable https or refresh the vpns config,
save & exit and the bug goes away... but as soon as I reboot the
unit, here we go again.
I don't really know what is triggering this bug but it pops up as
soon as I start configuring the unit after resetting it to the default
It's my first "cheap" cisco router... I also own 5 1941 routers and
8 SG300 switches... not a single problem there in 3+ years (ipsec,
gre, dmvpn, vlan, glbp, eigrp, dhcp and more)... rock solid ios on
My only “solution” was, as for plenty of users, the return to 1.3 version wich is more stable.
But even with it, from time to time the router stop accessing the internet and I have to reboot.
My oppinion is also that there is a problem with gateway ping for newtwork detection.
A 6020 TPLINK dual wan worked in the same network for years without a single reboot.