[Solved] Unable to setup Ghost

[ernestd3]

Although I am not a programmer so I followed up this link https://wiki.helionet.org/Installing_Ghost_CMS

And i thought it is perfectly configured but it's been more than 2hrs since I finished setup.

Can the the administrators look it up for me to see if there is error  in my setup?

Note: my domain is http://akilis.cf

My CPanel user: ernestd3

 

Thanks

[Sn1F3rt]

Please clear your cache. Your Ghost installation has been set up on the website you linked. 

[ernestd3]

Just like magic. Thank you sire 

[Sn1F3rt]

No problem ... If you need help with anything else, let us know! 

[ernestd3]

I am trying make ssl valid but it instead  returns CPanel index page. Please check the link https://akilis.cf again.

Could you please help me figure what I wrong?

Edited May 11, 2020 by ernestd3

[Luigi123]

I am trying make ssl valid but it instead returns CPanel index page. Please check the link https://akilis.cf again.

Could you please help me figure what I wrong?

What do you mean by that? It’s already valid and you’re on Tommy which is do have an automatic SSL Certificate feature.

[ernestd3]

 

I am trying make ssl valid but it instead returns CPanel index page. Please check the link https://akilis.cf again.

Could you please help me figure what I wrong?

What do you mean by that? It’s already valid and you’re on Tommy which is do have an automatic SSL Certificate feature.

 

What I mean is that SSL is now valid but website frontend and backend disappeared  as if there is no script in the ghost directory

[Luigi123]

 

 

I am trying make ssl valid but it instead returns CPanel index page. Please check the link https://akilis.cf again.

Could you please help me figure what I wrong?

What do you mean by that? It’s already valid and you’re on Tommy which is do have an automatic SSL Certificate feature.

What I mean is that SSL is now valid but website frontend and backend disappeared as if there is no script in the ghost directory

Ah I think you talking about this domain ernestd3.heliohost.org that isn’t forcing it using https.

 

Add this code inside the .htaccess file if you don’t have one yet.

 

RewriteEngine On
RewriteCond %{HTTPS} !=on
RewriteCond %{REQUEST_URI} !^/\.well-known/acme-challenge/[0-9a-zA-Z_-]+$
RewriteCond %{REQUEST_URI} !^/\.well-known/pki-validation/[A-F0-9]{32}\.txt(?:\ Comodo\ DCV)?$
RewriteRule ^ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

[Krydos]

There you go https://akilis.cf/

[ernestd3]

Thanks

[ernestd3]

There you go https://akilis.cf/

If you don't mind, please can you tell what was wrong and how you fixed it?

Apologies for being too inquisitive. I am here to learn

[Krydos]

Normally when you do the Register Application step it creates two files. One for http and one for https. When I checked your account the https one was missing, so that's why it worked over http, but not https. To fix it I copied the http setting over to the https virtualhost and restarted apache.

 

The reason I think it happened is you probably added that domain, and then quickly registered the application prior to autossl running and setting up ssl for that domain. Since the https virtualhost didn't exist at the time register application couldn't create both records like it normally does. To fix it yourself you probably could have just ran the register application step of the guide again, and waited two hours for apache to restart. To prevent it from happening in the future, just make sure ssl is working before you register the application.

[ernestd3]

Normally when you do the Register Application step it creates two files. One for http and one for https. When I checked your account the https one was missing, so that's why it worked over http, but not https. To fix it I copied the http setting over to the https virtualhost and restarted apache.

 

The reason I think it happened is you probably added that domain, and then quickly registered the application prior to autossl running and setting up ssl for that domain. Since the https virtualhost didn't exist at the time register application couldn't create both records like it normally does. To fix it yourself you probably could have just ran the register application step of the guide again, and waited two hours for apache to restart. To prevent it from happening in the future, just make sure ssl is working before you register the application.

All what you said is noted. Gratitude for the knowledge