Ghost - changing to HTTPS and stop it from appending :80 to everything

francis1 2016-08-03 23:30:08 UTC #1

Hey folks,

I just commissioned the latest Ghost AWS image. It's online and working, I've added a custom domain, switched out the SSL certificates and removed the bitnami logo.

I'm however struggling with a couple of things. When adding new navigation links, it keeps adding :80 to the end of my urls, eg. http://hostname:80/news:80/ - is there any way to stop this behavior? Also I want to use HTTPS by default - I can load over HTTPS initially but when I start clicking around the site it takes me back to HTTP - is there a setting to prefix everything with HTTPS://?

Cheers,
Francis

tomasp 2016-08-10 08:40:05 UTC #2

Hello francis1,

About the port 80 in the url, you can solve it by editing the file /opt/bitnami/apps/ghost/htdocs/config.js and deleting :80 from the property url inside the prodution section.

    production: {
        url: 'http://104.155.125.109:80',

After that you will need to restart the services:

sudo /opt/bitnami/ctlscript.sh restart

Then you can log in to your admin site, go to "Navigation" and fix your URLs

Regarding how to force HTTPS, you could follow this guide:

https://docs.bitnami.com/aws/components/apache/#how-to-force-https-redirection-for-an-application

I hope it helps,
Tomas

Ghost bnconfig not opening

sudhakarve 2017-11-14 12:23:32 UTC #3

Hi there,

I do have the same issue but it is not resolving even though I have changed the config.js file and deleted :80 from the property url. Another thing is, :80 is getting added before the URL as given below.

http://blog.abcdef.com:80/:80tag/
http://blog.abcdef.com:80/:80tag/industrial-automation/

I tried removing :80 from config.js & config.production.json as well but there are no benefit. Could anyone give me the solution please.

Regards, Sudhakar

jsalmeron 2017-11-15 09:07:09 UTC #4

Hi,

Could you share the parts of the configuration files you edited?

Best regards,

Javier J. Salmerón

Was my answer helpful? Click on

sudhakarve 2017-11-15 10:56:09 UTC #5

Hi,

This is what I have done from my end. Initially, it was with IP address so I just followed the procedure given in your docs.
https://docs.bitnami.com/aws/apps/ghost/

First I changed /opt/bitnami/apps/ghost/htdocs/config.production.json. Below is what is there inside the json.

Production:{
"url": "http://blog.abcdef.com",
"server": {
"port": 2368,
"host": "127.0.0.1"
},
}

Followed by bnconfig with
sudo /opt/bitnami/apps/ghost/bnconfig --machine_hostname blog.abcdef.com

Also, did a mistake of changing /opt/bitnami/apps/ghost/config.js but I reverted. Post making all the changes, I have restarted the service.

Currently, /opt/bitnami/apps/ghost/htdocs/config.js is blank and there is nothing.

There is also an error saying Ghost could not be stopped when I perform restart operation. I am not sure if this could also be helpful.

Thanks for your help.

Regards, Sudhakar

jsalmeron 2017-11-16 11:29:42 UTC #6

Hi,

I just launched our newest Ghost instance and executed this command

sudo /opt/bitnami/apps/ghost/bnconfig --appdomain mydomain.net

And I got my site up and running without issues.

Could you try this procedure with a fresh instance?

Best regards,

Javier J. Salmerón

Was my answer helpful? Click on

DanielFarina 2019-06-12 04:49:54 UTC #7

This is still an issue as of June 2019.

The command to run would be:

`docker exec -it home_ghost_1 ghost config url domainname.com

jota 2019-06-12 07:24:35 UTC #8

Hi @DanielFarina,

Are you using the Bitnami Ghost Docker image? If that's the case, please open an issue in the Github's repository of the solution so our team reviews it.

https://github.com/bitnami/bitnami-docker-ghost/issues

Thanks

sometimescasey 2020-12-06 18:07:33 UTC #9

Hey @sudhakarve thanks so much! It's now end of 2020 but this thread is still helpful.

I found that changing the url under /opt/bitnami/apps/ghost/htdocs/config.production.json and then restarting all the services via bnhelper-tool was all that I needed to do.

I also get errors whenever I start or stop services via /opt/bitnami/bnhelper-tool, as I've tweaked my apache and certificate configs for other things. However I find that as long as mysql, apache, and ghost are up and running when I check status via bnhelper-tool, then there are no issues and my blog works just fine.

I suspect bnhelper-tool is a bit of a wrapper script and maybe just checking for certain outputs so no need to take too literally.

michiel 2020-12-07 09:03:48 UTC #10

Hi @sometimescasey,

Instead of using the bnhelper tool you can also restart the services as follows:

sudo /opt/bitnami/ctlscript.sh restart

Regards,
Michiel

Bitnami provides free all-in-one installers, virtual machines and cloud images for popular open source applications. Get them now!