Nginx Rewrite Rule with PHP not working properly
up vote
1
down vote
favorite
I have an url structure like this:
- https://subdomain.domain.com/overview/test@hotmail.com
And want to rewrite it to:
- https://subdomain.domain.com/triggers/overview.php?technician=test@hotmail.com
To do so I tried around 1000 combinations which all come basically down to this code:
location /overview/
rewrite ^/overview/(.+)$ /triggers/overview.php?technician=$1 last;
I'm using Ajenti, php-fpm 7 & nginx.
Any Ideas?
Also here the whole .conf-File for context:
server $)
fastcgi_index index.php;
include fcgi.conf;
fastcgi_pass unix:/var/run/ajenti-v-php7.0-fcgi-technicians-php7.0-fcgi-0.sock;
fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
php nginx url-rewriting
asked Nov 8 at 16:50
ilir aga
609
add a comment |
up vote
1
down vote
favorite
I have an url structure like this:
- https://subdomain.domain.com/overview/test@hotmail.com
And want to rewrite it to:
- https://subdomain.domain.com/triggers/overview.php?technician=test@hotmail.com
To do so I tried around 1000 combinations which all come basically down to this code:
location /overview/
rewrite ^/overview/(.+)$ /triggers/overview.php?technician=$1 last;
I'm using Ajenti, php-fpm 7 & nginx.
Any Ideas?
Also here the whole .conf-File for context:
server $)
fastcgi_index index.php;
include fcgi.conf;
fastcgi_pass unix:/var/run/ajenti-v-php7.0-fcgi-technicians-php7.0-fcgi-0.sock;
fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
php nginx url-rewriting
asked Nov 8 at 16:50
ilir aga
609
It looks fine to me. Do you have any access or error logs. Also, you can change the logging level to show the rewrite process in great detail. See this link
– Richard Smith
Nov 8 at 17:40
Thx for the input, unfortunately there is absolutly nothing in the error log, even after enabling the rewrite log. I added the whole file for context informations.
– ilir aga
Nov 9 at 9:53
I should have mentioned that the rewrite logging level is "notice", so you will need to change the statement in your configuration toerror_log /var/log/nginx/technicians.error.log notice;in order to see them.
– Richard Smith
Nov 9 at 9:58
Really curious. After hard restarting nginx it worked. Seems like some caching issue.
– ilir aga
Nov 9 at 10:29
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I have an url structure like this:
- https://subdomain.domain.com/overview/test@hotmail.com
And want to rewrite it to:
- https://subdomain.domain.com/triggers/overview.php?technician=test@hotmail.com
To do so I tried around 1000 combinations which all come basically down to this code:
location /overview/
rewrite ^/overview/(.+)$ /triggers/overview.php?technician=$1 last;
I'm using Ajenti, php-fpm 7 & nginx.
Any Ideas?
Also here the whole .conf-File for context:
server $)
fastcgi_index index.php;
include fcgi.conf;
fastcgi_pass unix:/var/run/ajenti-v-php7.0-fcgi-technicians-php7.0-fcgi-0.sock;
fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
php nginx url-rewriting
asked Nov 8 at 16:50
ilir aga
609
I have an url structure like this:
- https://subdomain.domain.com/overview/test@hotmail.com
And want to rewrite it to:
- https://subdomain.domain.com/triggers/overview.php?technician=test@hotmail.com
To do so I tried around 1000 combinations which all come basically down to this code:
location /overview/
rewrite ^/overview/(.+)$ /triggers/overview.php?technician=$1 last;
I'm using Ajenti, php-fpm 7 & nginx.
Any Ideas?
Also here the whole .conf-File for context:
server $)
fastcgi_index index.php;
include fcgi.conf;
fastcgi_pass unix:/var/run/ajenti-v-php7.0-fcgi-technicians-php7.0-fcgi-0.sock;
fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
php nginx url-rewriting
php nginx url-rewriting
asked Nov 8 at 16:50
ilir aga
609
asked Nov 8 at 16:50
ilir aga
609
edited Nov 9 at 9:55
asked Nov 8 at 16:50
ilir aga
609
asked Nov 8 at 16:50
ilir aga
609
asked Nov 8 at 16:50
ilir aga
609
609
It looks fine to me. Do you have any access or error logs. Also, you can change the logging level to show the rewrite process in great detail. See this link
– Richard Smith
Nov 8 at 17:40
Thx for the input, unfortunately there is absolutly nothing in the error log, even after enabling the rewrite log. I added the whole file for context informations.
– ilir aga
Nov 9 at 9:53
I should have mentioned that the rewrite logging level is "notice", so you will need to change the statement in your configuration toerror_log /var/log/nginx/technicians.error.log notice;in order to see them.
– Richard Smith
Nov 9 at 9:58
Really curious. After hard restarting nginx it worked. Seems like some caching issue.
– ilir aga
Nov 9 at 10:29
add a comment |
It looks fine to me. Do you have any access or error logs. Also, you can change the logging level to show the rewrite process in great detail. See this link
– Richard Smith
Nov 8 at 17:40
Thx for the input, unfortunately there is absolutly nothing in the error log, even after enabling the rewrite log. I added the whole file for context informations.
– ilir aga
Nov 9 at 9:53
I should have mentioned that the rewrite logging level is "notice", so you will need to change the statement in your configuration toerror_log /var/log/nginx/technicians.error.log notice;in order to see them.
– Richard Smith
Nov 9 at 9:58
Really curious. After hard restarting nginx it worked. Seems like some caching issue.
– ilir aga
Nov 9 at 10:29
It looks fine to me. Do you have any access or error logs. Also, you can change the logging level to show the rewrite process in great detail. See this link
– Richard Smith
Nov 8 at 17:40
It looks fine to me. Do you have any access or error logs. Also, you can change the logging level to show the rewrite process in great detail. See this link
– Richard Smith
Nov 8 at 17:40
Thx for the input, unfortunately there is absolutly nothing in the error log, even after enabling the rewrite log. I added the whole file for context informations.
– ilir aga
Nov 9 at 9:53
Thx for the input, unfortunately there is absolutly nothing in the error log, even after enabling the rewrite log. I added the whole file for context informations.
– ilir aga
Nov 9 at 9:53
I should have mentioned that the rewrite logging level is "notice", so you will need to change the statement in your configuration to
error_log /var/log/nginx/technicians.error.log notice; in order to see them.– Richard Smith
Nov 9 at 9:58
I should have mentioned that the rewrite logging level is "notice", so you will need to change the statement in your configuration to
error_log /var/log/nginx/technicians.error.log notice; in order to see them.– Richard Smith
Nov 9 at 9:58
Really curious. After hard restarting nginx it worked. Seems like some caching issue.
– ilir aga
Nov 9 at 10:29
Really curious. After hard restarting nginx it worked. Seems like some caching issue.
– ilir aga
Nov 9 at 10:29
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
accepted
I found the solution myself: The configuration was correct, all I had to do is make sure that nginx is really restarting.
In Ajenti this didn't work through the UI so i tried it through nginx -s reload, which worked.
answered Nov 9 at 10:30
ilir aga
609
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
accepted
I found the solution myself: The configuration was correct, all I had to do is make sure that nginx is really restarting.
In Ajenti this didn't work through the UI so i tried it through nginx -s reload, which worked.
answered Nov 9 at 10:30
ilir aga
609
add a comment |
up vote
0
down vote
accepted
I found the solution myself: The configuration was correct, all I had to do is make sure that nginx is really restarting.
In Ajenti this didn't work through the UI so i tried it through nginx -s reload, which worked.
answered Nov 9 at 10:30
ilir aga
609
add a comment |
up vote
0
down vote
accepted
up vote
0
down vote
accepted
I found the solution myself: The configuration was correct, all I had to do is make sure that nginx is really restarting.
In Ajenti this didn't work through the UI so i tried it through nginx -s reload, which worked.
answered Nov 9 at 10:30
ilir aga
609
I found the solution myself: The configuration was correct, all I had to do is make sure that nginx is really restarting.
In Ajenti this didn't work through the UI so i tried it through nginx -s reload, which worked.
answered Nov 9 at 10:30
ilir aga
609
answered Nov 9 at 10:30
ilir aga
609
answered Nov 9 at 10:30
ilir aga
609
answered Nov 9 at 10:30
ilir aga
609
609
add a comment |
add a comment |
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53212454%2fnginx-rewrite-rule-with-php-not-working-properly%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
It looks fine to me. Do you have any access or error logs. Also, you can change the logging level to show the rewrite process in great detail. See this link
– Richard Smith
Nov 8 at 17:40
Thx for the input, unfortunately there is absolutly nothing in the error log, even after enabling the rewrite log. I added the whole file for context informations.
– ilir aga
Nov 9 at 9:53
I should have mentioned that the rewrite logging level is "notice", so you will need to change the statement in your configuration to
error_log /var/log/nginx/technicians.error.log notice;in order to see them.– Richard Smith
Nov 9 at 9:58
Really curious. After hard restarting nginx it worked. Seems like some caching issue.
– ilir aga
Nov 9 at 10:29