Denton Gentry

> Yes, it was -- with the same tag. Given this: ``` { "action": "accept", "src": ["autogroup:members", "group:shared"], "dst": ["autogroup:self", "tag:ssh-access"], "users": ["autogroup:nonroot", "root"], }, ``` A tagged node isn't...

You appear to have enabled Check mode for host `e` https://tailscale.com/kb/1193/tailscale-ssh/#configure-tailscale-ssh-with-check-mode Also as Host `a` is running Tailscale 1.24, it is not using Tailscale SSH at all. You're reaching the...

The Services tab will show that there is an SSH service running on port 22. That can be OpenSSHd, anything listening on port 22 will be shown. Tailscale SSH support...

PrivateDNS in automatic mode, where it tries DNS-over-TLS but falls back to UDP if it fails, does work. Turning PrivateDNS On all the time, where you enter a hostname like...

Around the time of the bugreport: ``` 2022-10-01 03:18:06.193507134 +0000 UTC: 22.8M/144.1M dns udp query: context deadline exceeded 2022-10-01 03:18:06.193748141 +0000 UTC: 22.8M/144.1M dns udp query: context deadline exceeded 2022-10-01...

@seowalex Please file a new issue.

What was the system doing around the time of the bugreport?

We need something to be able to help diagnose what is happening. If you attempt to connect to port 80 and immediately run `tailscale bugreport`, it gives us something to...

Shortly before the bugreport, we see: ``` 2022-09-21 13:31:15.641614678 +0800 +0800: Accept: TCP{100.95.116.34:52471 > 100.72.15.37:80} 64 tcp ok ``` So the connection to port 80 did arrive and was not...

The first screenshot says: `Connected to 100.72.15.37 (100.72.15.37) port 80 (80)` It was able to connect. The problem is that the web server did not return the data you were...