Cloudflare 1033 Tunnel error

Zero Trust Cloudflare Tunnel
1

What is the name of the domain?

swe-net.nl

What is the error number?

Error 1033

What is the error message?

Error 1033 Ray ID: 8bd3bde44e20d595 • 2024-09-03 06:39:17 UTC Cloudflare Tunnel error What happened? You’ve requested a page on a website (photos.swe-net.nl) that is on the Cloudflare network. The host (photos.swe-net.nl) is configured as an Cloudflare Tunnel , and Cloudflare is currently unable to resolve it. What can I do? If you are a visitor of this website: Please try again in a few minutes. If you are the owner of this website: Ensure that cloudflared is running and can reach the network. You may wish to enable load balancing for your tunnel.

What is the issue you’re encountering

Tunnel status = DOWN

What steps have you taken to resolve the issue?

  • Removed the tunnel
  • Removed the docker container
  • Re-installed on a different machine (RPi4)
  • In Websites, removed all DNS records which were old.

What are the steps to reproduce the issue?

  • Install the container
  • Set everything up
  • Wait an hour
  • See that loading a website (e.g.) homarr.swe-net.nl gives an error message
  • Go to the Cloudflare dashboard, verify if it’s still running by going to: Zero Trust > Networks > Status = DOWN

Screenshot of the error

firefox_3LX5CrAg4O.png
firefox_3LX5CrAg4O.png1908×990 32.7 KB

2

What are the logs from cloudflared?
You can get this by sudo systemctl status cloudflared.

3

Hi, it’s been installed in a Docker Container.
The status of the Docker container is: “exited - code 2”

On inspection fo the log’s it says:
2024-09-02T17:34:17Z INF Unregistered tunnel connection connIndex=0 event=0 ip=198.41.192.37

2024-09-02T17:34:17Z WRN Failed to serve quic connection error=“Application error 0x0 (remote)” connIndex=0 event=0 ip=198.41.192.37

2024-09-02T17:34:17Z WRN Serve tunnel error error=“Application error 0x0 (remote)” connIndex=0 event=0 ip=198.41.192.37

2024-09-02T17:34:17Z INF Retrying connection in up to 1s connIndex=0 event=0 ip=198.41.192.37

2024-09-02T17:34:19Z INF Registered tunnel connection connIndex=0 connection=296e434b-b2ff-4d2f-9a00-8ae125b845d6 event=0 ip=198.41.192.37 location=ams13 protocol=quic

4

See full logs right here:

2024-09-02T14:56:21Z INF Starting tunnel tunnelID=acb4b46d-d0cb-4605-b07d-50741e6683c9
2024-09-02T14:56:21Z INF Version 2024.8.3
2024-09-02T14:56:21Z INF GOOS: linux, GOVersion: go1.22.2-devel-cf, GoArch: arm64
2024-09-02T14:56:21Z INF Settings: map[no-autoupdate:true token:*****]
2024-09-02T14:56:21Z INF Generated Connector ID: ab017105-9525-44ef-9881-bd77d67ee19c
2024-09-02T14:56:21Z INF Initial protocol quic
2024-09-02T14:56:21Z INF ICMP proxy will use 172.17.0.3 as source for IPv4
2024-09-02T14:56:21Z INF ICMP proxy will use ::1 in zone lo as source for IPv6
2024-09-02T14:56:21Z INF Starting metrics server on 127.0.0.1:32839/metrics
2024/09/02 14:56:21 failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 7168 kiB, got: 416 kiB). See https://github.com/quic-go/quic-go/wiki/UDP-Buffer-Sizes for details.
2024-09-02T14:56:21Z INF Registered tunnel connection connIndex=0 connection=b4e38652-25e5-4ef6-a1fb-dac2e3d9a25e event=0 ip=198.41.192.37 location=ams13 protocol=quic
2024-09-02T14:56:22Z INF Registered tunnel connection connIndex=1 connection=44a33a72-c44a-4375-8578-ad1bf446f0b3 event=0 ip=198.41.200.113 location=ams01 protocol=quic
2024-09-02T14:56:23Z INF Registered tunnel connection connIndex=2 connection=b40b5899-2416-4c9d-88c7-0edd7c267872 event=0 ip=198.41.192.227 location=ams15 protocol=quic
2024-09-02T14:56:24Z INF Registered tunnel connection connIndex=3 connection=9238d1a1-9b70-403f-90a2-19fb6724ff5c event=0 ip=198.41.200.63 location=ams01 protocol=quic
2024-09-02T15:00:13Z INF Updated to new configuration config="{\"ingress\":[{\"hostname\":\"homar.swe-net.nl\", \"originRequest\":{}, \"service\":\"http://192.168.0.118:7575\"}, {\"service\":\"http_status:404\"}], \"warp-routing\":{\"enabled\":false}}" version=1
2024-09-02T15:00:56Z INF Updated to new configuration config="{\"ingress\":[{\"hostname\":\"homarr.swe-net.nl\", \"originRequest\":{}, \"service\":\"http://192.168.0.118:7575\"}, {\"service\":\"http_status:404\"}], \"warp-routing\":{\"enabled\":false}}" version=2
2024-09-02T15:03:06Z INF Updated to new configuration config="{\"ingress\":[{\"hostname\":\"homarr.swe-net.nl\", \"originRequest\":{}, \"service\":\"http://192.168.0.118:7575\"}, {\"hostname\":\"photos.swe-net.nl\", \"originRequest\":{}, \"service\":\"http://192.168.0.118:2342\"}, {\"service\":\"http_status:404\"}], \"warp-routing\":{\"enabled\":false}}" version=3
2024-09-02T16:33:40Z ERR  error="Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: dial tcp 192.168.0.118:2342: connect: connection refused" connIndex=1 event=1 ingressRule=1 originService=http://192.168.0.118:2342
2024-09-02T16:33:40Z ERR Request failed error="Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: dial tcp 192.168.0.118:2342: connect: connection refused" connIndex=1 dest=https://photos.swe-net.nl/ event=0 ip=198.41.200.113 type=http
2024-09-02T16:33:40Z ERR  error="Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: dial tcp 192.168.0.118:2342: connect: connection refused" connIndex=1 event=1 ingressRule=1 originService=http://192.168.0.118:2342
2024-09-02T16:33:40Z ERR Request failed error="Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: dial tcp 192.168.0.118:2342: connect: connection refused" connIndex=1 dest=https://photos.swe-net.nl/favicon.ico event=0 ip=198.41.200.113 type=http
2024-09-02T16:50:49Z ERR  error="Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: EOF" connIndex=2 event=1 ingressRule=1 originService=http://192.168.0.118:2342
2024-09-02T16:50:49Z ERR Request failed error="Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: EOF" connIndex=2 dest=https://photos.swe-net.nl/ event=0 ip=198.41.192.227 type=http
2024-09-02T16:50:49Z ERR  error="Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: EOF" connIndex=1 event=1 ingressRule=1 originService=http://192.168.0.118:2342
2024-09-02T16:50:49Z ERR Request failed error="Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: EOF" connIndex=1 dest=https://photos.swe-net.nl/favicon.ico event=0 ip=198.41.200.113 type=http
2024-09-02T16:52:28Z ERR  error="Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: EOF" connIndex=2 event=1 ingressRule=1 originService=http://192.168.0.118:2342
2024-09-02T16:52:28Z ERR Request failed error="Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: EOF" connIndex=2 dest=https://photos.swe-net.nl/ event=0 ip=198.41.192.227 type=http
2024-09-02T16:52:28Z ERR  error="Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: EOF" connIndex=1 event=1 ingressRule=1 originService=http://192.168.0.118:2342
2024-09-02T16:52:28Z ERR Request failed error="Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: EOF" connIndex=1 dest=https://photos.swe-net.nl/favicon.ico event=0 ip=198.41.200.113 type=http
2024-09-02T16:53:07Z ERR  error="Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: EOF" connIndex=2 event=1 ingressRule=1 originService=http://192.168.0.118:2342
2024-09-02T16:53:07Z ERR Request failed error="Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: EOF" connIndex=2 dest=https://photos.swe-net.nl/ event=0 ip=198.41.192.227 type=http
2024-09-02T16:53:07Z ERR  error="Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: EOF" connIndex=1 event=1 ingressRule=1 originService=http://192.168.0.118:2342
2024-09-02T16:53:07Z ERR Request failed error="Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: EOF" connIndex=1 dest=https://photos.swe-net.nl/favicon.ico event=0 ip=198.41.200.113 type=http
2024-09-02T17:34:17Z INF Unregistered tunnel connection connIndex=0 event=0 ip=198.41.192.37
2024-09-02T17:34:17Z WRN Failed to serve quic connection error="Application error 0x0 (remote)" connIndex=0 event=0 ip=198.41.192.37
2024-09-02T17:34:17Z WRN Serve tunnel error error="Application error 0x0 (remote)" connIndex=0 event=0 ip=198.41.192.37
2024-09-02T17:34:17Z INF Retrying connection in up to 1s connIndex=0 event=0 ip=198.41.192.37
2024-09-02T17:34:19Z INF Registered tunnel connection connIndex=0 connection=296e434b-b2ff-4d2f-9a00-8ae125b845d6 event=0 ip=198.41.192.37 location=ams13 protocol=quic
5

Sanity check: Does your CNAME record have this ID in it?

Those logs show you would get a 502 error as the tunnel can’t reach the server but not 1033