Cannot access Services run through Traefik - keep getting 521 Cloudflare error

• quic-go

  2 7,799 10.0 Go

  Discontinued A QUIC implementation in pure go [Moved to: https://github.com/quic-go/quic-go] (by lucas-clemente)

  

2023-02-12T15:29:22Z INF Starting tunnel tunnelID=f0cc67d9-973b-44bd-ae58-d7c9e3b112f0 2023-02-12T15:29:22Z INF Version 2023.2.1 2023-02-12T15:29:22Z INF GOOS: linux, GOVersion: go1.19.5, GoArch: amd64 2023-02-12T15:29:22Z INF Settings: map[no-autoupdate:true token:*****] 2023-02-12T15:29:23Z INF Generated Connector ID: 0550ea9c-1c9e-4e48-9d85-defcdc33a31c 2023-02-12T15:29:23Z INF Will be fetching remotely managed configuration from Cloudflare API. Defaulting to protocol: quic 2023-02-12T15:29:23Z INF Initial protocol quic 2023-02-12T15:29:23Z INF ICMP proxy will use 172.17.0.2 as source for IPv4 2023-02-12T15:29:23Z INF ICMP proxy will use :: as source for IPv6 2023-02-12T15:29:23Z INF Starting metrics server on 127.0.0.1:45807/metrics 2023/02/12 15:29:23 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. 2023-02-12T15:29:23Z INF Connection c81366ed-3bb8-479a-a832-243451980ad3 registered with protocol: quic connIndex=0 ip=198.41.192.227 location=MSP 2023-02-12T15:29:24Z INF Connection 8f2804c5-2dd7-4b2f-8400-e103c2165a80 registered with protocol: quic connIndex=1 ip=198.41.200.43 location=ORD 2023-02-12T15:29:24Z INF Updated to new configuration config="{\"ingress\":[{\"hostname\":\"portainer.mydomain.com\",\"originRequest\":{},\"service\":\"http://my-public-ip:9000\"},{\"hostname\":\"homeassistant.mydomain.com\",\"originRequest\":{},\"service\":\"http://my-public-ip:8123\"},{\"hostname\":\"frigate.mydomain.com\",\"originRequest\":{},\"service\":\"http://my-public-ip:5000\"},{\"hostname\":\"mosquitto.mydomain.com\",\"originRequest\":{},\"service\":\"http://my-public-ip:1883\"},{\"hostname\":\"ra.mydomain.com\",\"originRequest\":{},\"service\":\"http://my-public-ip:8124\"},{\"service\":\"http_status:404\"}],\"warp-routing\":{\"enabled\":false}}" version=28 2023-02-12T15:29:25Z INF Connection f5847632-f534-4cae-a4df-02e11447406e registered with protocol: quic connIndex=2 ip=198.41.192.107 location=MSP 2023-02-12T15:29:25Z INF Connection 664d6d41-b0ac-499d-894d-42e38e5bd475 registered with protocol: quic connIndex=3 ip=198.41.200.193 location=ORD 2023-02-12T15:30:16Z 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 my-public-ip:5000: connect: connection refused" cfRay=79865d4d2bdd62bd-ORD ingressRule=2 originService=http://my-public-ip:5000 2023-02-12T15:30:16Z 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 my-public-ip:5000: connect: connection refused" connIndex=1 dest=http://frigate.mydomain.com/api/stats ip=198.41.200.43 type=http 2023-02-12T15:31:37Z 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 my-public-ip:5000: connect: connection refused" cfRay=79865f497bb98101-ORD ingressRule=2 originService=http://my-public-ip:5000 2023-02-12T15:31:37Z 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 my-public-ip:5000: connect: connection refused" connIndex=1 dest=http://frigate.mydomain.com/api/stats ip=198.41.200.43 type=http

• InfluxDB

  www.influxdata.com featured

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

Suggest a related project