Cannot access Portainer instance via Cloudflare Tunnel getting 502 error

Hi @fritex ,
I’ve the same issue but it’s weird. Some tunnels with subdomain does working well, but the root domain (which is my wordpress blog) is not. I’ve tried to use the same running tunnel but no hope with 502 error. My logs:

2022-11-13T15:27:42Z INF Starting tunnel tunnelID=3336afb3-deea-42d9-ae29-cd8407a62d8b
2022-11-13T15:27:42Z INF Cannot determine default configuration path. No file [config.yml config.yaml] in [~/.cloudflared ~/.cloudflare-warp ~/cloudflare-warp /etc/cloudflared /usr/local/etc/cloudflared]
2022-11-13T15:27:42Z INF Version 2022.10.3
2022-11-13T15:27:42Z INF GOOS: linux, GOVersion: go1.19.2, GoArch: amd64
2022-11-13T15:27:42Z INF Settings: map[no-autoupdate:true token:*****]
2022-11-13T15:27:42Z INF Generated Connector ID: ea38d5ba-c72f-4252-8b95-16ac5cca59a2
2022-11-13T15:27:42Z INF Will be fetching remotely managed configuration from Cloudflare API. Defaulting to protocol: quic
2022-11-13T15:27:42Z INF Initial protocol quic
2022-11-13T15:27:42Z INF ICMP proxy will use 172.17.0.3 as source for IPv4
2022-11-13T15:27:42Z INF ICMP proxy will use :: as source for IPv6
2022-11-13T15:27:42Z INF Starting metrics server on 127.0.0.1:42267/metrics
2022/11/13 15:27:42 failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 2048 kiB, got: 416 kiB). See https://github.com/lucas-clemente/quic-go/wiki/UDP-Receive-Buffer-Size for details.
2022-11-13T15:27:43Z INF Connection 642d03cd-9d02-4659-b842-215f85a9017e registered connIndex=0 ip=198.41.200.193 location=SIN
2022-11-13T15:27:44Z INF Updated to new configuration config="{\"ingress\":[{\"hostname\":\"example.com\",\"originRequest\":{\"noTLSVerify\":true},\"service\":\"https://192.168.0.127:8081\"},{\"service\":\"http_status:404\"}],\"warp-routing\":{\"enabled\":false}}" version=3
2022-11-13T15:27:44Z INF Connection bee32659-6187-4e4f-abe4-2e9903757711 registered connIndex=1 ip=198.41.192.57 location=HKG
2022-11-13T15:27:45Z INF Connection b3ca2718-4169-4ef8-89d7-61a743f64ce8 registered connIndex=2 ip=198.41.200.43 location=SIN
2022-11-13T15:27:46Z INF Connection 84b89c8c-71f3-465c-b362-46fb56c8baf2 registered connIndex=3 ip=198.41.192.7 location=HKG
2022-11-13T15:28:35Z ERR  error="Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: tls: first record does not look like a TLS handshake" cfRay=769889bb8bf7044b-HKG ingressRule=0 originService=https://192.168.0.127:8081
2022-11-13T15:28:35Z 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: tls: first record does not look like a TLS handshake" connIndex=1 dest=https://example.com/ ip=198.41.192.57 type=http
2022-11-13T15:28:35Z ERR  error="Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: tls: first record does not look like a TLS handshake" cfRay=769889bd8e9e044b-HKG ingressRule=0 originService=https://192.168.0.127:8081
2022-11-13T15:28:35Z 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: tls: first record does not look like a TLS handshake" connIndex=1 dest=https://example.com/favicon.ico ip=198.41.192.57 type=http
1 Like