This is more of a heads up for others than an actual issue. Discord will reject payloads for for non-fully-qualified domains. This might happen if your alertmanager's external URL is http://alertmanager:123" where alertmanageris the machine's name in tailscale. This will work/resolve fine on members of your tailnet because the suffix is automagically applied, but discord apparently doesn't like it. To fix this, change your alertmanger's external URL to be fully qualified (ie, include the tailnet's dns name ...alertmanager.some-junk.ts.net`).
This is more of a heads up for others than an actual issue. Discord will reject payloads for for non-fully-qualified domains. This might happen if your alertmanager's external URL is
http://alertmanager:123" wherealertmanageris the machine's name in tailscale. This will work/resolve fine on members of your tailnet because the suffix is automagically applied, but discord apparently doesn't like it. To fix this, change your alertmanger's external URL to be fully qualified (ie, include the tailnet's dns name ...alertmanager.some-junk.ts.net`).