403 errors with Motorola MG7700

Hello,

I am receiving random 403 errors on every device on my home network. For instance, I am receiving a 403 error whenever I visit petfinder.com or onlyfans.com(long story) on two different laptops and two different cell phones that are on the network. The issue persists on WiFi and ethernet. If I use mobile data or another network then I am able to browse to petfinder.com just fine. .

I have tried factory resetting the router and changing the DNS to three different providers but nothing has worked.

I am not sure if it is related but now I am not able to login to my company's OKTA so this is now a priority for me. OKTA recognizes my username by showing me my security image but I am not able to get to the next screen to enter my password and I'm met with a "Unable to sign in" error message.

I am not using a VPN but I have setup a web proxy and it is not capturing the OKTA or petfinder.com errors which leads me to believe traffic is not getting passed the router.

[root@NBWIN0216 ~]$ curl -v petfinder.com*   Trying 18.211.161.156:80...* Connected to petfinder.com (18.211.161.156) port 80 (#0)> GET / HTTP/1.1> Host: petfinder.com> User-Agent: curl/7.82.0> Accept: */*>* Mark bundle as not supporting multiuse< HTTP/1.1 403 Forbidden< Server: awselb/2.0< Date: Tue, 24 May 2022 22:22:35 GMT< Content-Type: text/html< Content-Length: 118< Connection: keep-alive<<html><head><title>403 Forbidden</title></head><body><center><h1>403 Forbidden</h1></center></body></html>* Connection #0 to host petfinder.com left intact

[root@NBWIN0216 squid]# traceroute petfinder.comtraceroute to petfinder.com (52.7.109.30), 30 hops max, 60 byte packets 1  _gateway (172.24.144.1)  0.511 ms  0.556 ms  0.562 ms 2  192.168.0.1 (192.168.0.1)  23.991 ms  21.079 ms  23.983 ms 3  96.120.75.9 (96.120.75.9)  27.477 ms  31.958 ms  31.954 ms 4  24.124.225.53 (24.124.225.53)  28.439 ms  32.409 ms  31.085 ms 5  68.86.210.205 (68.86.210.205)  29.793 ms  32.365 ms  29.786 ms 6  162.151.210.53 (162.151.210.53)  31.135 ms  32.084 ms  32.043 ms 7  be-98-ar03.plainfield.nj.panjde.comcast.net (68.85.35.37)  32.714 ms  12.426 ms  11.903 ms 8  be-31133-cs03.newark.nj.ibone.comcast.net (96.110.42.41)  13.135 ms be-31143-cs04.newark.nj.ibone.comcast.net (96.110.42.45)  31.286 ms be-31133-cs03.newark.nj.ibone.comcast.net (96.110.42.41)  31.268 ms 9  be-2102-pe02.newark.nj.ibone.comcast.net (96.110.37.50)  31.313 ms be-2302-pe02.newark.nj.ibone.comcast.net (96.110.37.58)  33.269 ms be-3111-pe11.philadelphia.pa.ibone.comcast.net (96.110.36.130)  31.677 ms10  50.242.150.106 (50.242.150.106)  37.602 ms 23.30.207.38 (23.30.207.38)  35.179 ms  31.648 ms11  52.93.60.245 (52.93.60.245)  35.227 ms * *12  * * 52.93.60.81 (52.93.60.81)  31.595 ms13  * * *14  * * *15  * * *16  * * *17  * * *18  * * *19  52.93.28.222 (52.93.28.222)  20.086 ms * *20  * * *21  * * *22  * * *23  * * *24  * * *25  * * *26  * * *27  * * *28  * * *29  * * *30  * * *

Thanks,

[Edit: PII]

Responses

user_536f94

Visitor

•

7 Messages

3 years ago

Today, it is working, but I am positive that it will happen again in the future.

XfinityMarcos

Official Employee

•

2.3K Messages

Hello, @user_536f94, thank you for reaching out to our forum for help with that error code you're running into. I'm happy to hear things cleared up for you, hopefully, it's remained that way. Has that error code returned? Also, did you take any other steps aside from what you outlined previously to clear that error?

I am an Official Xfinity Employee.
Official Employees are from multiple teams within Xfinity: CARE, Product, Leadership.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Please, mark a reply as the Accepted Answer. tick

3 years ago

user_536f94

Visitor

•

7 Messages

3 years ago

Hello,

The 403 error with petfinder.com has popped up again and I have found that hudsoncountyclerk.org is also giving me a 403(I am sure there are others). Just to reiterate, changing browsers(chrome/edge/firefox) or devices does not fix the issue. I am pretty positive it is a networking issue because if I take the device to another WiFi or mobile network the URLs will not throw a 403 error.

[root@NBWIN0216 ~]$ traceroute petfinder.com
traceroute to petfinder.com (18.211.161.156), 30 hops max, 60 byte packets
 1  _gateway (172.23.0.1)  2.340 ms  1.840 ms  1.836 ms
 2  192.168.0.1 (192.168.0.1)  2.478 ms  10.195 ms  10.190 ms
 3  96.120.75.9 (96.120.75.9)  41.745 ms  12.916 ms  18.426 ms
 4  24.124.225.53 (24.124.225.53)  42.139 ms  42.133 ms  42.128 ms
 5  68.86.210.205 (68.86.210.205)  41.789 ms  12.813 ms  41.773 ms
 6  162.151.210.53 (162.151.210.53)  41.959 ms  34.632 ms  34.611 ms
 7  be-98-ar03.plainfield.nj.panjde.comcast.net (68.85.35.37)  34.613 ms  37.695 ms *
 8  be-31143-cs04.newark.nj.ibone.comcast.net (96.110.42.45)  19.611 ms  26.325 ms be-31123-cs02.newark.nj.ibone.comcast.net (96.110.42.37)  26.345 ms
 9  be-2302-pe02.newark.nj.ibone.comcast.net (96.110.37.58)  26.302 ms be-2402-pe02.newark.nj.ibone.comcast.net (96.110.37.62)  26.292 ms be-3411-pe11.philadelphia.pa.ibone.comcast.net (96.110.36.142)  26.292 ms
10  50.242.150.106 (50.242.150.106)  26.282 ms 23.30.207.38 (23.30.207.38)  26.261 ms 50.242.150.106 (50.242.150.106)  26.262 ms
11  * * *
12  * 52.93.60.67 (52.93.60.67)  30.694 ms 52.93.60.131 (52.93.60.131)  30.520 ms
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  52.93.28.126 (52.93.28.126)  21.417 ms  19.154 ms *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *

[root@NBWIN0216 ~]$ curl -v https://www.petfinder.com/
*   Trying 52.7.109.30:443...
* Connected to www.petfinder.com (52.7.109.30) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
*  CAfile: /etc/pki/tls/certs/ca-bundle.crt
*  CApath: none
* TLSv1.0 (OUT), TLS header, Certificate Status (22):
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS header, Certificate Status (22):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS header, Certificate Status (22):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS header, Certificate Status (22):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS header, Certificate Status (22):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS header, Certificate Status (22):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS header, Finished (20):
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS header, Certificate Status (22):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS header, Finished (20):
* TLSv1.2 (IN), TLS header, Certificate Status (22):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=www.petfinder.com
*  start date: Sep 11 00:00:00 2021 GMT
*  expire date: Oct 10 23:59:59 2022 GMT
*  subjectAltName: host "www.petfinder.com" matched cert's "www.petfinder.com"
*  issuer: C=US; O=Amazon; OU=Server CA 1B; CN=Amazon
*  SSL certificate verify ok.
* Using HTTP2, server supports multiplexing
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* h2h3 [:method: GET]
* h2h3 [:path: /]
* h2h3 [:scheme: https]
* h2h3 [:authority: www.petfinder.com]
* h2h3 [user-agent: curl/7.82.0]
* h2h3 [accept: */*]
* Using Stream ID: 1 (easy handle 0x558e4ba0f430)
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
> GET / HTTP/2
> Host: www.petfinder.com
> user-agent: curl/7.82.0
> accept: */*
>
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
< HTTP/2 403
< server: awselb/2.0
< date: Wed, 01 Jun 2022 15:30:36 GMT
< content-type: text/html
< content-length: 118
<
<html>
<head><title>403 Forbidden</title></head>
<body>
<center><h1>403 Forbidden</h1></center>
</body>
</html>
* Connection #0 to host www.petfinder.com left intact

[root@NBWIN0216 ~]$ traceroute hudsoncountyclerk.org
traceroute to hudsoncountyclerk.org (184.72.232.49), 30 hops max, 60 byte packets
 1  _gateway (172.23.0.1)  0.802 ms  0.964 ms  0.771 ms
 2  192.168.0.1 (192.168.0.1)  11.723 ms  16.005 ms  11.710 ms
 3  96.120.75.9 (96.120.75.9)  18.197 ms  15.945 ms  15.939 ms
 4  24.124.225.53 (24.124.225.53)  18.573 ms  18.254 ms  14.497 ms
 5  68.86.210.205 (68.86.210.205)  18.487 ms  14.521 ms  18.189 ms
 6  162.151.210.53 (162.151.210.53)  19.068 ms  20.777 ms  20.761 ms
 7  be-98-ar03.plainfield.nj.panjde.comcast.net (68.85.35.37)  19.375 ms *  15.855 ms
 8  be-31143-cs04.newark.nj.ibone.comcast.net (96.110.42.45)  16.974 ms  18.544 ms  18.534 ms
 9  be-3411-pe11.philadelphia.pa.ibone.comcast.net (96.110.36.142)  26.978 ms be-2102-pe02.newark.nj.ibone.comcast.net (96.110.37.50)  16.933 ms be-2302-pe02.newark.nj.ibone.comcast.net (96.110.37.58)  17.127 ms
10  50.242.150.106 (50.242.150.106)  26.343 ms 50.242.150.182 (50.242.150.182)  26.305 ms *
11  * * *
12  52.93.60.99 (52.93.60.99)  26.262 ms * 52.93.60.143 (52.93.60.143)  31.947 ms
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *

[root@NBWIN0216 ~]$ curl -v  https://www.hudsoncountyclerk.org/
*   Trying 52.1.195.216:443...
* Connected to www.hudsoncountyclerk.org (52.1.195.216) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
*  CAfile: /etc/pki/tls/certs/ca-bundle.crt
*  CApath: none
* TLSv1.0 (OUT), TLS header, Certificate Status (22):
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS header, Certificate Status (22):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS header, Certificate Status (22):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS header, Certificate Status (22):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS header, Certificate Status (22):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS header, Certificate Status (22):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS header, Finished (20):
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS header, Certificate Status (22):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS header, Finished (20):
* TLSv1.2 (IN), TLS header, Certificate Status (22):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=ssl.connect.clarityelections.com
*  start date: Jan 13 19:47:50 2022 GMT
*  expire date: Feb 14 19:47:50 2023 GMT
*  subjectAltName: host "www.hudsoncountyclerk.org" matched cert's "www.hudsoncountyclerk.org"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
* Using HTTP2, server supports multiplexing
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* h2h3 [:method: GET]
* h2h3 [:path: /]
* h2h3 [:scheme: https]
* h2h3 [:authority: www.hudsoncountyclerk.org]
* h2h3 [user-agent: curl/7.82.0]
* h2h3 [accept: */*]
* Using Stream ID: 1 (easy handle 0x561fb8252430)
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
> GET / HTTP/2
> Host: www.hudsoncountyclerk.org
> user-agent: curl/7.82.0
> accept: */*
>
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
< HTTP/2 403
< server: awselb/2.0
< date: Wed, 01 Jun 2022 15:29:07 GMT
< content-type: text/html
< content-length: 118
<
<html>
<head><title>403 Forbidden</title></head>
<body>
<center><h1>403 Forbidden</h1></center>
</body>
</html>
* Connection #0 to host www.hudsoncountyclerk.org left intact

XfinityBenjaminM

Official Employee

•

2K Messages

@user_536f94 Hello, we just wanted to check back in with you and see if you were able to review the information that BruceW provided in their comment? If you are still experiencing any issues, please let us know.

3 years ago

user_536f94

Visitor

•

7 Messages

Hello,

I have to reopen this because I'm having issues again today with petfinder.com and academy-team.appway.com. Both are giving me 403 errors.

Since opening this issue I have started renting a new router/modem from Xfinity. The Arris Touchstone TG1682G.

There must be something downstream causing this issue.

NBMAC0052:~ user$ traceroute petfinder.com
traceroute: Warning: petfinder.com has multiple addresses; using 52.205.65.91
traceroute to petfinder.com (52.205.65.91), 64 hops max, 52 byte packets
 1  10.0.0.1 (10.0.0.1)  6.378 ms  5.771 ms  24.592 ms
 2  96.120.75.9 (96.120.75.9)  18.957 ms  19.886 ms  12.243 ms
 3  24.124.225.53 (24.124.225.53)  18.722 ms  20.274 ms  14.099 ms
 4  68.86.210.205 (68.86.210.205)  13.492 ms  13.651 ms  13.762 ms
 5  162.151.210.53 (162.151.210.53)  20.331 ms  14.965 ms  16.123 ms
 6  be-98-ar03.plainfield.nj.panjde.comcast.net (68.85.35.37)  16.444 ms  14.652 ms  16.992 ms
 7  be-31133-cs03.newark.nj.ibone.comcast.net (96.110.42.41)  17.152 ms
    be-31113-cs01.newark.nj.ibone.comcast.net (96.110.42.33)  19.611 ms
    be-31143-cs04.newark.nj.ibone.comcast.net (96.110.42.45)  45.074 ms
 8  be-3211-pe11.philadelphia.pa.ibone.comcast.net (96.110.36.134)  22.994 ms
    be-2102-pe02.newark.nj.ibone.comcast.net (96.110.37.50)  20.536 ms
    be-2302-pe02.newark.nj.ibone.comcast.net (96.110.37.58)  17.198 ms
 9  50.242.150.182 (50.242.150.182)  46.082 ms
    50.242.150.106 (50.242.150.106)  23.386 ms  18.553 ms
10  * * 52.93.60.223 (52.93.60.223)  34.049 ms
11  52.93.60.45 (52.93.60.45)  28.264 ms
    52.93.60.147 (52.93.60.147)  22.360 ms *
12  * * *

NBMAC0052:~user$ traceroute academy-team.appway.com
traceroute: Warning: academy-team.appway.com has multiple addresses; using 52.31.200.44
traceroute to academy-team-2115783917.eu-west-1.elb.amazonaws.com (52.31.200.44), 64 hops max, 52 byte packets
 1  10.0.0.1 (10.0.0.1)  5.561 ms  5.224 ms  3.737 ms
 2  96.120.75.9 (96.120.75.9)  14.732 ms  12.308 ms  13.960 ms
 3  24.124.225.53 (24.124.225.53)  14.670 ms  13.520 ms  13.849 ms
 4  68.86.210.205 (68.86.210.205)  14.357 ms  13.012 ms  13.109 ms
 5  162.151.210.53 (162.151.210.53)  15.539 ms  14.273 ms  17.049 ms
 6  be-98-ar03.plainfield.nj.panjde.comcast.net (68.85.35.37)  15.645 ms  15.492 ms  15.964 ms
 7  be-31123-cs02.newark.nj.ibone.comcast.net (96.110.42.37)  17.517 ms
    be-31133-cs03.newark.nj.ibone.comcast.net (96.110.42.41)  16.047 ms
    be-31143-cs04.newark.nj.ibone.comcast.net (96.110.42.45)  17.053 ms
 8  be-2411-pe11.newark.nj.ibone.comcast.net (96.110.33.254)  16.915 ms
    be-2311-pe11.newark.nj.ibone.comcast.net (96.110.33.250)  16.649 ms
    be-2411-pe11.newark.nj.ibone.comcast.net (96.110.33.254)  15.537 ms
 9  66.208.229.226 (66.208.229.226)  15.506 ms  15.209 ms  15.982 ms
10  ae-1.r21.nwrknj03.us.bb.gin.ntt.net (129.250.6.86)  16.422 ms  14.268 ms  15.987 ms
11  ae-9.r20.londen12.uk.bb.gin.ntt.net (129.250.6.146)  93.381 ms
    ae-11.r20.parsfr04.fr.bb.gin.ntt.net (129.250.4.195)  95.821 ms  88.372 ms
12  ae-13.a03.londen12.uk.bb.gin.ntt.net (129.250.3.249)  96.240 ms
    ae-0.a00.parsfr05.fr.bb.gin.ntt.net (129.250.2.151)  113.267 ms  94.277 ms
13  212.119.4.66 (212.119.4.66)  87.364 ms
    ae-0.amazon.parsfr04.fr.bb.gin.ntt.net (128.241.3.18)  90.201 ms
    212.119.4.70 (212.119.4.70)  82.524 ms
14  * * *
15  * * *
16  * * *

3 years ago

user_536f94

Visitor

•

7 Messages

I am also currently getting a 403 error when trying to access this site:

https://www.hudsoncountyclerk.org/

3 years ago

CCTimothy

Valued Contributor

•

406 Messages

Thank you for contacting us on the forums, @user_536f94! I'm sorry that you're still having problems with these websites. Please send us a direct message so we can dig deeper.

To send a direct message [private message]:

Click "Sign In" if necessary
Click the "Direct Message" icon or https://forums.xfinity.com/direct-messaging
Click the "New message" (pencil and paper) icon
The "To:" line prompts you to "Type the name of a person". Instead, type "Xfinity Support" there.
- As you are typing a drop-down list appears. Select "Xfinity Support" from that list.
- An "Xfinity Support" graphic replaces the "To:" line.
Type your message in the text area near the bottom of the window
Press Enter to send it

I no longer work for Comcast.

3 years ago

BruceW

Gold Problem Solver

•

26.3K Messages

3 years ago

... I am receiving random 403 errors ...

403 "Not authorized/You don't have permission" messages are issued by the target servers, not by Comcast. They usually mean the servers have seen traffic from your public IP address that for whatever reason, they don't like. Normally I'd suggest changing the MAC address of your router and rebooting, to force Comcast's DHCP servers to issue a new public IP to see if that clears the problem, but I can't find a way to change the MAC address of the router component of the MG7700.

However you could still conduct this test by putting the MG7700 in bridge mode (see "MG7700 - Put into bridge mode" on https://help.motorolanetwork.com/hc/en-us/articles/115007129847-How-Do-I-Put-My-Cable-Modem-Router-Combo-also-called-a-Gateway-into-Bridge-Mode-So-I-Can-Connect-Another-Router-behind-It-). Then, with an Ethernet-cabled laptop or desktop connected to the gateway, when you reboot the MG7700 it should present the laptop's MAC to Comcast's DHCP server which should then issue a new public IP address.

If you do that do you still get the 403 errors from the problem sites?

Please be aware that there are 2 kinds of responses in this Forum: Replies and Comments. When you Comment on a post by scrolling down to "Comment on this post here...", I am notified of your response. But if you select Reply, I am NOT notified and may not be aware of your response.

(edited)

zip21222

Contributor

•

160 Messages

3 years ago

@user_536f94

Interestingly, every one of the sites you've mentioned are hosted by Amazon Web Services.

Perhaps it would be worth asking Amazon if they know of any Comcast<->AWS issues, or have any additional troubleshooting tools for you.

HTH

BruceW

Gold Problem Solver

•

26.3K Messages

3 years ago

... the sites you've mentioned are hosted by Amazon Web Services ...

Please see https://community.akamai.com/customers/s/article/Why-is-Akamai-blocking-me?language=en_US (thanks to @Hemingray42 for finding that page). I'm guessing (maybe incorrectly) that AWS is similar.

"Access Denied / You don't have permission" messages are typically issued by the destination site. A person or a program is using an Internet resource in a way the manager of that resource doesn't like. Customers having this problem will need to contact the site's admins for help with this.

Please be aware that there are 2 kinds of responses in this Forum: Replies and Comments. When you Comment on a post by scrolling down to "Comment on this post here...", I am notified of your response. But if you select Reply, I am NOT notified and may not be aware of your response.

(edited)

user_536f94

Visitor

•

7 Messages

2 years ago

I am now getting denied by Venmo(https://venmo.com/) with this message...

403 ERROR
The request could not be satisfied.
Request blocked. We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.
If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.
Generated by cloudfront (CloudFront)
Request ID: bTm8Pnli-PzvZ2Ku28ZbAxZFhfZL1pEhyW0LrMP4MqpF-rNIGzNNeA==

(edited)

zip21222

Contributor

•

160 Messages

2 years ago

@user_536f94

Not the most informative error message, but I think what it's saying is that Cloudflare hosts the Venmo site and that Venmo's server is either rejecting or ignoring your request.

There's multiple possible reasons for this, but I think the most likely is that Venmo thinks the address you're connecting from has a bad reputation for some reason.

First thing I'd do is contact Venmo directly if possible (have your public IP handy).

HTH

BruceW

Gold Problem Solver

•

26.3K Messages

2 years ago

... I think what it's saying is that Cloudflare hosts the Venmo site ...

"CloudFront" <> "Cloudflare". "CloudFront" is an Amazon Web Services offering. "Cloudflare" is a completely separate corporation. See https://en.wikipedia.org/wiki/Amazon_CloudFront and https://en.wikipedia.org/wiki/Cloudflare.

But I agree with your suggestion that the next step is to ask Venmo's admins for help with the problem. The user will probably need their public IP, which they can get from https://www.google.com/search?q=what+is+my+IP.

Please be aware that there are 2 kinds of responses in this Forum: Replies and Comments. When you Comment on a post by scrolling down to "Comment on this post here...", I am notified of your response. But if you select Reply, I am NOT notified and may not be aware of your response.

zip21222

Contributor

•

160 Messages

@BruceW

Whoops!

Thx for looking out.

2 years ago

jasongil

Visitor

•

15 Messages

2 years ago

I'd go with with with BruceW suggested - try and get a new IP.

As others have pointed out, the common thread seems to be that the sites are hosted in AWS with CloudFront. A feature of that is allowing / denying IPs based on reputation. Perhaps whoever had that IP before you was malicious which led to a low reputation and it no longer being trusted.

More info: https://docs.aws.amazon.com/waf/latest/developerguide/aws-managed-rule-groups-ip-rep.html#aws-managed-rule-groups-ip-rep-amazon

user_536f94

Visitor

•

7 Messages

@jasongil Shouldn't I have been given a new IP after setting up the new modem/router from Xfinity?

2 years ago

Your Home Network

user_536f94

403 errors with Motorola MG7700

user_536f94

XfinityMarcos

user_536f94

XfinityBenjaminM

user_536f94

user_536f94

CCTimothy

BruceW

Please be aware that there are 2 kinds of responses in this Forum: Replies and Comments. When you Comment on a post by scrolling down to "Comment on this post here...", I am notified of your response. But if you select Reply, I am NOT notified and may not be aware of your response.

zip21222

BruceW

Please be aware that there are 2 kinds of responses in this Forum: Replies and Comments. When you Comment on a post by scrolling down to "Comment on this post here...", I am notified of your response. But if you select Reply, I am NOT notified and may not be aware of your response.

user_536f94

zip21222

BruceW

Please be aware that there are 2 kinds of responses in this Forum: Replies and Comments. When you Comment on a post by scrolling down to "Comment on this post here...", I am notified of your response. But if you select Reply, I am NOT notified and may not be aware of your response.

zip21222

jasongil

user_536f94

New to the Community?