When I go to my new blog using https://linuxhowto.tech/ it works just fine. When I click on home at the top it works fine.
When I click on the name of the blog and so on it goes to http://localhost:2368/
I can’t see where to change it so URL will always be https://linuxhowto.tech/. I’ve looked through various config files and can’t seem to find what will make this change.
in config.js the url is set to https://linuxhowto.tech just as the instructions call for.
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
Accepted Answer
The first thing I would recommend changing is this server block:
server {
listen 80;
server_name linuxhowto.tech;
location / {
return 301 https://$server_name$request_uri;
}
}
When it comes to HTTP -> HTTPS redirects, you don’t need to specify a location block. All you need to use is:
server {
listen 80;
server_name linuxhowto.tech;
return 301 https://$server_name$request_uri;
}
Beyond that, I just setup and ran a test installation of Ghost + NGINX using your Proxy Config and it’s working without any issues, so it may be the above that’s causing the issues.
So for you domain, you should have two server blocks that look like:
server {
listen 80;
server_name linuxhowto.tech;
return 301 https://$server_name$request_uri;
}
server {
listen 443 ssl;
server_name linuxhowto.tech;
ssl on;
ssl_certificate /etc/letsencrypt/live/linuxhowto.tech/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/linuxhowto.tech/privkey.pem;
ssl_prefer_server_ciphers On;
ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
ssl_ciphers ECDH+AESGCM:DH+AESGCM:ECDH+AES256:DH+AES256:ECDH+AES128:DH+AES:ECDH+3DES:DH+3DES:RSA+AESGCM:RSA+AES:RSA+3DES:!aNULL:!MD5:!DSS;
location / {
proxy_pass http://localhost:2368;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header Host $http_host;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_buffering off;
}
}
I went ahead and restarted the droplet but somehow made the problem change to this:
502 Bad Gateway
LOL. From sort of working to flat out broken.
Are you running Ghost on port 80, or trying to, or are you using a web server such as NGINX/Apache to proxy requests to http://localhost:2368
?
If you’ll post your config.js
(comment out sensitive data) and, if using web server, the VirtualHost or Server Block details, we can take a look at those configurations and see what we can find.
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
Full documentation for every DigitalOcean product.
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
Stay up to date by signing up for DigitalOcean’s Infrastructure as a Newsletter.
New accounts only. By submitting your email you agree to our Privacy Policy
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.