Vivaldi won't open a whole bunch of sites…frustrating
-
You could run traceroute on the problematic sites for a starter, perhaps, plus check their ping times.
I suppose it could be nothing more complicated than a time-out problem, or a bad handshake at some node or other between you and the web destinations. Vivaldi has showed some signs of behaving poorly when the remote page takes too long to respond - but I almost never see any signs of that problem here - like once in a couple thousand pages or less, and then a reload goes smoothly.
So I'm not technically proficient enough to advise you. I'm just spitballing.
-
All 3 of the sites you listed open fine here (U.S.) with Win7-64, Vivaldi 1.0.303.32 stand-alone.
1. Do you have any extensions installed with Vivaldi?
2. If you try another browser, can you access the problem sites?
3. Are you using a proxy of any kind for your connection?
4. Do you use a special hosts file or custom DNS setting in your computer?
5. Are you allowing at least session cookies for the sites?
6. Does your AV perform any kind of 'trust' checks for visited websites? -
Hey Blackbird, thanks for helping out.
1. No, no extensions installed
2. Yes, I can access them with Firefox, Opera and Chrome.
3. No, not to my knowledge. I use 'stock' Windows settings.
4. No, since I'm not hosting anything. (Is there a way to check, to be certain?)
5. Yes, I'm allowing all cookies.
6. I use stock Windows Defender settings, so my guess would be no?Thanks!
-
EUREKA
Located the problem, now the only thing is - how can I get around it?
I tried switching off things one by one, first adguard, and then in Windows Defender settings. And it seems that the Windows Defender setting 'Real time protection' is making Vivaldi unable to browse those sites. It doesn't prevent other browsers doing so, so there must be a workaround of somekind?
-
Done (though MS's site is so clunky, I'm not sure if i've posted to a community site or made a bug report…)
-
Apparently, according to MS, creating a Vivaldi.exe exception in win defender should do the trick, though it's not the most elegant solution.
-
And also, I've scanned for some malware, and on a relatively fresh installed system, malwarebytes found Quite an amount of malware, eventhough i'm a safe web-browser. so i switched to bitdefender. that also helped the Vivaldi not opening sites issue. Bitdefender doesn't recognize Vivaldi as a problem
-
Apparently, according to MS, creating a Vivaldi.exe exception in win defender should do the trick, though it's not the most elegant solution.
Even more elegant is to remove completely that useless spyware from the system. And use a decent antivirus.
-
After almost 20 years of using 3rd party antivirus, firewall. SRP, anti-adware products, you name it, I've concluded there aren't any decent ones. I've used almost every brand out there, and it's not that they don't protect you - most do, at least pretty well. Their chief drawbacks are hogging system resources, interfering with normal file access, or blocking normal software that you want to run on your machine.
Norton, McAfee, Avast, Avira, AVG, PrevX, bitdefender, Panda, Kaspersky, Lavasoft, Trend Micro, Malwarebytes, etc., etc., all eventually caused some sort of system problem and could not be continued.
The best protection is a decent hardware firewall and safe behavior. With safe behavior and Windows' own free security measures, I have been trouble-free since MSE came on line.
-
Just to add my 2c again: After the big update from Microsoft for Windows 10 the other day, the problem with Vivaldi Beta not being able to open sites is non-existent.
Kind regards,
-
… After the big update from Microsoft for Windows 10 the other day, the problem with Vivaldi Beta not being able to open sites is non-existent...,
That's good news indeed! FWIW, yours is the first report of many I've seen that shows the 10 November Win10 update actually improving/fixing something on a user's system… nearly all the reports of system changes I've encountered involve all kinds of things that were broken or covertly reset to default by the update. :unsure:
-
-