Quick answer: To remove social media links in Ghost, go to Settings → General → Social accounts and clear the Facebook and X (Twitter) fields. For share buttons that appear at the bottom of posts, you'll need to edit your theme's Handlebars templates or add custom CSS to

Someone on the Ghost forum put it perfectly: they'd just moved from Squarespace and were used to a built-in social feed widget. They searched "social media feed", "socials feed" — nothing. Ghost's docs explain how to add social icons, but that's

Quick answer: Ghost CMS uses Amazon SES for transactional email (password resets, invites) via SMTP config in config.production.json. For bulk newsletters, you need the ghost-cms-amazon-ses-adapter or a Mailgun-compatible proxy like mailgun-ses-proxy. Neither is plug-and-play, but both work reliably once set up correctly. The Ghost forum thread says it

Quick answer: Ghost confirmation email links go to a 404 for five main reasons: the link expired (Ghost's 10-minute default), a broken welcome page route, a URL mismatch between your config and routes.yaml, a Cloudflare or proxy stripping the token, or the member portal not being enabled.

Quick answer: When ghost restart fails with "Systemd process manager has not been set up or is corrupted," run ghost setup linux-user systemd to rebuild the service file. If that's skipped because the service already exists, delete it from /lib/systemd/system/ and re-run setup. As

Quick answer: A Ghost CMS 500 Internal Server Error means the server encountered an unexpected condition. Common causes include a corrupted database connection, misconfigured Cloudflare SSL mode, a broken theme, low server memory, or a failed Ghost process — each with a specific fix covered below. Your Ghost site was working

Quick answer: Ghost CMS Instagram embeds stopped working automatically after Meta restricted its oEmbed API in 2024–2025. The fix is to grab the official embed code from the Instagram post (three dots → Embed), then paste it into a Ghost HTML card. This renders the post correctly on published pages.

Quick answer: When Ghost CMS admin login stops working after a URL change, the fix is to clear browser cookies for the old domain, ensure your config.production.json has the correct url value, then run ghost restart. Docker users must update the url environment variable and recreate the container.