Hi @Clarkerzas 

Thanks for posting in our business forum.

2.2.2 has forced HTTPS redirection. You probably should try a different browser or lower the security level on your browser if it requires a valid certificate for HTTPS.

Recommend you use the 2.1.5 beta instead of the 2.2.2.

Hi @Clarkerzas 

Thanks for posting in our business forum.

Clarkerzas wrote

Thanks but I had to reset the route and restore. It would appear that after the upgrade it forced the redirect but as access "HTTPS Server Status:" wasn't enabled before the upgrade I would never be able to connect. I reset the router and disabled the HTTPS Server Status: . I have another bug though, when you enable or disable a port forward, it changes the state but you are left with a spinning wheel forever and need to refresh the page to get rid of it else you cannot do anythingon the page.

Does this issue persist in the incognito mode or private mode?

Hi @Clarkerzas 

Thanks for posting in our business forum.

Clarkerzas wrote

  @Clive_A 

 

Hi Clive,

 

I logged into http://192.168.1.254 and then NAT then enabled web_home.

 

See attachement.

 

So you have two issues in the OP.

I'd suggest you set both 80 and 443 which are the default ports to different port numbers to resolve the port forwarding issue. If the 80 is taken by the ER605, you cannot open it up.

Second, about the force to HTTPS, this has been reported by people recently. This is a change in the device. So, if you need to bypass it, after upgrading to the HTTPS, you manually disable it.

What I said earlier about using the incognito mode is that you said it hangs or takes a very long time to log in to the admin web. I am not referring to the port forwarding.

Hi @Clarkerzas 

Thanks for posting in our business forum.

Clarkerzas wrote

  @Clarkerzas 

 

So you have two issues in the OP.

I'd suggest you set both 80 and 443 which are the default ports to different port numbers to resolve the port forwarding issue. If the 80 is taken by the ER605, you cannot open it up.
- Yes this is now resolved.
 

Second, about the force to HTTPS, this has been reported by people recently. This is a change in the device. So, if you need to bypass it, after upgrading to the HTTPS, you manually disable it - Yes I suggest you put as part of the release note to users to ensure https is enabeld BEFORE upgrading to 2.2.2 due to the forced redirect to HTTPS and that there is no check to actually see if it's enabled. 

 

What I said earlier about using the incognito mode is that you said it hangs or takes a very long time to log in to the admin web. I am not referring to the port forwarding. - This was due to the above HTTPS redirect.

 

The other issue I rerfreend was disabling or enabling an already setup prot forwarding rule cuases the interface to hang with a spinning wheel (as per my previous screenshot), It doesn't do this in ingonito mode though.

OK. Now we seem to be on the same page.

I am aware of the previous issues we discussed. About the last issue you said, that if you encounter any issues in the admin web, it hangs forever, you should clear the cache. Usually, we recommend you clear the cache after the upgrade. Sometimes, there might be a new update in the web system but the dev team would not include in the release note. It indeed does not help you or us(support) in understanding the product.

I'll give feedback on this. Hope they can be open to us.