Unable to sign up for newsletters

Hi

I’m running into issues with the newsletter feature in ghost. The newsletter portal just seems to never open up. Going to my blog/#/portal/signup doesn’t show anything either.

Running ghost version 6.0.9(docker), SMTP has been properly configured with brevo, newsletter has been setup with Mailgun properly. Is there anything else left to do?

Testing on Arc/Chromium, don’t see anything related in the console and network tab.

You have mixed content errors. That’ll cause most browsers to not load javascript. You can fix that by making sure that everything is http, or everything is https.

Hi Cathy

I’m setting up the URL variable in my docker compose as url: ``http://$``{DOMAIN:?DOMAIN environment variable is required} and using caddy separately as
```

blog.hiibi.xyz {
        bind unix//home/satindar/.blog.hiibi.xyz.webserver.sock|777

    reverse_proxy 127.0.0.1:2368 {
        header_up X-Forwarded-Proto 'https'
        header_up X-Forwarded-Host {host}
        header_up Host {host}
        header_up X-Real-IP {remote_host}
        header_up X-Forwarded-For {remote_host}
    }
}

Since it been mentioned to do it that way in the docs, if you’re have ghost behind a proxy.

My Caddy instance can handle SSL by itself, so I’ve made sure ghost uses http instead of https in the docker compose, could that be causing the issue?

Setting the URL to https in the docker compose seems to put me in an infinite redirect loop, I’ve verified that the caddy is passing on X-Forwarded-Proto but Ghost doesn’t seem to do anything. Is there something I’m missing?

Hi @Cathy_Sarisky
Would you be able to help with this?

Sorry, your setup is sufficiently different than mine, so I don’t have anything to contribute here. Ghost’s new ghost-docker repo does use Caddy out in front of Ghost, so it may be worth taking a look there for exactly how they set it up, since that presumably is a working configuration!

GitHub - TryGhost/ghost-docker

All good, managed to resolve it.

It ended up being an issue with my host, contacted them a few days ago and they were able to fix it for me just now.

Thanks for the help!

1 Like