FURLs not working after upgrade (2.1.3-pl) - My Forums

Re: FURLs not working after upgrade (2.1.3-pl)

pixelchutes — Sep 23, 2011, 04:56 PM

NOTE: This above solution may become problematic when you _don't_ want HTTPS set to "on".

By adjusting to the following, you can essentially "set it and forget it":

Place in the "http" context:

map $scheme $php_https { default off; https on; }

See: http://wiki.nginx.org/HttpMapModule

Then, in your fastcgi_params include, simply reference your new map variable via:

fastcgi_param HTTPS $php_https;

:) (Thx kolbyjack in #nginx)

Re: FURLs not working after upgrade (2.1.3-pl)

pixelchutes — Sep 23, 2011, 02:34 PM

Has anyone here ran into a "redirect loop" issue with MODx via nginx? ...it's currently only happening for me off the homepage "/", however this is on Evo 1.0.5. with SEO Strict plugin.

(Not sure if it's related, but thought I'd check here....)

@Roland, thanks for posting the nginx conf ... good use of try_files and @modx upstream to preserve GET vars. Well done!

UPDATE:

Should have thought of this sooner! Simply disabled "Strict URLs" Plugin, and voila! "redirect loop" went away.... (We have our culprit! )

UPDATE 2:

This issue only showed up as a result of "forced HTTPS" -- Turns out that $_SERVER['HTTPS'] was _not_present in this nginx/php-fpm build $_SERVER vars, while it was there for original Apache setup...

This resulted in the condition (http://domain.com != https://domain.com) always equating "false", and forcing the redirect (loop) to the HTTPS strict URL.

The following nginx config adjustment did the trick:

fastcgi_param HTTPS on;

Re: FURLs not working after upgrade (2.1.3-pl)

markh — Sep 23, 2011, 01:43 PM

Thanks for posting that Roland.

As I honestly am not skilled with this server stuff but I suspect others may be looking for this topic at a later stage I linked to it from the Nginx Server Config documentation as an alternative.

Re: FURLs not working after upgrade (2.1.3-pl)

towerofbabel — Sep 22, 2011, 01:59 PM

Hi Roland,

That did it.

Thanks a lot for the config.

Re: FURLs not working after upgrade (2.1.3-pl)

rfirmont — Sep 21, 2011, 11:58 AM

The main error here is the capturing of the first slash.
Some config changes (i use a similiar config for a modx revo site):

server {
	listen 80;
	server_name www.financetrails.com financetrails.com;
	root /path/to/www.financetrails.com;
	index index.php index.html;

	location / {
		#try to get file directly, try it as a directory or fall back to modx
		try_files $uri $uri/ @modx;
	}

	location @modx {
		#including ? in second rewrite argument causes nginx to drop GET params, so append them again
		rewrite ^/(.*)$ /index.php?q=$1&$args;
	}

	location ~ \.php(.*)$ {
		include fastcgi_params;
		fastcgi_pass backend;
		fastcgi_index index.php;
		fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
	}
}

also make sure you have

cgi.fix_pathinfo=0

inside your php.ini, otherwise you might be susceptible to attacks via uploaded php files.

Re: FURLs not working after upgrade (2.1.3-pl)

leeboone — Sep 21, 2011, 08:09 AM

I'm not a server expert either, but if I were having this problem I'd do a clean install of 2.1.3 and build a quick test site to rule out something in your ported site causing a conflict.
Of course, this thread is 10 days old, so you may have already done this…

Re: FURLs not working after upgrade (2.1.3-pl)

towerofbabel — Sep 21, 2011, 02:05 AM

oh, ok, no related errors in the modx error log either....

Yes, I got the config from there.

Re: FURLs not working after upgrade (2.1.3-pl)

markh — Sep 20, 2011, 06:25 AM

I meant the MODX error log Reports -> Error Log

I'm honestly not into server stuff much, and that server config means nothing to me, lol.

Looks like you got it from here right? http://rtfm.modx.com/display/revolution20/Nginx+Server+Config

Re: FURLs not working after upgrade (2.1.3-pl)

towerofbabel — Sep 19, 2011, 08:25 AM

Hi Mark,

No errors in the nginx error log.

I have reinstalled the original working-gr8-on-apache application on the new machine, with no upgrade to MODX.

The behaviour is now slightly different to how I described earlier, but the end result is that URL rewriting is not working. What I see:

* everything works great with FURLs turned off in MODX.
* If I turn FURLs on, the links are generated correctly in the HTML (eg, "/features/" instead of "index.php?whatever"), but those links do not resolve to the correct pages - they just return me the home page.

Here is my nginx config:

server
{
listen 80;
server_name www.financetrails.com financetrails.com;
root /path/to/www.financetrails.com;
index index.php;

location / {
root /path/to/www.financetrails.com;
index index.php index.html;

# This is the important part - map any extension of
# /blahblahblah that doesn't exist to index.php

if (!-e $request_filename) {
rewrite ^(.*)$ /index.php?q=$1 last;
}
}

location ~ \.php(.*)$ {
include fastcgi_params;
fastcgi_pass backend;
fastcgi_index index.php;
fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;

}

Re: FURLs not working after upgrade (2.1.3-pl)

markh — Sep 12, 2011, 09:04 PM

Had a look at your error log?

Whenever I noticed friendly urls are not being generated it is cause of some URI issues, which could very well be caused by a different move/upgrade method than suggested. Luckily the error log usually notifies you of that though, by filling up a bit on every request.