Thanks @girish maybe automatic detection could be achieved with something like https://github.com/lycheeverse/lychee

Yes, that's exactly the same issue I faced. Enabling it does work, but it looks like the social/activitypub features are broken.

Yes, you have to setup transactional email as per https://docs.cloudron.io/apps/ghost/#email . Many of the things are hardcoded and there's also a step by step guide at https://forum.cloudron.io/topic/7043/how-on-earth-do-you-get-ghost-memberships-and-newsletters-working-with-cloudron/21 by @jdaviescoates

Right.. with node 22 it does not load root@168af0b1-79ac-45e0-84ed-54d64b54cfcf:/home/cloudron/ghost/versions/5.110.4# node Welcome to Node.js v22.14.0. Type ".help" for more information. > Error: Could not open history file. REPL session history will not be persisted. > require('@tryghost/html-to-mobiledoc') Uncaught Error: Cannot find module '@tryghost/kg-parser-plugins' Require stack: - /home/cloudron/ghost/versions/5.110.4/node_modules/@tryghost/html-to-mobiledoc/lib/converter.js - /home/cloudron/ghost/versions/5.110.4/node_modules/@tryghost/html-to-mobiledoc/index.js - <repl> at Function._resolveFilename (node:internal/modules/cjs/loader:1225:15) at Function._load (node:internal/modules/cjs/loader:1055:27) at TracingChannel.traceSync (node:diagnostics_channel:322:14) at wrapModuleLoad (node:internal/modules/cjs/loader:220:24) at Module.require (node:internal/modules/cjs/loader:1311:12) at require (node:internal/modules/helpers:136:16) at Object.<anonymous> (/home/cloudron/ghost/versions/5.110.4/node_modules/@tryghost/html-to-mobiledoc/lib/converter.js:4:31) at Module._compile (node:internal/modules/cjs/loader:1554:14) at Object..js (node:internal/modules/cjs/loader:1706:10) { code: 'MODULE_NOT_FOUND', requireStack: [ '/home/cloudron/ghost/versions/5.110.4/node_modules/@tryghost/html-to-mobiledoc/lib/converter.js', '/home/cloudron/ghost/versions/5.110.4/node_modules/@tryghost/html-to-mobiledoc/index.js', '<repl>' ] } With node 20, it works fine: root@718c9254-490c-4da1-8479-d7977bc2217b:/home/cloudron/ghost/versions/5.110.4# node Welcome to Node.js v20.18.3. Type ".help" for more information. > Error: Could not open history file. REPL session history will not be persisted. > require('@tryghost/html-to-mobiledoc') { toMobiledoc: [Function (anonymous)] } Will pin node in the ghost package - https://git.cloudron.io/packages/ghost-app/-/merge_requests/47

Is the page behind Cloudflare or some other site proxy? It's possible some WAF is filtering something out.

@joseph said in Is there a way to get the theme files running on git?: @roofboard are ghost themes simply uploaded to a directory inside /app/data ? Yes, simple uploading works /app/data/content/themes I haven't tried it, but wouldn't SFTP uploads work fast enough here? Just noticed your last bulletpoint

@wmlutz said in Emojis in email render incorrectly: They still aren't happy with v5.108.2 and recommend rolling back. https://forum.ghost.org/t/html-encoding-issue-in-emails-nbsp-amp-etc/54798/18 Any guidance on how to do this in my cloudron deployment? My members are getting cranky. The fix mentioned there has already been released (see https://forum.ghost.org/t/html-encoding-issue-in-emails-nbsp-amp-etc/54798/13 ) and has already been on Cloudron for a while as @joseph just mentioned

@rosano said in How to add this new anti bot sign-up configuration on Cloudron?: Ghost recently made a UI for this https://ghost.org/changelog/signup-spam-protection/ Thanks for the headsup! Odd that it isn't pre-poluated with the links I've already added using the previous config method!

@canadaduane thanks, might help someone! BTW FYI (and anyone else who doesn't know or who has forgotten), you can also check here: [image: 1739180184561-907f3e52-dfa3-4dc2-85b3-e30c0d6dfe16-image.png] The Admin Page will take you to /ghost and it's also mentioned in the First Time Setup which you can view again but choosing it from this menu

@brianb you have to use the Web Terminal to view the full filesystem of an app. The File manager only shows the data directory (/app/data) of an app.

Ah, just found it - apparently, I restrict access to the page in the general settings, and then in the settings of the individual post, I can set access to "public". Then the page itself is still password-protected, but the text is now included into the API call.

@jdaviescoates Yes, great news, they seem to make good progress about it : https://activitypub.ghost.org/day5/

@shrey ah, I understood now! There is a small chance that the upstream Ghost forum has 'rebels'

Nevermind. In case someone finds this, you can enable it in the config. https://docs.cloudron.io/apps/ghost/

@pxlcodes one idea is to to install and build the theme locally on your laptop. Then , you can push the build via the Cloudron CLI tool (npm install cloudron) or just upload it via the File manager. I think, otherwise, we have to install all the devtools that a theme requires (which is unknown ahead of time). At the end of the day, the theme is only create static html/css/js files.

Yes, confirmed it becomes error because of SSL configuration. Sometimes we need to check the SSL configuration. My case, the website is refusing the connection because I set the SSL to flexible. On the hand the configuration must be set to full strict or full. Because the Cloudron uses valid SSL and it can't be used the flexible configuration.

I see you've found a solution, but you don't just add here, you need to change in other places too. I will add all the possible settings of what you need to set, so that other people know how to set it. Sorry that it took a long time. But my private life has been pounding me [image: 1707587036442-1-resized.png] [image: 1707587036956-2-resized.png] [image: 1707587037336-3-resized.png] [image: 1707587037720-4-resized.png] [image: 1707587037965-5-resized.png] [image: 1707587038347-6-resized.png] [image: 1707587038579-7-resized.png] [image: 1707587038952-8-resized.png]

The simpler approach and what @girish is suggesting is to keep a separate install of WP and Ghost in 2 different apps and join them via the rev proxy config from one of them to keep the desired (sub)domain. Another option is the embeded iframe from the /blog page that pulls in the other URL. Let us know what you come up with as a final solution