yea, you get the error code CF 1033 / http status code 530
yea, you get the error code CF 1033 / http status code 530
5 Replies
Unknown User•3y ago
Message Not Public
Sign In & Join Server To View
Tunnels establish an outbound connection to Cloudflare, you don't need to open any ports and it doesn't matter if your IP is dynamic
You're saying you have more then one server, and you don't want one of them going down making all your web servers inaccessible?
or.. can you explain your use case a bit more?
Where is the tunnel running?
If you have the tunnel and your web server running on a rented VPS for example, then no the tunnel would still be active
If you are self-hosting your web server and the tunnel on your computer, then yea the tunnel would be dead, so would your web server
The tunnel is just a connector to your web server, it can't bring what's dead back to life, it's like a reverse proxy with some special features
What do you mean "serverless"?
You're asking if you can use a serverless function, like a cf worker, as a reverse proxy?
If so, yea you can, but Tunnels are more special then that. A Worker could connect to a normal origin and act as a reverse proxy.
Cloudflare -> Worker -> (Logic) -> Normal Origin, established connection inbound over 80/443
Tunnels connect outbound to Cloudflare. So unlike with a normal origin, you don't need to have a static IP, or port forward, or worry about https. The tunnel creates a secure tunnel/connection back to Cloudflare's edge, as an outbound connection. Then when requests come to Cloudflare's proxy for the tunnels' hostname, CF just forwards the requests down the tunnel, and cloudflared (the actual service running on your infrastructure) connects to your configured web server
Cloudflare -> Tunnel Connection -> cloudflared (running on your server) -> Web Server
Unknown User•3y ago
Message Not Public
Sign In & Join Server To View
Have you tried deleting the cache folder?