When the connection fails, "Couldn't connect to Ghost" appears, and the reason shows in red under the key field on the Ghost page of Project settings. To open it in the editor, click the sliders icon in the icon rail, Project settings, then Ghost. A site that was connected and stopped working shows Needs attention there instead, with the reason under the site's name, for the same causes as below. Your live site keeps working either way; only publishing and the preview of your posts stop.
Your site opens in a browser at the address you entered, and so does Ghost Admin at that address followed by /ghost/. A site in a subfolder, such as https://example.com/blog, works with that full address.
The address starts with https://. Fantasma connects only over HTTPS, and "Ghost URL must use HTTPS" means the site has none yet. Your host can turn on HTTPS for it.
The site is on the public internet. A site on your own computer, such as http://localhost:2368, or on a private network, shows "Ghost URL resolved to a private address". Fantasma cannot reach it, so download the theme instead.
"Ghost URL host could not be resolved" means the address has a typo, or its domain does not point to your site yet. A new domain can take some hours to work everywhere; your domain provider can check it.
Save and verify stays grayed out
The button waits until Ghost site or Admin URL holds a web address and Admin API key or Staff access token holds a key of the right form. The key must be the Admin API key or the Staff access token, a long string of letters and digits with one colon in the middle. Ghost's Content API key, which sits on the same integration screen, has no colon and does not work. Copy the Admin API key instead, as Connect your Ghost site shows. Paste the key alone, without spaces or a line break around it.
Ghost rejected the key
"Ghost rejected the Admin API key or Staff access token. Copy it again from Ghost."
The key was copied with a character missing, it was regenerated in Ghost after you copied it, or its integration was deleted. Copy it again from Ghost Admin, as Connect your Ghost site shows, paste it, and click Save and verify. On a connection that shows Needs attention, click Replace under Access first to get the key field.
The token belongs to an Editor
"This Staff access token belongs to an Editor. Ghost lets only the Owner and Administrators publish themes. Use an Admin API key or an Administrator's token."
The message names the role of the staff user whose token you pasted. Ask the site's Owner or an Administrator to add a custom integration and send you its Admin API key, then paste that key. Connect your Ghost site shows where they find it.
A CDN or firewall blocks Fantasma
"Your Ghost site refused the connection check (HTTP 403) without a Ghost error message. A CDN, firewall, or security rule in front of /ghost/api/admin/ usually causes this."
The same cause can read "Your Ghost site answered the access check with something other than a Ghost response." Something in front of Ghost, such as Cloudflare, a hosting firewall or a login page, answered instead of Ghost. Fantasma calls your site from a server, not from your browser, and such services often block requests from servers.
Allow requests to the path /ghost/api/admin/ in that service. Ghost still asks for the key on every request there, so the rest of your site stays protected. In Cloudflare, look in the security events for blocked requests to that path; each event names the security feature that blocked it. Then add a custom rule for paths that start with /ghost/api/admin/ that skips that feature. When the message ends with "The block page reports error 1020.", one of your own Cloudflare firewall rules made the block, so change that rule to leave the path out. If you cannot change these settings yourself, send the message to your host's support and ask them to allow that path.
The address redirects
"Ghost returned a redirect without a destination. Check the site or Admin URL and try again." or "Ghost URL redirected too many times"
Enter the address your site ends up at in the browser, with or without www as it shows there. If the browser also shows "too many redirects" on your site, the redirect settings at your host or CDN send visitors in a circle; your host can fix them.
The site does not answer
"We couldn't reach your Ghost site." or "Ghost returned an error (HTTP 502)."
The site was down, slow or under maintenance. Fantasma waits 15 seconds for an answer. A site that often takes longer needs faster hosting, which your host can help with. Check that the site opens, then click Save and verify again. On a connection that shows Needs attention, click Check connection under the site's name instead.
Too many tries
"Too many connection attempts." followed by how many seconds to wait.
Your account can try to connect 10 times in 30 minutes, whether the tries work or not. Wait up to 30 minutes.
When the connection fails, "Couldn't connect to Ghost" appears, and the reason shows in red under the key field on the Ghost page of Project settings. To open it in the editor, click the sliders icon in the icon rail, Project settings, then Ghost. A site that was connected and stopped working shows Needs attention there instead, with the reason under the site's name, for the same causes as below. Your live site keeps working either way; only publishing and the preview of your posts stop.
Until the connection works, you can still download your theme and upload it in Ghost yourself.
Check the basics first
/ghost/. A site in a subfolder, such ashttps://example.com/blog, works with that full address.https://. Fantasma connects only over HTTPS, and "Ghost URL must use HTTPS" means the site has none yet. Your host can turn on HTTPS for it.http://localhost:2368, or on a private network, shows "Ghost URL resolved to a private address". Fantasma cannot reach it, so download the theme instead.Save and verify stays grayed out
The button waits until Ghost site or Admin URL holds a web address and Admin API key or Staff access token holds a key of the right form. The key must be the Admin API key or the Staff access token, a long string of letters and digits with one colon in the middle. Ghost's Content API key, which sits on the same integration screen, has no colon and does not work. Copy the Admin API key instead, as Connect your Ghost site shows. Paste the key alone, without spaces or a line break around it.
Ghost rejected the key
"Ghost rejected the Admin API key or Staff access token. Copy it again from Ghost."
The key was copied with a character missing, it was regenerated in Ghost after you copied it, or its integration was deleted. Copy it again from Ghost Admin, as Connect your Ghost site shows, paste it, and click Save and verify. On a connection that shows Needs attention, click Replace under Access first to get the key field.
The token belongs to an Editor
"This Staff access token belongs to an Editor. Ghost lets only the Owner and Administrators publish themes. Use an Admin API key or an Administrator's token."
The message names the role of the staff user whose token you pasted. Ask the site's Owner or an Administrator to add a custom integration and send you its Admin API key, then paste that key. Connect your Ghost site shows where they find it.
A CDN or firewall blocks Fantasma
"Your Ghost site refused the connection check (HTTP 403) without a Ghost error message. A CDN, firewall, or security rule in front of /ghost/api/admin/ usually causes this."
The same cause can read "Your Ghost site answered the access check with something other than a Ghost response." Something in front of Ghost, such as Cloudflare, a hosting firewall or a login page, answered instead of Ghost. Fantasma calls your site from a server, not from your browser, and such services often block requests from servers.
Allow requests to the path
/ghost/api/admin/in that service. Ghost still asks for the key on every request there, so the rest of your site stays protected. In Cloudflare, look in the security events for blocked requests to that path; each event names the security feature that blocked it. Then add a custom rule for paths that start with/ghost/api/admin/that skips that feature. When the message ends with "The block page reports error 1020.", one of your own Cloudflare firewall rules made the block, so change that rule to leave the path out. If you cannot change these settings yourself, send the message to your host's support and ask them to allow that path.The address redirects
"Ghost returned a redirect without a destination. Check the site or Admin URL and try again." or "Ghost URL redirected too many times"
Enter the address your site ends up at in the browser, with or without
wwwas it shows there. If the browser also shows "too many redirects" on your site, the redirect settings at your host or CDN send visitors in a circle; your host can fix them.The site does not answer
"We couldn't reach your Ghost site." or "Ghost returned an error (HTTP 502)."
The site was down, slow or under maintenance. Fantasma waits 15 seconds for an answer. A site that often takes longer needs faster hosting, which your host can help with. Check that the site opens, then click Save and verify again. On a connection that shows Needs attention, click Check connection under the site's name instead.
Too many tries
"Too many connection attempts." followed by how many seconds to wait.
Your account can try to connect 10 times in 30 minutes, whether the tries work or not. Wait up to 30 minutes.
Contact support
If none of these fix it, contact us and send:
Fantasma never shows the key on that page, so the screenshot is safe. Never send the key or token itself.