2023-12-27, 11:54 AM
(This post was last modified: 2023-12-27, 11:59 AM by jschwar313. Edited 1 time in total.)
I have windows 10 64-bit with all the updates. I use comcast for my isp with windows defender, malwarebytes premium and malwarebytes browser guard. I am installing the 64-bit windows installation version 10.8.13. I use an Archer AX6600 Tri-Band Wifi 6 Router to route my network, not the comcast equipment. The comcast equipment is in bridge mode. I did not install it as a service.
After installing the windows software, I went to the address localhost:8096 and it says repeatedly "the site can't be reached. localhost refused to connect". I've tried it with my windows defender disabled, my browser guard disabled and malwarebytes premium disabled. I've also opened a rule for incoming and outgoing in windows defender on tcp port 8096, but since it doesn't work with defender disabled, that's not necessary. Any idea on what can be causing this? I'm not familiar with the log locations, so I might need help with that.
I've tried searching for "localhost refused to connect", but the forum brings up a post and when I click on it, it says it doesn't exist. That happens with other searches, too. I'm definitely a newbie and networking isn't my strength.
After installing the windows software, I went to the address localhost:8096 and it says repeatedly "the site can't be reached. localhost refused to connect". I've tried it with my windows defender disabled, my browser guard disabled and malwarebytes premium disabled. I've also opened a rule for incoming and outgoing in windows defender on tcp port 8096, but since it doesn't work with defender disabled, that's not necessary. Any idea on what can be causing this? I'm not familiar with the log locations, so I might need help with that.
I've tried searching for "localhost refused to connect", but the forum brings up a post and when I click on it, it says it doesn't exist. That happens with other searches, too. I'm definitely a newbie and networking isn't my strength.