Detailed description: no longer have access to router in my case at 192.168.1.1 via browsers or telnet
Product & version number: Norton latest as of 10/6/2024
OS details:
What is the error message you are seeing?
If you have any supporting screenshots, please add them:
Hello Chester_John. Are you following these steps?
My side I insert 192.168.1.1 into my URL bar and press enter. I see the info in the 1st screenshot below and click “Continue to site”.:
I see the info in the 2nd screenshot: Click “Help me understand”.
Next, the below appears in the 3rd screenshot: I click " Proceed to 192.168.1.1 (unsafe)
Which then lands me at my Verizon router login page:
SA
This was working (with the no https as in your note) until the newest version of Norton 360 came out a week ago (version 24.9.9452 (build 24.9.9452.877))
I can ping it, but no more
I’m on version 24.9.942 ( build 24.9.9452.877 ) as well. What browser are you using? I’m using Opera GX (default) and Edge alternative. Don’t add http to the URL link. Just 192.168.1.1
SA
I’m generally using Edge, but I’ve tried this on both Edge and Chrome. Yes, I tried just 192.168.1.1 to no avail. The new version of Norton 360 said they are limiting a couple of modules to protect privacy which I think may be the problem, but I don’t know where to reset them in the new Norton 360
Found it!!
in norton 360 goto security > advanced > browser protection
then set HTTPS scanning to disabled.
Then it works!
Note: it would be great if Norton would allow a list of escapes (192.168.1.1 for me) and allow https scanning to continue for other addresses
further info, they already have an exclusions list
Awesome find!! Thanks so much for the info and post-back. I’m sure there will be others who will see your solution and be grateful there is one. Kudos!!
SA
som info when the 24 is comming out to all
Globus5000. With all due respect. Version 24.xx is already out and still BETA. This thread is for putting the issues that may be being ignored out, so that, corrections are done and hopefully included into the public release. More info is coming seems to be the standard answer for what should already be see from where I sit. If I am going to be forced into a new version, not once but twice. And after removal on my part only to have the very first live update go directly from version 22.23.10.10 to 24.xx , its only right to post the issues being found so we can get resolutions. The choice that should have been made here. Was put version 24.xx STRICTLY in a BETA channel and only there until real world issues can be found/corrected. Having our devices pigbutchered isn’t a real world scenario we should be dealing with.
SA
Thank you. I was going to uninstall Norton. Fing pain in the @@s
