The internal network penetration cannot be accessed normally.
I have recreated the tunnel and redeployed the service.
Just access it directly.
What troubleshooting steps have you tried already regarding 1033 error? 
1033 error means your tunnel wasn’t connected to our Cloudflare network at the moment.
What happens if you can run cloudflared tunnel list to see the list of connections from your tunnel?
Did you tried to re-authenticate yourself again with cloudflared tunnel login?
Are you using the cloudflare Load Balancer product as well or not?
May I ask if you’ve created and manage your cloudflared tunnel via Dashboard (remote) or locally (CLI)?
Do you know if the requests reached your tunnel, do you see them if you’re running local tunnel (via CLI)?, and was the tunnel able to connect with your service?
Do you have network or firewall or even routing policies that can block connections from and to the tunnel?
Which protocol are you using for your tunnel? QUIC? Try with http2 instead.
This topic was automatically closed after 15 days. New replies are no longer allowed.