I successfully upgraded my self-hosted CLI 5.0 to Docker 6.0.
Right now Iām not a big poster, so I was hoping to piggyback on Ghostās own ActivityPub infrastructure. But when I click on my Profile, I get this āYour account has been suspended due to policy violationsā message⦠before I have had a chance to violate any policies.
A few years back, I did have a Ghost(pro) account, so the backend may be picking up on that.
I saw that yesterday at one point in my saga to get it working. It didnāt mean anything scary at the time, itās just that something is going wrong with validation.
Are you front end and admin panel on the same subdomain, or different?
It sounds like something is not quite right here. Youāll want your non-admin domain to redirect /ghost (and /ghost/* possibly?) to your admin domain.
Your Ghost install āphones homeā to ActivityPub (if youāre using the Ghost.org-hosted version) when you start Ghost. So after you change config, you need to restart Ghost so that it can try again.
Iām having similar issues; Iāve gotten this error before, as well as
Rate limit exceeded
Youāve made too many requests. Please try again in a moment.
Iām self-hosted, and I believe Iāve added everything I need to my nginx configs, but having trouble getting in. Only the āexploreā page loads. Any ideas?
I just went through the process of getting my setup working. I got this policy violation when these factors were true:
Activitypub container was working as expected.
Ghost container was not resolving my domain.
For my setup (kubernetes) I had to change the ndots dns settings so it would resolve my hostname with only one dot in it. Changing ndots from 5 to 1 solved my issue.
If your ghost container can resolv it, it just might need a restart.
I just made ActivityPub working in my setup (selfhosted using apache reverse proxy) and I have this same message. I could not see any errors when docker starts.
I forgot to add that Iām using a domain ending on .cc and that iām using the same domain as admin (i couldnāt configure a subdomain yet)
(Strangely, I saw the same issues when using the new Docker install method when self-hosting with a new domain. Turned on āNetworkā, went to the Network tab, and the console was riddled with 403 errors. When self-hosting, I also completed a fresh install and used the self-hosted AP option, and that swapped the 403s for 500s.)
We just fixed a bug that was causing the app to render āAccount suspendedā wrongly, for users that have not set up ActivityPub correctly. No account has been blocked!
If youāre having trouble with setting up ActivityPub, I invite you to start a fresh thread with more information on your current config, so that we can help debug.