I am running docker and manage it with portainer. Portainer was installed with docker command. Anyway, being away most of the time, i wanted to be able to deploy more apps for my homelab and decided to make portainer available on the web. I spun up a tunnel, copied the code to run it in docker and everything worked. But… not so long after the tunnel container got shutdown and i was able to get this from the log:
2023-05-13T08:57:20Z INF Starting tunnel tunnelID=d4a3cefa-1c78-4ac3-8a93-7f9c631134eb
2023-05-13T08:57:20Z INF Version 2023.5.0
2023-05-13T08:57:20Z INF GOOS: linux, GOVersion: go1.19.8, GoArch: amd64
2023-05-13T08:57:20Z INF Settings: map[no-autoupdate:true token:*****]
2023-05-13T08:57:20Z INF Generated Connector ID: 9fdb1657-9d50-4dbe-a302-d889cd885634
2023-05-13T08:57:20Z INF Initial protocol quic
2023-05-13T08:57:20Z INF ICMP proxy will use 172.17.0.3 as source for IPv4
2023-05-13T08:57:20Z INF ICMP proxy will use :: as source for IPv6
2023-05-13T08:57:20Z WRN The user running cloudflared process has a GID (group ID) that is not within ping_group_range. You might need to add that user to a group within that range, or instead update the range to encompass a group the user is already in by modifying /proc/sys/net/ipv4/ping_group_range. Otherwise cloudflared will not be able to ping this network error="Group ID 65532 is not between ping group 65534 to 65534"
2023-05-13T08:57:20Z WRN ICMP proxy feature is disabled error="cannot create ICMPv4 proxy: Group ID 65532 is not between ping group 65534 to 65534 nor ICMPv6 proxy: socket: permission denied"
2023-05-13T08:57:20Z INF Starting metrics server on 127.0.0.1:38931/metrics
2023/05/13 08:57:20 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-05-13T08:57:21Z INF Registered tunnel connection connIndex=0 connection=d43bfce3-1e30-4c62-afe2-b211ad03c03b event=0 ip=198.41.200.113 location=OSL protocol=quic
2023-05-13T08:57:21Z INF Registered tunnel connection connIndex=1 connection=5d5554d8-0097-400c-9b9d-f5eccfde24e0 event=0 ip=198.41.192.27 location=TLL protocol=quic
2023-05-13T08:57:21Z INF Updated to new configuration config="{\"ingress\":[{\"hostname\":\"port.umbres.xyz\", \"originRequest\":{\"http2Origin\":true, \"noTLSVerify\":true}, \"service\":\"https://<internal_IP>:9443\"}, {\"service\":\"http_status:404\"}], \"warp-routing\":{\"enabled\":false}}" version=5
2023-05-13T08:57:22Z INF Registered tunnel connection connIndex=2 connection=17da220e-a16b-4986-be91-9235108a2d6a event=0 ip=198.41.192.57 location=TLL protocol=quic
2023-05-13T08:57:24Z INF Registered tunnel connection connIndex=3 connection=2b0ec15d-32f8-4ace-9de6-ac2a06cea83c event=0 ip=198.41.200.73 location=OSL protocol=quic
2023-05-13T10:00:03Z INF Initiating graceful shutdown due to signal terminated ...
I reenabled it and after some time, it got shutdown again and the container got deleted aswell, don’t know why.
If someone could explain to me why this keeps happening and how do i prevent it from happening i would appreciate it.