Page MenuHomeMiraheze

502 errors on all custom domains
Closed, ResolvedPublic


I'm seeing 502 Bad Gateway error when requesting any page on Miraheze-hosted domains like

Same results accessing from different browsers, mobile and desktops, and different locations (West Coast, US).

Also seen on and

Related Objects

Duplicates Merged Here
T6367: 502 Bad Gateway

Event Timeline

Tmccormick1 triaged this task as Unbreak Now! priority.Nov 6 2020, 22:00
Tmccormick1 created this task.
Unknown Object (User) lowered the priority of this task from Unbreak Now! to Normal.Nov 6 2020, 22:03
Unknown Object (User) added a project: DNS.
Unknown Object (User) added a subscriber: revi.

I can tell you that was removed from the Miraheze DNS earlier today due to some sort of misconfiguration with namesavers or domain status. I am guessing the same goes for your other domain? @revi what was the reason for the removal again?

RhinosF1 raised the priority of this task from Normal to Unbreak Now!.Nov 6 2020, 22:08 is also 502 so could it be our DNS servers?

RhinosF1 renamed this task from getting 502 Bad Gateway error on and to 502 errors on all custom domains.Nov 6 2020, 22:10
RhinosF1 assigned this task to Paladox.
RhinosF1 updated the task description. (Show Details)

Under investiagtion

* Remove

No longer pointing to Miraheze NS

;			IN	NS

;; ANSWER SECTION:		1800	IN	NS		1800	IN	NS

That domain's DNS record is not pointing to Miraheze's Authoritative DNS server, therefore it has been removed from miraheze DNS configuration. Not related to the downtime, I assume.

RhinosF1 updated the task description. (Show Details)

This is now resolved. As @revi says, is a seperate issue for another task.