Apple ID, browser: 502 Bad Gateway, iPhone: authentication server [RESOLVED]

[z0rk]

I've recently purchased an iPhone and I am unable to authenticate with my Apple ID credentials on the device itself:
authentication server can't be reached

Or with any browser from any other device (laptop, etc.) https://appleid.apple.com/
502 Bad Gateway

So I know it's not a browser issue with any one of my devices. I don't know if this is an issue introduced with the upgrade to 19.x, because I had already upgraded prior to purchasing the iPhone.

Regardless I found this forum topic that I thought might be related and followed the instructions, but it did not resolve the issue. https://forum.opnsense.org/index.php?topic=11401.msg51701#msg51701

Any thoughts?

Thanks

[newsense]

Unclear why a 502 issue would be pinned on opnsense here...can you please describe your setup ?

[z0rk]

Just to be clear, I am not necessarily trying to pin this on OPNsense, but prior to upgrading, I scanned through the 19.x forum posts to see, if anybody reported any issues with the upgrade. That's how I came across the post mentioned above and it specifically refers to an iPhone being unable to access an Apple website that requires Apple ID authentication, so I don't think my reasoning is too far fetched. Also, I can access other websites without issues from the iPhone or my other devices, so this appears to be specific to the https://appleid.apple.com/ website. Prior to posting, I've checked the Apple services status page. All services were up and running. As far as my setup is concerned, this is one segment that exhibits this behavior:

modem > OPNsense > wifi router
> laptop wired
> iPhone wireless

[newsense]

Does it work modem > wifi router, taking the firewall out of the way ? If yes then it's likely a configuration (or change) on the firewall that may be causing it -- so we'll need more details about your FW setup.

[z0rk]

This issue resolved itself on its own. I believe it was related to one or two DNS service providers: 1.1.1.1 or/and 9.9.9.9. This is just a guess, but I've noticed before that randomly domains don't resolve properly.