Bug: Setting url: to https in config.js causes a redirect loop

[xtceed]

Issue Summary

Creating a blog which only uses https requires that the links generated by blog.url to be https however I am not able to set this in config.js

If I enter the url: to my blog in config.js as http, then all of my internal links point to http causing users and search engines to get redirected unnecessarily.

Steps to Reproduce

Apache/2.2.22 (Debian) using the following options
RewriteEngine On
RewriteCond %{HTTPS} !=on
RewriteRule ^(.*)$ https://example.com$1 [R=301,L]
ProxyRequests off
ProxyPass / http://127.0.0.1:2368/
ProxyPassReverse / http:/127.0.0.1:2368/

Ghost is running as http but needs to be able to write blog.url as whatever the user wants to specify.

Technical details

• Ghost Version: 0.4.2
• Client OS: Win 7
• Server OS: Debian 7.5
• Node Version: v0.10.28
• Browser: Chrome
• Database: sqlite3

[halfdan]

What is the setting in config.js for url? Did you try setting it to url: 'https://example.com'?

[xtceed]

Right now its http to work, but when I set it to https that's when I get the problem.

[sebgie]

Hello @xtceed and welcome to Ghost.

Ghost is able do what you are trying to achieve but the Apache configuration doesn't seem correct to me. As @halfdan pointed out the url:https://example.com setting does what you are asking for because it'll enforce https for all traffic and output the correct links. Ghost uses the X-Forwarded-Proto header to determine your protocol and therefore it has to be passed from the proxy. This header is missing from the config example above. When it comes to configuring your proxy the forum is probably a better place to ask for instructions as there are more people with Apache experience than you will find here.

[ErisDS]

Going to close this until there is some evidence that it is a bug rather than a configuration/environment issue.

[bravius]

Also got the redirection loop of death when setting the url in config.js to https.... was attempting to proxy Ghost into an existing application. Fixed it by adding the request header 'X-Forwarded-Proto' = 'https'; Thanks to sebgie for the heads-up.

[xtceed]

Bravius could you give an example of what you mean? Thanks.

[jcjones]

xtceed: On Nginx I added proxy_set_header X-Forwarded-Proto https; to my site configuration, such that it reads:

server {
        listen                          443 ssl spdy;

        location / {
            proxy_pass              http://localhost:8080;
            proxy_set_header        X-Real-IP $remote_addr;
            proxy_set_header        X-Forwarded-For $proxy_add_x_forwarded_for;
            proxy_set_header        X-Forwarded-Proto https;
            proxy_set_header        Host $http_host;
            proxy_intercept_errors  on;
        }
}

This stopped the 302 redirect loop on my HTTPS-only blog at https://tacticalsecret.com/

[dustinmatlock]

I can confirm this happens on a DigitalOcean Ghost app install. @ErisDS could you possibly provide the correct settings to fix this? Here's what I have now.

server {
    listen 80 default_server;
    listen [::]:80 default_server ipv6only=on;

    server_name my-ghost-blog.com; # Replace with your domain

    root /usr/share/nginx/html;
    index index.html index.htm;

    client_max_body_size 10G;

    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;
    } 
}

[ErisDS]

@dustinmatlock Please use the forum for support questions, thanks!

[HLFH]

I added proxy_set_header X-Forwarded-Proto https; entry on my ghost.conf (powered by Nginx). Thanks @jcjones ! It's solved now.

[MostDev]

I am having the same issue with my Ghost blog on Azure websites (IIS). When i change the config.js url to https from http it causes a redirect loop.

[dustinmatlock]

You can set the blog to http in config.js and redirect to https. I'm not sure if it's a configuration issue, but it happens on DigitalOcean. This is how I solved the problem. CloudFlare has an easy way to setup redirects, or use the Nginx solution above.

[davidmyersdev]

Adding the line proxy_set_header X-Forwarded-Proto $scheme; worked like a charm!

[esfoobar]

I can confirm I had the redirect loop and with proxy_set_header X-Forwarded-Proto $scheme; on my nginx virtual conf it now works.