RV325 firmware 1.4.2.19 login issue

[guillemmll]

Hello, I just have updated router firmware from 1.3.2.02 to 1.4.2.19...... and first problem is that I can´t login to GUI, does anyone else is happenig same issue?

I have tried many browsers and OS, but allways is the same, problem with certificate and is I access directo to 443 port with firefox "400 Bad Request - The plain HTTP request was sent to HTTPS port - nginx/1.10.1" other browsers are waiting.

Regards

[guillemmll]

Hello, I reply myself, I think the problem is default configuration, I have downgrade to 1.3.2.02, all above this firmware has the same issue. Steps for if anyone has same problem:

Step 1: downgrade to 1.3.2.02

Step 2: login and reset certificates.

Step 3: login and reset to factory

Step 4: NO LOGIN (Prevent change default password)

Step 5: Upgrade to 1.4.2.19 via TFTP, I have not checked with 1.4.2.15 neither 1.4.2.17

Step 6: Login to web UI and for now is working without issues.

Regards

[ktonev]

Hello,

Did you perform a factory reset after upgrading the device? In the release notes it is recommended to perform a reset to factory defaults once you upload the latest firmware:

"We recommend that you reset your device to use default settings when you upgrade to version 1.4.2.19 and reconfigure your settings to include these new features"

[guillemmll]

Yes I did it, but it didn't work with reset button, it just has been solved as I explein above, seems the problem happens if upgrade is done thru web interface because when you log in, first step is change password, if you reset to factory and then upgrade via tftp has worked fine.

Regards

[viningele]

If Cisco SMB router firmware requires a complete re-config from scratch then I'd say cisco needs new engineers or we need to buy product from another company.  Why is cisco continually making us work harder because their engineers are working dumber.  

[JOHNCHERRY19837]

I am having this same issue with the 1.3 firmware.  I have been unable to achieve any factory reset with the reset button.  I do not have experience with CLI or TFTP, though I have to teach myself in order to perform an actual reset and rollback the firmware.  This is a very common problem from what I've found and I haven't seen a solution yet.

John

[JOHNCHERRY19837]

I figured out a solution!  If you are receiving the 502 bad gateway message and unable to reach the router GUI at 192.168.1.1, you have to flash the firmware.  A factory reset will not get you back in to the router.  The only way I could accomplish this was to use TFTP program http://tftpd32.jounin.net/tftpd32_download.html.   Again, a factory reset is not going to get you back in.  You must flash the firmware.

Follow the instructions posted here the for a Netgear firmware flash.

https://kb.netgear.com/000059633/How-to-upload-firmware-to-a-NETGEAR-router-using-TFTP-client

The key is to "PUT" the bin file onto the router while it is booting.  It is different for the Cisco router, so read this on how to get it into the boot loader phase.

https://www.paladin.technology/tech/73-cisco-rv325-firmware-update-via-tftp.html

Make sure the server interface is set to the static IP you set earlier and not another IP.  The PWR LED should be blinking green and the DIAG will be solid red.  Click on PUT and you should see the status bar filling up.  Voila!  

Now if the certificate is bad, like mine was, you can fix that too!  You should be able to log in to the GUI at 192.168.1.1 using cisco/cisco.  Under System Management, there is a Factory Default option.  There you can reset the router to Factory Default including Certificates.  That will restore the router and remove any certificate issues.

Hope this helps.  It took me 2 days to track this method down and lots of help from this forum and the web.  Let me know if this solution worked for you.

John