Issue connecting to home server via newly created (through Cloudflare) domain name/Cloudflare tunnel
What steps have you taken to resolve the issue?
I am attempting to set up Cloudflare tunnels due to my ISP recently changing to CGNAT and I can no longer access a home server via remote login. My public IP address assigned by my ISP is now useless due to this change. It was recommended that instead of changing ISPs, that I use Cloudflare tunnels. I’m not experienced in setting this up, so I am working off of YouTube vids of how to do it. As part of the process, I created a domain name which I purchased through CIoudflare… In setting up the DNS Records for the new domain name, I get the following message at the top of the page: Recommended steps to complete zone set-up: Add an A, AAAA, or CNAME record for www so that myhomeserver.net will resolve. I also get the same message for adding a www to the domain name to resolve.
When I attempt to create the recommended records, an IP address is requested. If I enter in my useless ISP Public address, I can see myhomeserverdotnet in DNS searches, but…I can’t make login to my server using the newly create subdomain for it off of my main domain name. Is this because I am using the “no good” (for remote login purposes) public IP address issued by my CGNAT ISP?
I have set up a connection, via docker, from my server to Cloudflare. I can see that tunnel on Cloudflare and it is active and healthy. However, I can’t access the server. I feel it has something to do with the DNS record using my IPv4 public address (which , again, is issued from a CGNAT ISP).
I’m a home user, trying to set this up via YouTube vids and web articles. Pretty sure I’m almost there, but just need to figure this piece out. Any help is greatly appreciated.
What feature, service or problem is this related to?
The domain you gave myhomeserver.net seems to be someone else’s domain – registered years ago and not through Cloudflare and doesn’t use Cloudflare at all.
If you don’t want to share your own domain publicly, don’t share some innocent person’s domain either. Use example.com instead… which is a reserved domain meant for this very purpose.
Ignore these…
… and continue to setup your tunnel following whichever tututial you’re using, or Cloudflare’s official guide here: Set up your first tunnel
If you added any DNS records yourself, remove them completely.
Cloudflare adds the necessary DNS record(s) automatically when you create the tunnel.
And if you want us to look over your domain’s DNS records for you, you need the share the actual domain. If you setup the tunnel with a subdomain, give the full subdomain.
I am showing the docker is running on the server/nas and that the connection is healthy on Cloudflare. I just can’t remote login to my nas yet, so I was wondering if the IP address in the DNS records (being that it is issued by a CGNAT ISP) was the issue.
So, again, I appreciate the response. I’ll go delete any DNS records I created and leave what Isee that Cloudflare created automatically. I’ll also check out the tunnels guide you provided.
Any additional comments or assistance is appreciated.