403 Forbidden. Your server is not able to communicate with generatepress.com.

Hi there,

can you provide your server IP address so we can check if its being blocked.

The server IP is 69.163.224.70.

Hi there,

I just checked that IP with our hosting and they confirmed that it's not blocked on our end.

Can your hosting confirm that they can reach generatepress.com via cURL on your server?

If so, can they share the traceroute so we can share it with our hosting?

Also, are there any recent errors in the error_log file on the server that look relevant?

Thanks!

I had already contacted them before contacting you. They said that cURL is automatically turned on by default on their servers. They updated the permissions to my domain, and I tried entering again, still receiving the 403 Forbidden error.

Here are the results of the traceroute:

traceroute to generatepress.com (162.159.135.42), 30 hops max, 60 byte packets
1 ip-69-163-224-1.dreamhost.com (69.163.224.1) 1.218 ms 1.158 ms 1.125 ms
2 pdx1-cr-2.sd.dreamhost.com (66.33.200.3) 0.813 ms 0.791 ms 0.760 ms
3 pdx1-bdr-1.sd.dreamhost.com (66.33.200.0) 0.730 ms 0.699 ms 0.669 ms
4 pdx1-bdr-2.sd.dreamhost.com (66.33.200.1) 0.639 ms 0.608 ms 0.660 ms
5 be5106.ccr51.pdx02.atlas.cogentco.com (38.142.108.113) 175.537 ms 175.518 ms 175.390 ms
6 be2216.ccr21.pdx01.atlas.cogentco.com (154.54.31.157) 1.291 ms 1.535 ms 1.560 ms
7 be2670.ccr22.sea02.atlas.cogentco.com (154.54.42.149) 5.628 ms 5.544 ms 5.510 ms
8 38.142.50.154 (38.142.50.154) 5.777 ms 5.705 ms 5.907 ms
9 162.159.135.42 (162.159.135.42) 5.393 ms 5.417 ms 5.456 ms

Hi there,

I shared this with our hosting (Kinsta) support and they escalated it to their dev team. They weren't able to find any blocks on our end at all. They did mention the traceroute doesn't seem to be complete and that they'd be willing to look at the entire one if we can provide it.

Hello,

I ran the traceroute again, and it's similar to the one that I gave you:

traceroute to generatepress.com (162.159.135.42), 30 hops max, 60 byte packets
1 ip-69-163-224-1.dreamhost.com (69.163.224.1) 1.822 ms 1.757 ms 1.722 ms
2 pdx1-cr-2.sd.dreamhost.com (66.33.200.3) 0.790 ms 0.768 ms pdx1-cr-1.sd.dreamhost.com (66.33.200.2) 0.734 ms
3 pdx1-bdr-1.sd.dreamhost.com (66.33.200.0) 0.701 ms 0.667 ms 0.632 ms
4 pdx1-bdr-2.sd.dreamhost.com (66.33.200.1) 0.597 ms 0.563 ms 0.529 ms
5 be5106.ccr51.pdx02.atlas.cogentco.com (38.142.108.113) 1.150 ms 1.116 ms 1.075 ms
6 be2216.ccr21.pdx01.atlas.cogentco.com (154.54.31.157) 560.191 ms 1.390 ms 1.341 ms
7 be2670.ccr22.sea02.atlas.cogentco.com (154.54.42.149) 4.936 ms 4.947 ms 4.973 ms
8 38.142.50.154 (38.142.50.154) 8.592 ms 8.551 ms 8.500 ms
9 162.159.135.42 (162.159.135.42) 5.325 ms 5.538 ms 5.235 ms

I copy and pasted all that was returned back to me from the web server after the traceroute completed.

Hmm, they weren't able to find anything there.

We have had this issue with Dreamhost quite a bit, unfortunately. It's never been clear if there's some sort of internal block of their end or on Kinsta's end.

I wonder if there are any other IPs for your server that we can check? Or is that the only one?