I created a new Pro account and have setup a custom domain. I added my mastodon account in the social networks list ( about 24 hours ago ).
Mastodon can see the account, but isn’t getting notices.
On the Ghost account’s network dashboard it says profile doesn’t exist and there are no notes. I can’t add a note.
Preferences does bring up profile settings, but I can’t actually change anything.
The Social Web Handle says, “Could not load your Social Web handle.”
Access and subscribe are set to public.
Do we have to have a facebook account to activate the social web profile?
Aside from custom domain and adding the URL for the Mastodon account is there something I need to do to enable Ghost working with Mastodon/ActivityPub ?
No, you don’t need a Facebook account. Ghost’s social web runs on ActivityPub and doesn’t depend on Facebook or any other social login.
A few things that might be tripping this up:
The Mastodon link you added under social accounts only puts a link on your site. It doesn’t connect the two accounts. Your Ghost site gets its own social web identity, which by default is @index@yourdomain.com. Your Mastodon account will only see your posts once it follows that handle (search for it from Mastodon).
Make sure the social web is switched on. In Settings, search for “Network” (in Ghost 6 it sits under Growth) and check that the toggle is on. Private mode also needs to be off, which it sounds like it already is.
Check whether the handle exists at all. Open this in a browser, with your own domain in place of yourdomain.com: https://yourdomain.com/.well-known/webfinger?resource=acct:index@yourdomain.com
If you get a small block of JSON back, the profile exists and the problem is on the Admin side. If you get a 404 or an error, the profile most likely hasn’t been set up yet.
The custom domain has to be the site’s main domain, not a subdirectory like yourdomain.com/blog. My guess is that because the site started on a ghost.io address and the custom domain was added afterwards, the social web profile didn’t get set up for the new domain. On Ghost(Pro) that’s something only their support team can fix from their side, so it’s worth emailing them with your site URL and the exact “Could not load your Social Web handle” message. A full day is already longer than DNS and SSL usually need, so I wouldn’t keep waiting on it.
Disclosure: I drafted this with AI assistance and checked it against Ghost’s social web help page before posting.
I did open a ticket with support over the weekend and they started working it Monday, but they haven’t been able to reproduce the issue from the admin side.
Thanks for checking. That JSON is a good sign, and I looked at the public side of your profile too. Your actor at /.ghost/activitypub/users/index loads fine, your outbox has your two articles from Oct 16 (“Name-dropping” and “Neuron crafted experiments in story-telling”), and your followers list shows one follower, which I’m guessing is your Mastodon account. So federation itself looks like it’s working, and the problem seems to be only in the Admin side.
That might also explain the missing notices on Mastodon. Mastodon only shows posts that arrive after you follow someone, and it doesn’t pull in older ones. If you followed after Oct 16, those two articles won’t show up in your home feed even though everything is set up right. Publishing a short test post now should show whether new posts get through.
For the “Could not load your Social Web handle” error, it might help to give support the details above: that webfinger, the actor and the outbox all return correctly from outside, and only the Network tab and handle fail inside Admin. That points them at the Admin app or your account record rather than DNS. A hard refresh or a private window is worth one try too, in case the Admin app cached the old ghost.io address.
(Drafted with AI assistance; I checked your public profile URLs directly before posting.)
Thanks for testing that. One more data point for your ticket: your new post “Reaching out to Fediverse” (Oct 21) does show up in your public outbox, so Ghost is creating the post fine. It just isn’t reaching your Mastodon follower. That suggests the problem is delivery from Ghost’s side to Mastodon, not your setup. It might help to tell support exactly that, and include the Mastodon server your account is on. Would be great if you could post the fix here once they find it. (Drafted with AI assistance.)