Starting this morning, I haven't been able to connect to the Washington Post on any of my home computers (or phone) via WiFi. I can connect on cellular, which tells me there's potentially a Comcast issue.
I receive this error message:
An error occurred while processing your request.
Is anyone else having similar problems?
Try disabling the Xfi Advanced Security feature as a work-around for now and see. It's buggy ! And there is currently no way for an end-user to be able to whitelist anything;
@SueMcE wrote: Starting this morning, I haven't been able to connect to the Washington Post ...
The home page at https://www.washingtonpost.com is working for me. When one customer cannot reach a site but others can, it usually means the site is blocking that customer's public Comcast IP. You can look up your IP at https://www.google.com/search?q=what+is+my+IP.
What does a trace to www.washingtonpost.com show? In Windows, open a Command Prompt window, enter
tracert -4 www.washingtonpost.com
and post the output. Mine looks like:
C>tracert -4 www.washingtonpost.com Tracing route to e9631.j.akamaiedge.net [22.214.171.124] over a maximum of 30 hops: 1 17 ms 6 ms 6 ms router1 [192.168.1.1] 2 23 ms 20 ms 14 ms 126.96.36.199 3 21 ms 20 ms 20 ms 188.8.131.52 4 * 24 ms 14 ms 184.108.40.206 5 16 ms 15 ms 15 ms 220.127.116.11 6 25 ms 23 ms 23 ms 18.104.22.168 7 32 ms 36 ms 26 ms 22.214.171.124 8 28 ms 33 ms 26 ms a23-216-153-53.deploy.static.akamaitechnologies.com [126.96.36.199] Trace complete.