Last post 2 hours 13 min ago

Posts last week 141

Average response time last week 4 hours 42 min

All time posts 67832

All time tickets 10481

All time avg. posts per day 21

Helpdesk is open from Monday through Friday CET

Please create an (free) account to post any question in the support area.

Please check the development versions area. Look at the changelog, maybe your specific problem has been resolved already!

All tickets are private and they cannot be viewed by anyone. We have made public only a few tickets that we found helpful, after removing private information from them.

#2631 – Nginx 404 Profile

Posted in ‘sh404SEF’

This is a public ticket. Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Friday, 19 August 2016 19:56 UTC

configgamer

Hi,

If i use Nginx, i have 404 error when there is a "?" in URL .
For exemple : "http://www.xxxx.fr/Profil/Aller-sur-le-profil/?userid=62"

In the log :

[Fri Aug 19 17:47:25.689576 2016] [fcgid:warn] [pid 6048] [client xxxx] mod_fcgid: stderr: thrown in /var/www/vhosts/xxxx.fr/public_html/plugins/system/redirect/redirect.php on line 55
[Fri Aug 19 17:48:17.234349 2016] [fcgid:warn] [pid 6048] [client xxxx] mod_fcgid: stderr: PHP Fatal error: Uncaught TypeError: Argument 1 passed to PlgSystemRedirect::handleError() must be an instance of JException, instance of Error given, called in /var/www/vhosts/xxxx.fr/public_html/administrator/components/com_sh404sef/classes/router.php on line 1992 and defined in /var/www/vhosts/xxxx.fr/public_html/plugins/system/redirect/redirect.php:55
[Fri Aug 19 17:48:17.234377 2016] [fcgid:warn] [pid 6048] [client xxxx] mod_fcgid: stderr: Stack trace:
[Fri Aug 19 17:48:17.234382 2016] [fcgid:warn] [pid 6048] [client xxxx] mod_fcgid: stderr: #0 /var/www/vhosts/xxxx.fr/public_html/administrator/components/com_sh404sef/classes/router.php(1992): PlgSystemRedirect::handleError(Object(Error))
[Fri Aug 19 17:48:17.234386 2016] [fcgid:warn] [pid 6048] [client xxxx] mod_fcgid: stderr: #1 /var/www/vhosts/xxxx.fr/public_html/administrator/components/com_sh404sef/classes/router.php(1972): Sh404sefClassRouterInternal->sh404sefErrorPage(Object(Error))
[Fri Aug 19 17:48:17.234390 2016] [fcgid:warn] [pid 6048] [client xxxx] mod_fcgid: stderr: #2 [internal function]: Sh404sefClassRouterInternal->sh404sefExceptionHandler(Object(Error))
[Fri Aug 19 17:48:17.234393 2016] [fcgid:warn] [pid 6048] [client xxxx] mod_fcgid: stderr: #3 {main}
[Fri Aug 19 17:48:17.234396 2016] [fcgid:warn] [pid 6048] [client xxxx] mod_fcgid: stderr: thrown in /var/www/vhosts/xxxx.fr/public_html/plugins/system/redirect/redirect.php on line 55

Can you help me ?

Saturday, 20 August 2016 09:16 UTC

wb_weeblr

Hi

This is not related to Nginx. It's a change in Joomla a few versions back, that was not backward compatible. I think they fixed it later on, and we also added a workaround for it in later versions.

This would indicate that you are not running up to date versions of Joomla and/or sh404SEF.

In addition, the error is happening as you can see in the Joomla Redirect system plugin. As a quick fix, you can disable that plugin anyway, it's not used when sh404SEF is enabled.

Rgds

Saturday, 20 August 2016 10:00 UTC

configgamer

Hi,

Version :
The last version of joomla 3.6.2
The last version of sh404SEF 4.7.3.3292
PHP : 7.0.9

If i use , Application Fast CGI Apache : it's OK
If i use , PHP-FM Nginx , 404 for URL profile jomsocial

[*]

Monday, 22 August 2016 08:21 UTC

wb_weeblr

Hi

sh404SEF does not deal with the web server. As you can see on your first screenshot, the 404 error you are getting is generated by the web server, nginx. It is not generated by Joomla or sh404SEF:

https://weeblr.com/images/screenshots/xxxx

The errors you are seeing in your PHP logs:

- are NOT 404 errors. A PHP error causes a 500 error, not a 404
- can be easily solved by disabling the system redirect plugin, as already mentioned.

Rgds

Tuesday, 06 September 2016 05:34 UTC

system

This ticket has been automatically closed. All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.

This ticket is closed, therefore read-only. You can no longer reply to it. If you need to provide more information, please open a new ticket and mention this ticket's number.