Prestashop Administrator issue

[Mohana]

Hi,

    While login the prestashop backend we face the "504 Gateway Time-Out". I have change the php "max_execution_time 600" but it's not working. Please any one help me.

[selectshop.at]

Activate debug modus via FTP change of file named here and read errors you are having while trying to login: https://www.prestashop.com/forums/topic/224525-how-to-turn-on-error-reporting-for-debug-information-blank-page-500-internal-server-error/

Read server error logs. If you don't have access to them via FTP or cPanel, so contact your provider.

[Dh42]

Debug mode is not going to help him with a 504 error, a server admin should know that. 

[selectshop.at]

1 hour ago, Dh42 said:

Debug mode is not going to help him with a 504 error, a server admin should know that. 

Although 50xx error are internal server errors, your remark is not even true. In 99% these errors are shown in combination of other errors you will see on Pretashop scripts either.

[Dh42]

A 504 error under nginx is a time out error. Time out errors do not generate anything with debug enabled since the execution has timed out from the proxy. The time out happens before a header is returned, if a header is returned a timeout will not happen. You are wrong on this, he needs to look at his proxy_error_log or nginx log. 

[selectshop.at]

Sorry, to contradict you. Had this week same error on my ngnix. Due to upstream problems on the script of Prestashops watermak module. So please do not tell me that it is a server error. It is a script error of Prestashop. Only by disabling nginx and php-fpm, returning to php 5.3. as apache module, the script worked and all pictures could be regenerated with watermark.

PHP message: PHP Notice:  Array to string conversion in xxxx/modules/watermark/watermark.php on line 297
2018/02/26 18:30:34 [error] 8507#0: *293500 upstream timed out (110: Connection timed out) while reading response header from upstream, client: xxxx, server: xxxxxx, request: "POST /adminxxxxx/index.php?controller=AdminImages&token=ac9ad8e63d24f4cfb1d49aec3b1dc9f0 HTTP/1.1", upstream: "fastcgi://unix:/xxxx/php-fpm.sock", host: "xxxxxx", referrer: "http: /adminxxxx/index.php?controller=AdminImages&token=ac9ad8e63d24f4cfb1d49aec3b1dc9f0"

So in this case it is not wrong to activate debug mode as well AND read also the error logs of the server, for to see what is running wrong.

 

[Dh42]

Jesus christ. You are running that old and insecure of software? I imagine you might have had issues like that with something that old and insecure. I was speaking about modern and commonly used versions. Sure, there are always people running really weird setups that can cause errors that are very out of the ordinary. It seems like yours is one. 

[selectshop.at]

@Mohana - For me it wasn't an error to activate debug mode and for to read server error log files. It helped in several directions.

@Dh42 - I'm running nothing insecure. I upgraded a PS 1.4.7.3 the first time with 1-click module (which is a nightmare and also buggy) for a new customer. As you know Prestashop removes all watermak of old pictures when you move from legacy to new. And indeed my customer wants all his images watermarked again. So it is a wish of my customer and not mine. I hear what my customer wants and I follow his wishes.

After several attempts and looking for the problem for to put it on debug tracker I tried several other things. In future I will not use this standard image regenertion feature anymore. Discovered better tool based on Json. And BTW the latest watermark module of PS is also having bigs on latest php versions. Besides the 1-click-module is also not to be recommended in this case. Better to update manually.

 

[Dh42]

You must not carry insurance. My insurance would never let me host a client with old, insecure software like that. PHP 5.3 is open to all kinds of attacks that back ports do not cover just simply because of how its made. Read this, 

https://www.reddit.com/r/webdev/comments/4j58rw/how_insecure_is_php_version_53_and_the_mysql/

https://developers.slashdot.org/story/14/12/31/002253/over-78-of-all-php-installs-are-insecure

Software not getting bug fixes is insecure. Especially almost 4 years without a security update. It is on us, the developers, the system admins to draw a line with our clients. I have refused many a request because I have integrity. Its hard to come by when there are a lot of people in the industry that will do anything a client tells them for money. I will not however.

[selectshop.at]

On 1.3.2018 at 7:59 PM, Dh42 said:

You must not carry insurance. My insurance would never let me host a client with old, insecure software like that. PHP 5.3 is open to all kinds of attacks that back ports do not cover just simply because of how its made. Read this, 
 

You didn't catched what I meant. To regenerate the pictures without crashing server, the only option was by DOWNGRADING THE SERVER to that version + without nginx and fast-cgi. With newer php-versions and server techniques you will crash the server with that native options of Prestashop. So a bug on PS core I was trying to identify and debug.

Thanks for the links, but as server specialist I don't need them. I'm quite up-to-date with latest techniques, AND I'm not using any "OLD" server packages for to host my clients !! You simply misunderstood what I've written before.

AND for to make it short: THE BEST WAY FOR TO IDENTIFY AND DEBUG ERRORS is to

1) Activate debug mode and read possible errors there AND

2) to read server error logs as well. Both in combination.