Business Community > Gateways > ER605 Router v1 - no HTTPS after upgrading firmware
< Gateways

ER605 Router v1 - no HTTPS after upgrading firmware

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

ER605 Router v1 - no HTTPS after upgrading firmware

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
ER605 Router v1 - no HTTPS after upgrading firmware
ER605 Router v1 - no HTTPS after upgrading firmware
2025-05-02 13:25:03 - last edited 2025-05-06 01:45:40
Tags: #Firmware Update
Model: ER605 (TL-R605)  
Hardware Version: V1
Firmware Version: ER605(UN)_V1_1.3.1 Build 20231207

I've been running an ER605 on the original firmware, v1.0.1 since 2021 with no issues.  Recently I wanted to start using one of the Dynamic DNS services and decided to upgrade to the latest firmware available for v1 hardware in case anything new had been added.

 

1. I backed up the existing firmware and configuration.

2. I downloaded ER605(UN)_V1_1.3.1 Build 20231207 firmware.

3. Installed the firmware successfully.  Router successfully rebooted and all devices reconnected.

 

The firmware upgrade was easy and all of my network devices reconnected to the web seamlessly afterward.

 

The problem I'm seeing is when I hit the router's login page.  I've always had it bookmarked as https://192.168.0.1/webpages/login.html.  Now Chrome tells me it's not secure.

 

 

HTTPS is already enabled:

 

Eventually it displays the login but it takes a long time.  Before the upgrade it was instantaneous.

 

After logging in, it takes a long time to reach the router's admin menu.  Before the upgrade this was very fast.

 

When I get timed out, it takes a long time reload the login page and sometimes that times out.  Before the upgrade, timeouts took me back to login immediately.

 

What can I do to resolve these issues?  Are there any other steps I missed during the upgrade process?

  0      
 
  0      
 
#1
Options
1 Accepted Solution
Re:ER605 Router v1 - no HTTPS after upgrading firmware-Solution
2025-05-06 01:45:17 - last edited 2025-05-06 01:46:38

Hi @w4lkr 

Thanks for posting in our business forum.

The cert is self-assigned so when you use a browser, it will verify with the CA side to check if it is issued by the CA.

HTTPS cert can be self-assigned and for any web services that use HTTP3 can be self-assigned. If you create yourself a HTTP3 server, it will also generate a cert or you can buy a cert from CA and install that to your server so it will not pop up that warning.

CA cert requires an annual fee. For the Chrome browser, you can also ignore that warning and access the page "anyway".

Recommended Solution
  1  
  1  
#3
Options
4 Reply
Re:ER605 Router v1 - no HTTPS after upgrading firmware
2025-05-05 20:49:56 - last edited 2025-05-06 11:34:48

I found a work-around.  If I use FireFox instead of Chrome it still warns me the router's login page isn't secure, but after I click through the "do it anyway" buttons the login page loads lightning fast in FireFox.  I read a post from another user on Reddit that at some point these router's certificates stopped playing nice with Chrome to the point that loading the login page is problematic.  I have not way to verify if that's true, but for now I'm happy to use FF and keep working.

 

I also considered the possibility that another device on my home network somehow ended up with a duplicate IP assignment of 192.168.0.1.  That might also explain the weird behavior of the login page taking forever to load and sometimes not loading at all.  But that seems really unlikely because even after a firmware upgrade to the router, I would think after a reboot it would assign 192.168.0.1 to itself before standing up DHCP and handing out other addresses, and I'm assuming the firmware is at least smart enough to never handout the device's own assignment......right?

 

I hope this helps someone else.  Just use FF and forget it.

  0  
  0  
#2
Options
Re:ER605 Router v1 - no HTTPS after upgrading firmware-Solution
2025-05-06 01:45:17 - last edited 2025-05-06 01:46:38

Hi @w4lkr 

Thanks for posting in our business forum.

The cert is self-assigned so when you use a browser, it will verify with the CA side to check if it is issued by the CA.

HTTPS cert can be self-assigned and for any web services that use HTTP3 can be self-assigned. If you create yourself a HTTP3 server, it will also generate a cert or you can buy a cert from CA and install that to your server so it will not pop up that warning.

CA cert requires an annual fee. For the Chrome browser, you can also ignore that warning and access the page "anyway".

Recommended Solution
  1  
  1  
#3
Options
Re:ER605 Router v1 - no HTTPS after upgrading firmware
2025-05-06 11:36:24

  @Clive_A Thanks for the helpful info.  I may buy a CA certificate eventually.  Do you have any theories on why it takes 1-2 minutes for the login screen to load in Chrome but in FF it's immediate?  This problem only began after I upgraded to latest firmware.  I have yet to rollback to the old firmware and see if the problem goes away.  I don't mind clicking through the proceed anyway buttons as much as I mind the really long load time.

  1  
  1  
#4
Options
Re:ER605 Router v1 - no HTTPS after upgrading firmware
2025-05-07 00:40:32

Hi @w4lkr 

Thanks for posting in our business forum.

w4lkr wrote

  @Clive_A Thanks for the helpful info.  I may buy a CA certificate eventually.  Do you have any theories on why it takes 1-2 minutes for the login screen to load in Chrome but in FF it's immediate?  This problem only began after I upgraded to latest firmware.  I have yet to rollback to the old firmware and see if the problem goes away.  I don't mind clicking through the proceed anyway buttons as much as I mind the really long load time.

We do not support an external CA to be installed on the router.

The system was optimized for the Chrome-based browsers before. But ER605 V1 has been discontinued for support and production for a long time. We then did not release newer firmware for it.

The FF uses a kernel different from Chromium. And their default security and browsing settings are different. That could be the reason.

  1  
  1  
#5
Options

Information

Helpful: 0

Views: 770

Replies: 4

Tags

Firmware Update
About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.