Hello all,
I have read all the topics on the AP, but considering there are no recent threads, and existing ones are not covering this particular issue, I have opened a new one.
Running multiple Ghost (latest 6.19.2) instances in Docker for years. I have zero issues with the setup, but AP is giving me some problems that I’m not sure is it related to a configuration layer or something else.
After a fresh boot, the log is reporting:
[2026-02-26 09:37:35] INFO Checking ActivityPub Webhook state
[2026-02-26 09:37:35] INFO ActivityPub webhooks in correct state
[2026-02-26 09:37:35] INFO Explore Response 200 OK
Visiting the Network section via Ghost admin, everything loads just fine including the Profile page, Reader, accounts that are being followed etc.
What doesn’t work is when trying to visit my profile by clicking the avatar icon/name inside the loaded Profile section, I get: “Profile not found”
This is followed by the browser console error 404:
GET
https://www.blackvoid.club/.ghost/activitypub/v1/account/@index@blackvoid.club
[HTTP/3 404 162ms]
Also, when trying to use the @index@blackvoid.club to search for my profile via Mastadon for example I also do not get the profile loaded.
Blusky sharing/linking works via the configured URL: @index.www.blackvoid.club.ap.brid.gy.
So, my question here is why can’t I locate my profile via Mastadon for example? Is there something that I have not configured or missed?
Reverse proxy is nginx (NPM to be exact) and added blocks look like this in that particular order:
# Serve JWKS from local Ghost app (required for ActivityPub)
location = /ghost/.well-known/jwks.json {
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header Host $http_host;
proxy_pass http://127.0.0.1:2368;
}
location ~ /.ghost/activitypub/* {
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header Host $http_host;
#add_header X-Content-Type-Options $header_content_type_options;
add_header X-Content-Type-Options nosniff;
proxy_ssl_server_name on;
proxy_pass https://ap.ghost.org;
}
location ~ /.well-known/(webfinger|nodeinfo) {
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header Host $http_host;
#add_header X-Content-Type-Options $header_content_type_options;
add_header X-Content-Type-Options nosniff;
proxy_ssl_server_name on;
proxy_pass https://ap.ghost.org;
}
Also I’m not using the selfhosted AP container, but wanted to rely on the ghost provided one, but that is more than obvious from the configuration.
Thanks for any heads up and assistance on the matter!
