How to update Ghost Portainer Stack and Cloudflare Tunnels for AP?

Greetings,

I pulled and updated my Ghost instance and I am getting the “Loading interrupted” message. Is there something new I need to add to my Portainer stack compose file or anything I need to adjust to my Cloudflare tunnels for it to work?

Thank you!

2 Likes

So far, the only guidance I’ve seen is “just update your nginx.conf".

Unfortunately, those of us using Cloudflare tunnels don’t have one of those that we can edit.

Greetings,

I pulled and updated my Ghost instance and I am getting the “Loading interrupted” message. Is there something new I need to add to my Portainer stack compose file or anything I need to adjust to my Cloudflare tunnels for it to work?

There’s a similar topic here that may have useful information Upgrade from 5 to 6 using Portainer

I’ve managed to get past the 404 loading interrupted errors by mapping three additional entries for blog.myblogname.com in the Cloudflare tunnel web UI. All of these go BEFORE the existing entry, and have the following for paths:

  • .ghost/activitypub/*
  • .well-known/webfinger
  • .well-known/nodeinfo

The target Service for all of them is https://ap.ghost.org

Unfortunately, now I’m getting rate limit exceeded errors any time I access the Network section in my Ghost admin panel. But, an account now actually shows up on ActivityPub for my blog.

1 Like

This works so far! I am now at your same error with the rate limits. I have opened a new thread:

I think I’m giving up on using Ghost’s complimentary ActivityPub service, and redirecting to a self-hosted ActivityPub server. Looks like that involves creating two new Docker containers, remapping port 8080 of the main ActivityPub container to a free port on my machine, then having Cloudflare tunnels use that instead of ap.ghost.org as the Service.

Here’s the Compose file to help make those containers: ghost-docker/compose.yml at main · TryGhost/ghost-docker · GitHub