AstroLog PIR®
All WordPress sites entries

The XDN comes home while the family gets a shoutout

MediumWordPress sites 2 min readBy Christopher W
TL;DR: The escalated XDN case resolved the same evening - Martin G. at WPX System Admins unstuck the rebuild and confirmed "the issue has been resolved." And the root cause is now on the record: a left-over value from the suspension period had sealed the toggle shut from the front end. The WPX family also got a public shoutout in the AstroLog's contacts library.
Read the full story →

🎉 The unstick

The escalation from the breather entry lasted barely an afternoon of working hours. On October 14 at 17:53, two replies landed almost together:

  • Nikolay Georgiev confirmed the XDN was still stuck after his resets and that he had escalated to the System Admins, with their working window (Mon-Fri, 09:30-18:00 GMT+3).
  • Martin Georgiev, WPX System Admin, closed the loop: “The issue has been resolved.”

Christopher’s verification habit held: certificate live for both the apex and www on both XDN IPs, the site serving through the CDN with cache hits, cart/checkout/account pages correctly bypassing cache, and mail untouched - the same checklist Velina’s SSL fix passed on October 5.

🧾 The root cause, on the record

The answer to “what actually happened” arrived on October 15, and it is a small classic of how systems fail quietly. In Martin G.’s words: a left-over value from the suspension period had prevented any actions on the XDN. While it stayed active in the backend and the website kept loading from the XDN, that parameter blocked every front-end action on it - including retrieving its status (on/off).

Which explains everything the panel was doing: the rebuild spinning on “building,” the resets that wouldn’t take, the status that wouldn’t read. The toggle was never broken - it was sealed shut by a leftover from the payment lapse, and only a System Admin could remove the seal. Ticket #517528 is now Closed, with thanks to Nikolay G., Nikolai R., and Martin G. by name.

📜 Asking for the minutes

One more exchange mattered for how we keep records: Christopher asked WPX to “provide details on what happened for this page being built out for our members to see how WPX helps us,” pointing at this very changelog. Nikolai R. forwarded the inquiry to the System Admins, Martin G. supplied the write-up above, and Christopher closed the ticket with thanks. A support team helping write the public record of their own good work - exactly how it should go.

And the shoutout: the WPX family now appears in the contacts library - the people behind the tickets, thanked in public.

🧭 The pattern, for next time

  1. Verify with the checklist, not with hope: cert on both hostnames and both IPs, CDN serving with cache hits, sensitive pages bypassing, mail untouched.
  2. Escalations are patience problems, not data problems - the source of truth was never at risk.
  3. A suspension can leave residue after it lifts. When a control panel acts sealed after a billing event, ask the provider to check for left-over suspension values before suspecting the feature itself.
  4. Ask for the write-up while the ticket is warm - the details land in the AstroLog while everyone still remembers them.

The edge caught its breath; the fellowship kept meeting.