Ghost version 6 websocket not initialised

[Ahson-Shaikh]

Hi everyone. I'm from Easypanel Team. We are getting an error while upgrading to the latest version of the Image to 6.0.0.

[2025-08-05 10:59:22] INFO Explore Response 200 OK
[2025-08-05 10:59:23] INFO "GET /.ghost/activitypub/v1/site" 301 374ms
[2025-08-05 10:59:23] INFO "GET /.ghost/activitypub/v1/site/" 404 112ms
[2025-08-05 10:59:23] ERROR Could not get webhook secret for ActivityPub FetchError: invalid json response body at https://uptime-kuma-ghost.klorzb.easypanel.host/.ghost/activitypub/v1/site/ reason: Unexpected token '<', "<!DOCTYPE "... is not valid JSON
[2025-08-05 10:59:23] ERROR No webhook secret found - cannot initialise

We would require assistance in solving this. Thanks!

[rusty1281]

Hello,

I have just cloned one of my v5.130 instances, and run the upgrade with the v6.0.0. docker image. I can confirm the same issue:

[2025-08-05 17:17:58] INFO Database is in a ready state.
[2025-08-05 17:17:58] INFO Ghost database ready in 9.062s
[2025-08-05 17:18:00] INFO Invalidating assets for regeneration
[2025-08-05 17:18:02] INFO URL Service ready in 2344ms
[2025-08-05 17:18:03] INFO Adding offloaded job to the inline job queue
[2025-08-05 17:18:03] INFO Scheduling job mentions-email-report at 9 59 * * * *. Next run on: Tue Aug 05 2025 17:59:09 GMT+0000 (Coordinated Universal Time)
[2025-08-05 17:18:03] INFO Pinging Explore with Payload https://explore.ghost.org/api/update {"ghost":"6.0.0","site_uuid":"fa47c70d-4ffe-4d4e-b602-b3f6cfa2ddfe","url":"https://xxxxx.domain.com","theme":"source","facebook":"xxxxx","twitter":"@xxxxx","posts_total":2x30,"posts_last":"2022-05-19T18:08:12.000Z","posts_first":"2019-03-05T22:59:00.000Z"}
[2025-08-05 17:18:04] INFO Adding offloaded job to the inline job queue
[2025-08-05 17:18:04] INFO Scheduling job clean-expired-comped at 54 47 3 * * *. Next run on: Wed Aug 06 2025 03:47:54 GMT+0000 (Coordinated Universal Time)
[2025-08-05 17:18:04] INFO Adding offloaded job to the inline job queue
[2025-08-05 17:18:04] INFO Scheduling job clean-tokens at 9 12 20 * * *. Next run on: Tue Aug 05 2025 20:12:09 GMT+0000 (Coordinated Universal Time)
[2025-08-05 17:18:04] INFO Ghost booted in 14.879s
[2025-08-05 17:18:04] INFO Adding offloaded job to the inline job queue
[2025-08-05 17:18:04] INFO Scheduling job update-check at 33 18 16 * * *. Next run on: Wed Aug 06 2025 16:18:33 GMT+0000 (Coordinated Universal Time)
[2025-08-05 17:18:04] INFO Running milestone emails job on Fri Aug 08 2025 17:18:04 GMT+0000 (Coordinated Universal Time)
[2025-08-05 17:18:04] INFO "GET /.ghost/activitypub/v1/site" 301 503ms
[2025-08-05 17:18:05] INFO Explore Response 200 OK
[2025-08-05 17:18:05] INFO "GET /.ghost/activitypub/v1/site/" 404 277ms
[2025-08-05 17:18:05] ERROR Could not get webhook secret for ActivityPub FetchError: invalid json response body at https://xxxxx.domain.com/.ghost/activitypub/v1/site/ reason: Unexpected token '<', "<!DOCTYPE "... is not valid JSON
[2025-08-05 17:18:05] ERROR No webhook secret found - cannot initialise
[2025-08-05 17:18:08] INFO "HEAD /" 200 325ms
[2025-08-05 17:18:09] INFO "GET /ghost/api/admin/site/" 200 364ms
[2025-08-05 17:18:10] INFO "GET /ghost/api/admin/site/" 200 2ms
[2025-08-05 17:18:13] INFO "GET /" 200 219ms

[rusty1281]

Also, once I have managed to go into the new ActivityPub section, but I can no longer go back as there is the following popup:

This also reflects with the following error in the logs:

[2025-08-05 17:36:31] INFO "GET /.ghost/activitypub/users/index/" 404 28ms
[2025-08-05 17:36:31] INFO "GET /.ghost/activitypub/v1/account/me/" 404 56ms
[2025-08-05 17:36:31] INFO "GET /.ghost/activitypub/v1/feed/reader/" 404 54ms
[2025-08-05 17:36:31] INFO "GET /.ghost/activitypub/v1/account/me/follows/following/" 404 59ms
[2025-08-05 17:36:31] INFO "GET /.ghost/activitypub/v1/blocks/domains/" 404 59ms
[2025-08-05 17:36:31] INFO "GET /.ghost/activitypub/v1/notifications/unread/count/" 404 58ms
[2025-08-05 17:36:31] INFO "GET /.ghost/activitypub/v1/blocks/accounts/" 404 58ms

Looks like a configuration matter, but if we could get some info on what needs to be configured and where, that would be great.

tnx!

[pupontech]

its a traefik issue

[rusty1281]

Guessing you mean a reverse proxy in general. Not using trafik myself but it makes sense. Just waiting to see how to actually resolve it.

tnx!

[pupontech]

sorry easypanel uses traefik
There is a config already provided for caddy in the documentation

[rusty1281]

Would be so kind and just link that documentation? Not sure is it the docker image documentation or the Ghost general documentation.

tnx again!

[rusty1281]

I have added the following reverse proxy settings for the host in question:

location ^~ /.ghost/activitypub/ {
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;
    proxy_pass https://ap.ghost.org;
}

# Proxy well-known endpoints
location = /.well-known/webfinger {
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;
    proxy_pass https://ap.ghost.org;
}

location = /.well-known/nodeinfo {
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;
    proxy_pass https://ap.ghost.org;
}

The errors are no longer present in the logs, but the "Login interrupted" in the dashboard is still present. This makes sense atm as https://ap.ghost.org is down.

[rusty1281]

Pointers came from the Ghost forum post here: https://forum.ghost.org/t/upgraded-but-no-ap/59206

[rusty1281]

This advanced nginx RP config works for me, and the activity pub is up and running just fine:

  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;
}

[pupontech]

Here is the fix

https://forum.ghost.org/t/question-how-to-define-custom-location-block-e-g-ghost-via-traefik-instead-of-caddy/58996/3