Version 6.5.3 giving Error 502

Hi, 502 means bad gateway is when PHP is not responding. You should try to check the php log, since there are not changes that could raise this error.

For example a PHP timeout can bring to a 502 error.

Stefano.

I have checked the log and it shows nothing. If plugin is updated, than it gives 502 error. When I deactivate the plugin, the website is loading. When I uploaded the 6.5.2 version again and activated the plugin, the website is working without any problem.

So I can be sure, that the only reason to get the error from the server is, when the latest version of the plugin is activated.

Hi I did a diff between the two version without relevant results. Are you sure there are no errors logged? The 502 should be logged for example, as timeout or fatal error.

Stefano.

There is no entry in log, I’m sure.

You should see in your nginx or paache server if it is a timeout. Long requests can be logged by php, if enabled.

Stefano.

You could try to enter the main settings of newsletter and set it in debug mode. A log file could be generated and accesible from the status panel.

Stefano.

I’m using the 6.5.2 version now. This has no problem. If I update, than the website is not accessible, so I can not set debug mode, nor see the status panel. The 6.5.3 version has something, that is causing a 502 error. That’s all, I can “see”.

Hi, what you can attempt is to set the newsletter in debug mode, update it (you’ll have the error), and then look for php logs in our status panel (after downgrading or via FTP).

I’m getting a second code review but really I’m not able to find where the problem is. Could be something generated by another plugin? It sounds like a infinite loop.

Have you custom code or like? If you want I can try to analyze the plugins you have. Contact me at stefano [at] thenewsletterplugin.com.

Stefano.

Hi, do you have php 5.3?

It’s PHP 7.2.3. I know, it needs an update, but I think it should be working on this PHP version, right?

Hi, I asked cause another person had problem, but he was running php 5.3 and there are a couple of line of code which need php 5.6 or greater (we’re adding a check for that on next version).

So, in your case, a 502 look more like a freeze and infinite loop which prevents the blog to complete the response.

In this case at least a timeout should be logged by PHP. Are you aware of blog customization which could interact with our plugin?

What I cannot find diffing the 6.5.2 to 6.5.3 is changed code which runs on plugin startup to explain a blog crash.

The version 6.5.2 you restore is from wp.org or a local backup?

Stefano.

Are you aware of blog customization which could interact with our plugin?

There are some customizations, but not directly related to your plugin. I will make a deeper test soon. I will disable every other plugin and update your plugin to 6.5.3. And set the default theme to be sure, there is nothing to be in conflict.

The version 6.5.2 you restore is from wp.org or a local backup?

It is from wp.org.

Update: plugin upgraded to 6.5.5 and it is still generating 502 error on the site. Downgrading to 6.5.2 works fine without any errors. So I still can not upgrade it to the latest version.