Fly.io: exit node enabled on Tailscale but traffic doesn't pass through the node

SUPPORT QUESTIONS
1

I am following this guide to create an exit node on fly.io:

I am able to create the node and mark it as an exit node, but when I choose that exit node on other devices, I don’t see traffic passing through the exit node. Could I get a hand in troubleshooting why this might be happening, please?

Here’s a bug report from the node that runs as an exit: BUG-f88b29bf6b21fee8ba5a5003551a9b0c450f70e143f302a96643f21af2f5a6b2-20211118150441Z-a1c7ed862f4e9adc

I can ping other devices fine:

➜  fly-tailscale-exit git:(main) ✗ fly ssh console
Connecting to sparkling-snow-565.internal... complete
/ # cd app/
/app # ./tailscale ping mew
pong from mew (100.78.96.64) via DERP(blr) in 139ms
pong from mew (100.78.96.64) via DERP(blr) in 57ms
pong from mew (100.78.96.64) via DERP(blr) in 57ms
pong from mew (100.78.96.64) via 49.37.209.1:8985 in 43ms

Other devices can ping the exit node fine too:

➜  ~ ping fly-sin-1
PING fly-sin-1.tailnet-b593.ts.net (100.121.42.93): 56 data bytes
64 bytes from 100.121.42.93: icmp_seq=0 ttl=64 time=94.122 ms
64 bytes from 100.121.42.93: icmp_seq=1 ttl=64 time=46.009 ms
64 bytes from 100.121.42.93: icmp_seq=2 ttl=64 time=52.326 ms
64 bytes from 100.121.42.93: icmp_seq=3 ttl=64 time=46.443 ms
64 bytes from 100.121.42.93: icmp_seq=4 ttl=64 time=47.079 ms
64 bytes from 100.121.42.93: icmp_seq=5 ttl=64 time=46.696 ms
64 bytes from 100.121.42.93: icmp_seq=6 ttl=64 time=47.153 ms
^C
--- fly-sin-1.tailnet-b593.ts.net ping statistics ---
7 packets transmitted, 7 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 46.009/54.261/94.122/16.393 ms

I have set autogroup:internet:443 on my ACLs too.

I am not using Tailscale in userspace networking mode, which is a known issue at the moment:

Thanks for taking a look!

2

Using Cloudflare for DNS at the moment:

image
image1638×1688 223 KB 

➜  fly-tailscale-exit git:(main) ✗ fly ssh console
Connecting to sparkling-snow-565.internal... complete
/ # cat /etc/resolv.conf
# resolv.conf(5) file generated by tailscale
# DO NOT EDIT THIS FILE BY HAND -- CHANGES WILL BE OVERWRITTEN

nameserver 100.100.100.100
search tailnet-b593.ts.net arunwp.org.github.beta.tailscale.net
3

Disregard, autogroup:internet:443 was the problem. Updating that to autogroup:internet:443,80,53 matches my needs.