I’m running a hobby project with a Raspberry Pi on my home network. I’ve gotten apache up and running, and I can connect to it with its local IP. I added a port forward to port 80, and I can connect to its public IP over a VPN. However, I can’t access it through the domain I set up.
I added an A record pointing to the public IP and I keep getting error 522. I haven’t set up any whitelisting/blacklisting yet, so nothing should block Cloudflare on the Pi’s side. The only other thing I can think of is my ISP is blocking Cloudflare, but it would alert me when it blocks an IP from accessing it.
The only other thing I can think of is if there are packet drops, which I heavily doubt as I can connect to its public IP over a VPN.
I did try running a traceroute from the Pi to a few of Cloudflare’s IPs. 188.8.131.52 and 184.108.40.206 give me a random mess that looks like Comcast is running it through a bunch of its own servers, while 220.127.116.11 is accessible in about 7 hops.
Is the issue on my side, Comcast’s, or Cloudflare’s?
I would suggest to put the binary file in /usr/local/bin/ folder (this is the default installation directory for cloudflared).
And, port 80 can be closed on the router.
Some quick tips:
First login to your Cloudflare account using cloudflared login
Then, create a new tunnel using cloudflared tunnel create my_tunnel
Next, run the tunnel using cloudflared tunnel run --url localhost:80 my_tunnel
You can change my_tunnel to any name you like.
Lastly, run cloudflared tunnel route dns my_tunnel www.example.com, where you can change www.example.com to your own domain name.