tunnel not accessible.. synology container manager
as the title suggest I setup a tunnel and it shows active and getting all connector info but can't be accessed from the web
so I went and reseved a free domain from Cloudns.net, changed the ns records to match with what's provided from cloudflare, then created a tunnel and installed cloudflared in a container in y synology... now it shows healthy in the tunnels as shown in the picture attached and the browser can't access it yet
9 Replies
@Aku
Hmm
Tbh I have no idea
Sorry
maybe synology firewall is blocking it
Synology firewall is down..
Synology is accessible from local networks and through VPN connections… I don’t think that’s the issue
No worries ۔۔۔
show me the setup in the "public hostname" tab of your tunnel
Let’s see..
There’s something I did wrong maybe but dnschecker points to a correct dns records, and as I mentioned in the first post that domain is a free domain provided by cloudns.net
I added 2 ns records ns records provided by Cloudflare and it shows active ✅ in Cloudflare dashboard
alright.. how is that possible to achieve? or if there's a keywords to search or a tutorial on YouTube to follow since I'm doing an experimental project and I'm completely noob here
can be done... then how do I transfer them to cloudflare?
appreciate your precious time
so I bought a domain from cloudflare which doesn't need to be transferred, but now when I create a tunnel and configure cloudflared container it doesn't run throwing an error: invalid token... of course I double checked the token, refreshed the token, recreated the tunnel from scratch, and tried setting up a cloudflare package from Package center... I keep getting the same error and the status shows inactive!