Windows 10 will reach EOS (end of support) on October 14, 2025. For more information, see this article.

Avatar for Username

Eheka Pytyvõha

Emboyke pytyvõha apovai. Ndorojeruremo’ãi ehenói térã eñe’ẽmondóvo pumbyrýpe ha emoherakuãvo marandu nemba’etéva. Emombe’u tembiapo imarãkuaáva ko “Marandu iñañáva” rupive.

Kuaave

Ko téma oñeñongatúma. Ejapo porandu pyahu eikotevẽramo pytyvõ.

Webinterface not loading - possible security risk

  • 1 Mbohovái
  • 0 oguereko ko apañuãi
  • 4 Hecha
  • Mbohovái ipaháva 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

Opaite Mbohovái (1)

Andreas
Andreas Porandu apoha
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 :/