u/TrashMobber

Hey folks — long-time lurker, first-time beggar. I run a small nonprofit site (trashmob.eco — we organize community litter cleanups) and I have an intermittent apex-domain bug that I've been chasing for months and finally need an army of strangers to help me pin down.

The setup: Azure Front Door Standard in front of a Container App. www.trashmob.eco is a CNAME to the AFD endpoint; trashmob.eco is an alias A record to the same endpoint. Both custom domains bound to the same route, both with AFD-managed certs, both Approved. There's a rule set that 308s the apex to https://www.trashmob.eco/.

What works, all day, every day, from every device I own:

• http://trashmob.eco/ → 308 → https://www.trashmob.eco/ (single hop, x-azure-ref header present, everything textbook)
• https://trashmob.eco/ → 308 → https://www.trashmob.eco/
• https://www.trashmob.eco/ → 200 with the page

What (I'm told) sometimes doesn't work:

• User types trashmob.eco into a fresh browser session — usually iPhone Safari, but also Chrome on desktop — and gets a "site can't be reached" style error
• Refresh, and it loads fine
• Going straight to www.trashmob.eco has never once failed

I've written up the current investigation, ruled out DNS + cold-container-start + cert propagation, deployed a single-hop redirect fix, and cannot for the life of me reproduce it. Every warm probe is clean. But at least one user hit it yesterday on an iPhone.

The ask: if you have a spare 15 seconds — especially if you're on iOS Safari, on a mobile network, or in a region that isn't the US west coast — could you try typing trashmob.eco (no https://, no www.) into a fresh browser tab / private window and let me know:

1. Did it load? (Yes / no — either answer is a data point.)
2. If it didn't load: what did the error say, verbatim? A screenshot is worth a thousand curl -vs. The error text alone would narrow this from four theories to one.
3. Bonus: your rough geo (country / region is fine), browser, and whether hitting refresh made it work.

I'm not asking for a support engagement, a code review, or the truth about whether I should just delete the apex record and let www win — I just need enough repros to correlate the pattern. Whatever you send back, I promise to update the investigation log and reply with what I find.

Thank you in advance. If Azure Front Door were a person I would like to have a very long, calm conversation with it.

— A guy with an alias A record and a dream