Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Lolu chungechunge lwabekwa kunqolobane. Uyacelwa ubuze umbuzo omusha uma udinga usizo.

Webinterface not loading - possible security risk

  • 1 baphendule
  • 0 zinale nkinga
  • 19 views
  • Igcine ukuphendulwa ngu Andreas

Andreas
Andreas
more options

Hi,

we have some appliances with a webadmin interface over https with a custom port. Since one of the last Updates, Firefox 102.3 (portable) is still working, I can not load the webadmin of said appliances when I try to connect over DNS or the WAN IP, it's only allowed to be accessed through our WAN IP or from the local network. When I connect with the internal IP address of the Appliance or if I use Opera/Edge (both I don't want to use) I get the option to accept the Security Risk and Continue. It's not with every Appliance, same vendor, same firmware but maybe newer certificate. But all certificates still valid, but self-signed.

What can we do, other than not use Firefox?

Greetings from Germany, Andreas

Hi, we have some appliances with a webadmin interface over https with a custom port. Since one of the last Updates, Firefox 102.3 (portable) is still working, I can not load the webadmin of said appliances when I try to connect over DNS or the WAN IP, it's only allowed to be accessed through our WAN IP or from the local network. When I connect with the internal IP address of the Appliance or if I use Opera/Edge (both I don't want to use) I get the option to accept the Security Risk and Continue. It's not with every Appliance, same vendor, same firmware but maybe newer certificate. But all certificates still valid, but self-signed. What can we do, other than not use Firefox? Greetings from Germany, Andreas

All Replies (1)

Andreas
Andreas Umnikazi wombuzo
more options

I forgot to mention that I tried deleting the SiteSecurityServiceState.txt and that we use a proxy, but every browser is configured to use the systems internet settings. Also the problem exists on every system with an up to date firefox :/