The year my Ghost site never reached the fediverse
Two missing nginx proxy blocks left my Ghost site invisible on the fediverse for a year. Here is how I noticed, fixed it, and what to check after a domain move.
The bug that sat in my Ghost admin for a year
For almost a year, the Network tab in my Ghost Admin quietly said “Loading interrupted”. Every time I opened it, I saw 404 responses on /.ghost/activitypub/ and moved on.
I had just moved the site from a .nl domain to .com. Posts loaded, images worked, SSL was fine. The only thing that clearly was not fine lived in that Network tab, and I assumed it was some rough edge of the ActivityPub beta.
It was not. It was my nginx config.
What actually broke in the move
During the domain move, I rebuilt the nginx config and missed two proxy blocks that forward ActivityPub traffic from my domain to Ghost's ActivityPub service at ap.ghost.org.
Without those location blocks, requests to the ActivityPub endpoints on my domain simply hit nginx and died. Ghost itself never saw them. That explains the 404s in the Admin Network tab on paths under /.ghost/activitypub/.
The fix was small and specific: add back the two location blocks that proxy ActivityPub traffic to ap.ghost.org. Once those were in place and nginx was reloaded, the server side of ActivityPub started working again.
The second problem: my own browser
After fixing nginx, the Network tab in Ghost Admin still looked broken. Requests were being redirected in a loop, and the browser kept following cached 301 responses instead of the new, correct ones.
On the server, the config was now fine. On the client, my browser was stuck in the past.
Clearing the cache finally snapped it out of it. After that, the Network tab stopped complaining about "Loading interrupted" and the ActivityPub calls succeeded. If you are debugging anything involving redirects and domain moves, a stale 301 can waste a lot of time.
What that year of 404s actually meant
ActivityPub is how Ghost federates posts into the wider social web. With the proxy blocks missing, my site was effectively publishing into a void as far as the fediverse was concerned.
Everything I published during that year never federated. From the outside, my account might as well not have existed. When I finally fixed the config, I was effectively starting from zero followers again.
That is the part that stings a bit: the bug was visible the whole time in my own admin interface. I decided it was probably a beta issue and ignored it.
How I finally tested that it worked
Once the nginx fix was in and the browser cache cleared, I wanted to confirm that ActivityPub was actually live again, not just erroring more quietly.
1. Searching for my handle from Mastodon
The first step was to search for my handle @richard@richardlemon.com from a Mastodon account.
Two details mattered here:
- Searching while logged out from Mastodon did not work.
- Searching while logged in did work and found the account.
That was the first confirmation that federation was doing something again.
2. Following my own account
From that same Mastodon account, I followed @richard@richardlemon.com. This was a simple way to test whether the inbox on my Ghost ActivityPub setup was accepting and processing follow requests.
The follow went through, which meant the plumbing from Mastodon to my domain and on to Ghost was alive again.
3. Sending a first note
Next step: publish a first ActivityPub note from Ghost and see if it arrives on the Mastodon side.
That note showed up in the follower's feed within a couple of minutes. After a year of silence, seeing that first note land was enough proof that the fix was real.
Why I ignored it for so long
The honest reason this sat for a year is simple: I assumed the ActivityPub integration was still beta and a bit flaky, and that the "Loading interrupted" message in Ghost Admin was part of that.
Once you have told yourself "this is probably just beta noise" a few times, it fades into the background. The site worked, readers could visit, posts published. Only the fediverse side was dead, and that is easy to miss if you are not actively watching it.
What to check after you move a self-hosted domain
If you self-host Ghost and move your domain, there are a few things worth checking immediately after you flip DNS.
1. ActivityPub proxying
If you use Ghost's ActivityPub integration:
- Confirm your nginx (or other proxy) config still contains the
locationblocks that forward ActivityPub traffic toap.ghost.org. - Open the browser dev tools Network tab in Ghost Admin and watch the ActivityPub-related requests for 404s or redirect loops.
2. Redirects and caching
After any domain move, you will have a mix of old and new URLs, and probably some 301 redirects in between.
- Verify that your redirects work from a private window or another browser, not just your main one.
- If you change anything related to redirects, clear your browser cache so you are not debugging stale 301s.
3. External federation checks
Do not stop at "no errors in the admin UI". From another fediverse account:
- Search for your handle in Mastodon or another ActivityPub client while logged in.
- Follow your account to see if the follow request lands.
- Publish a small note and confirm it arrives on the follower side.
Skipping these checks can quietly cost you a year of visibility.