Search the Community

EDIT 3: FIXED. Looks like it was a DNS issue. I restarted the DNS Resolver in pfSense, but more importantly, I did an "ipconfig /flushdns" in Windows. Then I could log in. Sorry for the false alarm. With the VPN up (either via OpenVPN on my pfSense router or via Eddie if I've got the router in "vanilla" mode), I can browse to my ISP's (Cox Communications) sites (www.cox.com), but I can't log in. This morning, I get an error page saying: "This site can’t be reached idm.east.cox.net took too long to respond. Try: Checking the connection Checking the proxy and the firewall Running Windows Network Diagnostics ERR_CONNECTION_TIMED_OUT" Last night, after two login attempts, it would just tell me I'd had too many invalid login attempts (no redirection to that error page). I talked to them and they claim they don't block access from VPNs. Since I couldn't even reset my password from their login area, they reset it for me. I still couldn't log in. Using that password on their end, they could, though. If I shut down the VPN, I can log in. Searching the internet, I find many identical posts with no solution. I can't search for "cox" on this site and "cox.com" comes up with nothing, so I'm reporting this here. I also checked AirVPN's "Checking Routes" page: https://airvpn.org/routes/ two ways. For their main site (www.cox.com), all the servers trying to get to www.cox.com are green (Direct) for "Routed To," red (Fail) for "Ping," and green (302) for "HTTP." But, for one of their separate login pages: https://www.cox.com/resaccount/sign-in.cox?onfailure=http%3A%2F%2Fwww.cox.com%2Fresaccount%2Flasvegas%2Fsign-in.cox&onsuccess=https%3A%2F%2Fwww.cox.com%2Fmyprofile%2Fhome.cox all the the "HTTP"s are red (Fail). Of course, the issue isn't browsing to cox. It's signing in. Since changing the VPN configuration on the router is fairly involved, I reverted my pfSense box back to a non-VPN save and tried different AirVPN servers in Eddie. In each case, with the VPN on, I can't log in. Here's what I tried: - my default server using the standard UDP 443, - another server using UDP 53, and - a server using UDP 443 Alternative "If your ISP blocks the standard entry IP" Since I'm new to VPNs in general, AirVPN in specific, OpenVPN and Eddie, and my pfSense box, I could be wrong about this. But, it sure looks like Cox is blocking access via VPNs regardless of what they say. As another note, last night, after several days of running with the VPN on pfSense without issue, I lost internet connection entirely. This morning, I reverted the pfSense box to a non-VPN vanilla save and got the internet back. Even with Eddie, I've got full internet access except for logging onto Cox. So, again, maybe something's wrong with what I did with pfSense. Still, I can't log into Cox with Eddie. EDIT 1: I struck through that last bit because it looks like the AirVPN client on pfSense had stalled or something. Once I restarted it, I was back up and running through that box. The issue with not being able to sign in to Cox is still valid, though. EDIT 2: I've also tried logging into Cox via my default Chrome browser and Microsoft's Edge browser (and cleared all history, etc., to boot). Same problem.