@SuperOscar
I'm not using wayland. i just thought your issue might be related to this bug report and the latest snapshot claimed it was fixed.
That is: VB-105882
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Vivaldi]
"ExtensionManifestV2Availability"=dword:00000002
The whole MV3 thing is a catastrophe for those of us who have been relying on various content blocking extensions to throttle web exploitation and privacy abuse.
This is a Windows registry change. What about all the other desktop platforms?
This is ridiculous, why has this not been fixed after months and why do we need to learn something completely unrelated just to put up with the devs' incompetence?
IMO (one might probably say IMNSHO) if the server have both HTTP on port 80 and HTTPS on port 443 configured, then one should make the server on 443 the primary one (and redirect there from 80). The "problem" only occurs if one mixes the two, and expect to get to port 80. You will get to port 80 iff there is no open port 443.
This is not a valid assumption. Webservers can serve both http sites and https sites. Just because a webserver has port 443 open does not mean that particular site is configured for or even capable of https. Further, closing port 443 on the webserver would break any site that does use https.