Bot Mhann Posts - Answer Overflow

Bot Mhann

Explore posts from servers

DIdiscord.js - Imagine ❄CDCloudflare Developers

•Created by Bot Mhann on 12/10/2024 in #general-help

Issue With Cloudflared Tunnel

I have a cloudflared tunnel that was running healthy for just shy of 2 days. I run warp but have excluded all the domains I believe I need to (see pic below). The status is now appearing as degraded. I have included my logs below. It seems to keep retrying, but to no avail. Any suggestions as to what I could try?

Dec 08 20:50:32 ip-172-31-95-88 systemd[1]: Started cloudflared.
Dec 08 20:50:32 ip-172-31-95-88 cloudflared[110864]: 2024-12-09T01:50:32Z INF Registered tunnel connection connIndex=1 connection=559819d6-89f2-4a85-9400-80ed022bb6a2 event=0 ip=2606:4700:a8::10 location=iad07 protocol=http2
Dec 08 20:50:33 ip-172-31-95-88 cloudflared[110864]: 2024-12-09T01:50:33Z INF Updated to new configuration config="{\"ingress\":[{\"hostname\":\"mhanndalorianbot.work\", \"service\":\"http://localhost:80\"}, {\"service\":\"http_status:404\"}], \"warp-routing\":{\"enabled\":true}}" version=6
Dec 08 20:50:33 ip-172-31-95-88 cloudflared[110864]: 2024-12-09T01:50:33Z INF Registered tunnel connection connIndex=2 connection=1334e347-2141-4877-b482-809a0e6fae26 event=0 ip=2606:4700:a8::5 location=iad05 protocol=http2
Dec 08 20:50:34 ip-172-31-95-88 cloudflared[110864]: 2024-12-09T01:50:34Z INF Registered tunnel connection connIndex=3 connection=2a174fcc-3b93-468e-9127-2ee490fe31b6 event=0 ip=2606:4700:a0::1 location=iad02 protocol=http2
Dec 10 07:39:38 ip-172-31-95-88 cloudflared[110864]: 2024-12-10T12:39:38Z INF Lost connection with the edge connIndex=3
Dec 10 07:39:38 ip-172-31-95-88 cloudflared[110864]: 2024-12-10T12:39:38Z WRN Serve tunnel error error="connection with edge closed" connIndex=3 event=0 ip=2606:4700:a0::1
Dec 10 07:39:38 ip-172-31-95-88 cloudflared[110864]: 2024-12-10T12:39:38Z INF Retrying connection in up to 1s connIndex=3 event=0 ip=2606:4700:a0::1
Dec 10 07:39:38 ip-172-31-95-88 cloudflared[110864]: 2024-12-10T12:39:38Z ERR failed to serve incoming request error="Error shutting down control stream: client disconnected"

Dec 08 20:50:32 ip-172-31-95-88 systemd[1]: Started cloudflared.
Dec 08 20:50:32 ip-172-31-95-88 cloudflared[110864]: 2024-12-09T01:50:32Z INF Registered tunnel connection connIndex=1 connection=559819d6-89f2-4a85-9400-80ed022bb6a2 event=0 ip=2606:4700:a8::10 location=iad07 protocol=http2
Dec 08 20:50:33 ip-172-31-95-88 cloudflared[110864]: 2024-12-09T01:50:33Z INF Updated to new configuration config="{\"ingress\":[{\"hostname\":\"mhanndalorianbot.work\", \"service\":\"http://localhost:80\"}, {\"service\":\"http_status:404\"}], \"warp-routing\":{\"enabled\":true}}" version=6
Dec 08 20:50:33 ip-172-31-95-88 cloudflared[110864]: 2024-12-09T01:50:33Z INF Registered tunnel connection connIndex=2 connection=1334e347-2141-4877-b482-809a0e6fae26 event=0 ip=2606:4700:a8::5 location=iad05 protocol=http2
Dec 08 20:50:34 ip-172-31-95-88 cloudflared[110864]: 2024-12-09T01:50:34Z INF Registered tunnel connection connIndex=3 connection=2a174fcc-3b93-468e-9127-2ee490fe31b6 event=0 ip=2606:4700:a0::1 location=iad02 protocol=http2
Dec 10 07:39:38 ip-172-31-95-88 cloudflared[110864]: 2024-12-10T12:39:38Z INF Lost connection with the edge connIndex=3
Dec 10 07:39:38 ip-172-31-95-88 cloudflared[110864]: 2024-12-10T12:39:38Z WRN Serve tunnel error error="connection with edge closed" connIndex=3 event=0 ip=2606:4700:a0::1
Dec 10 07:39:38 ip-172-31-95-88 cloudflared[110864]: 2024-12-10T12:39:38Z INF Retrying connection in up to 1s connIndex=3 event=0 ip=2606:4700:a0::1
Dec 10 07:39:38 ip-172-31-95-88 cloudflared[110864]: 2024-12-10T12:39:38Z ERR failed to serve incoming request error="Error shutting down control stream: client disconnected"

2 replies

CDCloudflare Developers

•Created by Bot Mhann on 12/5/2024 in #general-help

Cloudflared Tunnel Loosing Connection

I have an AWS system running a Cloudflared tunnel. I am also running WARP. The Cloudflared tunnel has worked fine for the past 5 days, but then approximately 12 hours ago it went down and I noticed this in my logs:

Dec 04 22:55:45 ip-172-31-95-88 cloudflared[1386]: 2024-12-05T03:55:45Z WRN Failed to serve tunnel connection error="timeout: no recent network activity">
Dec 04 22:55:45 ip-172-31-95-88 cloudflared[1386]: 2024-12-05T03:55:45Z WRN Serve tunnel error error="timeout: no recent network activity" connIndex=1 ev>
Dec 04 22:55:45 ip-172-31-95-88 cloudflared[1386]: 2024-12-05T03:55:45Z INF Retrying connection in up to 1s connIndex=1 event=0 ip=2606:4700:a0::5
Dec 04 22:55:45 ip-172-31-95-88 cloudflared[1386]: 2024-12-05T03:55:45Z WRN Failed to serve tunnel connection error="failed to accept QUIC stream: timeou>
Dec 04 22:55:45 ip-172-31-95-88 cloudflared[1386]: 2024-12-05T03:55:45Z WRN Serve tunnel error error="failed to accept QUIC stream: timeout: no recent ne>
Dec 04 22:55:45 ip-172-31-95-88 cloudflared[1386]: 2024-12-05T03:55:45Z INF Retrying connection in up to 1s connIndex=0 event=0 ip=2606:4700:a8::5
Dec 04 22:55:45 ip-172-31-95-88 cloudflared[1386]: 2024-12-05T03:55:45Z WRN Failed to serve tunnel connection error="timeout: no recent network activity">
Dec 04 22:55:45 ip-172-31-95-88 cloudflared[1386]: 2024-12-05T03:55:45Z WRN Serve tunnel error error="timeout: no recent network activity" connIndex=3 ev>
Dec 04 22:55:45 ip-172-31-95-88 cloudflared[1386]: 2024-12-05T03:55:45Z INF Retrying connection in up to 1s connIndex=3 event=0 ip=2606:4700:a0::8

Dec 04 22:55:45 ip-172-31-95-88 cloudflared[1386]: 2024-12-05T03:55:45Z WRN Failed to serve tunnel connection error="timeout: no recent network activity">
Dec 04 22:55:45 ip-172-31-95-88 cloudflared[1386]: 2024-12-05T03:55:45Z WRN Serve tunnel error error="timeout: no recent network activity" connIndex=1 ev>
Dec 04 22:55:45 ip-172-31-95-88 cloudflared[1386]: 2024-12-05T03:55:45Z INF Retrying connection in up to 1s connIndex=1 event=0 ip=2606:4700:a0::5
Dec 04 22:55:45 ip-172-31-95-88 cloudflared[1386]: 2024-12-05T03:55:45Z WRN Failed to serve tunnel connection error="failed to accept QUIC stream: timeou>
Dec 04 22:55:45 ip-172-31-95-88 cloudflared[1386]: 2024-12-05T03:55:45Z WRN Serve tunnel error error="failed to accept QUIC stream: timeout: no recent ne>
Dec 04 22:55:45 ip-172-31-95-88 cloudflared[1386]: 2024-12-05T03:55:45Z INF Retrying connection in up to 1s connIndex=0 event=0 ip=2606:4700:a8::5
Dec 04 22:55:45 ip-172-31-95-88 cloudflared[1386]: 2024-12-05T03:55:45Z WRN Failed to serve tunnel connection error="timeout: no recent network activity">
Dec 04 22:55:45 ip-172-31-95-88 cloudflared[1386]: 2024-12-05T03:55:45Z WRN Serve tunnel error error="timeout: no recent network activity" connIndex=3 ev>
Dec 04 22:55:45 ip-172-31-95-88 cloudflared[1386]: 2024-12-05T03:55:45Z INF Retrying connection in up to 1s connIndex=3 event=0 ip=2606:4700:a0::8

This has happened before and running sudo systemctl restart cloudflared always seems to fix the issue. Does anyone know why this might be happening and what I can try to avoid it? Also, is there some way I can auto restart if my system gets in this state? Thanks for any help!

3 replies

CDCloudflare Developers

•Created by Bot Mhann on 9/15/2024 in #general-help

Warp Logs

How do I decrease the logging done by cloudflare Warp? I'd like to turn off all debug logs so it is not spamming syslog. Thanks!

1 replies

CDCloudflare Developers

•Created by Bot Mhann on 5/21/2024 in #general-help

Warning with Split Tunnel

I am using coudflare warp (warp-cli) on Ubuntu. I recently added a URL to my exclude list. SInce doing that, I am now getting thousands of these:

via hosts list.
May 21 08:36:04 ip-172-31-95-88 warp-svc[482]: #033[2m2024-05-21T12:36:04.603Z#033[0m #033[33m WARN#033[0m #033[2mwarp::warp::split_manager#033[0m#033[2m:#033[0m Host swprod.capitalgames.com => 34.205.245.251 matches tunnel rules but is not specified

via hosts list.
May 21 08:36:04 ip-172-31-95-88 warp-svc[482]: #033[2m2024-05-21T12:36:04.603Z#033[0m #033[33m WARN#033[0m #033[2mwarp::warp::split_manager#033[0m#033[2m:#033[0m Host swprod.capitalgames.com => 34.205.245.251 matches tunnel rules but is not specified

Can anyone explain what I need to do to fix this? Thank you!

5 replies

CDCloudflare Developers

•Created by Bot Mhann on 5/18/2024 in #general-help

Warp CLI mode question.

I have the following options for mode in warp CLI: [possible values: warp, doh, warp+doh, dot, warp+dot, proxy, tunnel_only] I am using warp on my AWS EC2 instance to host a discord bot. The instance only has an IPv6, and to work with Discord it needs IPv4. The current mode is warp. Is this the best mode for what I am doing?

7 replies

CDCloudflare Developers

•Created by Bot Mhann on 3/24/2024 in #general-help

Bypass WARP

Is it possible to have all traffic from a Docker container bypass WARP (running on Ubuntu)? WARP is running on the host machine. I need to keep WARP running non containerized on the host machine. Thanks!

1 replies

CDCloudflare Developers

•Created by Bot Mhann on 3/18/2024 in #general-help

Cloudfarw WARP

I am running WARP on my AWS EC2 instance. Is there a way that I can have certain traffic not go through the WARP tunnel? I make certain calls to various APIs from within a Discord bot and would like to avoid using the tunnel if possible for these calls. Thank you.

6 replies

CDCloudflare Developers

•Created by Bot Mhann on 3/12/2024 in #general-help

WARP and Nginix

5 replies

CDCloudflare Developers

•Created by Bot Mhann on 3/12/2024 in #general-help

Cloudflare WARP question

I'm running a discord bot on an AWS EC2 instance. I am using node redis locally for caching. After enabling WARP, I am getting several connection timeout errors with Redis when I launch. Usually after about 1 - 2 minutes the errors stop and it finally connects. I tried increasing the time out to 15 seconds and the errors are still occurring. Is there anything in WARP I can check/set to troubleshoot this? Thanks!

7 replies

Gaming

Programming