RV320 1.3.1.12 to 1.4.2.20 update now can't access GUI.

[fmarshall]

After updating the firmware, system won't respond AFTER LOGIN to http/s, SSH or Telnet.  "Forbidden"

The configuration is large enough to NOT want to re-enter.  It's been saved of course.

What to do?  I still have a 1.3.1.12 in production.

[Kristian_Skytte]

Same problem, but I can access the router with FireFox

[fmarshall]

See my other post about using Port 8007 here in Small Business Routers.  That may help.

Summary:

Can access the router with https://(address)

Can access some routers with http://(address):8007

In the end, I don't think it's browser-specific although it can seem that way if some browsers aren't flushed of old data.

[leecoxhouse1]

I loaded 1.4.2.20 on my daughter's RV320 router at her business and I can access it with Microsoft Edge fine.  I loaded it in January right after release of the firmware.

[fmarshall]

Sorry, I'd solved this problem last year but had lost track of the thread where I described the solution.  

It appears there's a bug in firmware at least as recent as 1.4.2.19 and, I'm rather sure now including 1.4.2.20.

It has to do with the VLAN setup if starting with earlier firmware where it works (e.g. 1.3.2.12)

Here is my description of how it was fixed / worked around:

At first, I suspected the firewall and Access Rules but they didn’t cause the problem as I added them.

Next step was the VLAN configuration:

The original VLAN configuration was done like this:

Delete default VLAN 25

Delete default VLAN 100

Add new VLAN 2 and used this for Management.

Add new VLAN 3:

This leaves default VLAN 1 which was originally for Management and is now unused.

Here’s the result that is running on 1.3.2.12 but won’t work for GUI login on 1.4.2.19:

Then, when building it over again on 1.4.2.19, I did this:

Deleted default 100

Renamed VLAN 1 and VLAN 25 and used them.

Used VLAN 1 for Management

Here’s the result:

This one seems to survive a reboot and lets me log in.

It occurs to me that maybe having Management on a VLAN other than 1 is the culprit here.  

I hope this is helpful to someone!