Do really old cloudflared servers no longer work?
Do really old cloudflared servers no longer work?
503 header?zones/{zone_id}/email/routing/rules/catch_all endpoint and I cant for the life of me figure out the permissions the api key needs to have (the same key is working on other endpoints with its current permissions)discord.com A @1.1.1.1 +noall +answerdiggy diggy hole
•3/2/24, 5:03 AM
X-Auth-Key and X-Auth-Email headers are just the same key as the Authorization header, minus Bearer right?



subdomain.example.comsomething.subdomain.example.com*.example.com, example.com). Because of how SSL Certificates work, wildcards only ever cover one label or level of subdomains. You'd need a certificate covering *.subdomain.example.com or something.subdomain.example.com exact for it to work.com is operated by Versign, example.com is delegated/controlled by someone else, test2.example.com could also be controlled/operated by someone else. Different levels can be controlled by different people, part of the reason why there's special rules around it like with SSL Certificates.something-subdomain.example.com, using - rather then ., and you would have no issue with Cloudflare SSL covering it, the wildcard *.example.com universal certificate would cover it.NAME | TTL | DATA
------------+------+----------------
discord.com | 219s | 162.159.135.232
discord.com | 219s | 162.159.128.233
discord.com | 219s | 162.159.138.232
discord.com | 219s | 162.159.137.232
discord.com | 219s | 162.159.136.232subdomain.example.comsomething.subdomain.example.comsomething.subdomain.example.com*.example.com*.example.com*.subdomain.example.comcomtest2.example.comsomething-subdomain.example.com-.