Subscribe button doesn’t work after enabling SSL

Developer help
1

Dear Team
I am new to ghost. I have been struggling to setup ghost since last 2 days. I used bitnami packaged ghost from an AWS AMI

Here are 2 strange problems i am facing

  1. After enabling SSL using the tools provided, the “Subscribe” button is not working
  2. Sometimes my browser is redirecting to https://127.0.0.1:2368/ (But if i open in incognito mode its opening)

If someone can help me here

Regards
Chitta

2

Hey Chitta!

That sounds like the environment variable in your Docker image aren’t set correctly.

Here’s something similar from a few days ago: Subscribe and login button not working - #19 by Rob_Wright

I am unfamiliar with AWS AMI, but you should be able to update environment variables somewhere. Find the url variable and change it to your actual domain name, including https://.

That should do the trick :slight_smile:

3

Hi @jannis
Thanks for a quick response. I did what you suggested but it’s now throws error

Screenshot 2023-10-13 at 11.52.23 AM
Screenshot 2023-10-13 at 11.52.23 AM2104×1474 149 KB

Regards
Chitta

4

When i change it back to http:// and restarts, it works again and serves as https:// in the browser but the subscribe button doesn’t work

Screenshot 2023-10-13 at 11.57.48 AM
Screenshot 2023-10-13 at 11.57.48 AM2106×716 47.4 KB

5

So, I am a bit confused where the 127.0.0.1 comes from – because that is the URL of localhost, which can only be reached when you’re actually on your server.

Can you confirm that the environment variable url is set to https://blogs.acehours.com? Additionally, you’ll need to restart the container after you’ve updated it.

6

Once i make http to https in config.production.json it goes to 127.0.0.1:2368 when i type blogs.acehours.com in browser

I have been struggling with this bitnami packaged AMI. I am now planning to install directly

7

There is a difference between the config.production.json and the environment variables of your server.

My assumption is that the environment variable url is set to http://127.0.0.1:2368 and is therefore overwriting whatever you put into the config file.

So, to solve this, you need to find where you can set environment variables in your AWS setup. Have a look at the thread I shared above – we had the same issue there :slight_smile: