Skip Navigation

[Resolved] 502 Bad Gateway NGINX error

This support ticket is created 5 years, 3 months ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun Mon Tue Wed Thu Fri Sat
- 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 -
- 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 -

Supporter timezone: Asia/Karachi (GMT+05:00)

Tagged: 

This topic contains 5 replies, has 2 voices.

Last updated by louE 5 years, 3 months ago.

Assisted by: Waqar.

Author
Posts
#1351057

When I try to access the admin for my products in WooCommerce
hidden link

I get a 502 Bad Gateway on NGINX

The php-error.log shows this

Uncaught Error: Call to undefined function WP_Filesystem() in /srv/bindings/15d305c250994a188bc556fb2053764d/code/wp-content/plugins/types/vendor/otgs/installer/includes/class-otgs-installer-source-factory.php:6
Stack trace:
#0 /srv/bindings/15d305c250994a188bc556fb2053764d/code/wp-content/plugins/types/vendor/otgs/installer/includes/upgrade/class-otgs-installer-upgrade-response.php(128): OTGS_Installer_Source_Factory->create()
#1 /srv/bindings/15d305c250994a188bc556fb2053764d/code/wp-content/plugins/types/vendor/otgs/installer/includes/upgrade/class-otgs-installer-upgrade-response.php(63): OTGS_Installer_Upgrade_Response->append_site_key_to_download_url('hidden link...', 'LI09oYJfDq', 'toolset', 'hidden link...')
#2 /srv/bindings/15d305c250994a188bc556fb2053764d/code/wp-includes/class-wp-hook.php(288): OTGS_Installer_Upgrade_Response->modify_upgrade_response(Object(stdClass))
#3 /srv/bindings/15d305c250994a188bc556fb2053764d/code/wp-includes/plugin.php(208): WP_Hook->apply_fil

I've read about reinstalling the Toolset Types plugin possibly helping to fix this, but I have a lot of data I want to keep and uninstalling the plugin looks like it will delete all my data.

#1351187

Also, I've tried reverting to PHP 7.1 as well as testing on PHP 7.2
The site was developed on 7.1 and I moved it to Pantheon from my local environment. Pantheon was running 7.3 for the site and I changed that to 7.1 thinking it might fix the issue but it did not.

I'm currently running 7.2

#1351395

Hi Lou,

Thank you for contacting us and I'd be happy to assist.

To ensure that the Toolset Types plugin's existing data and settings are not lost, you can re-install the plugin files, manually.
( instead of deleting them from the admin area )

Here are the steps:

1. Please make a complete backup copy of the website.

2. Deactivate ( but don't delete ) the Toolset Types plugin from the plugin section in the admin area.

3. Using the FTP access or hosting's file manager tool, delete the "types" folder at "wp-content/plugins/" folder.

4. Download the latest Types version from the downloads page ( https://toolset.com/account/downloads/ ) and unzip the files on your computer.

5. Upload the same "types" folder in place of the deleted folder and then activate the plugin.

I hope this helps and please let me know how it goes.

Important note: In case the issue still persists, it would be a good idea to test the clone of your website on a different server, to rule out any server environment related conflict.

regards,
Waqar

#1351901

I will probably need to test this out some more. I replaced the Types folder with the latest download and I'm still getting the 502 error. I've been back and forth with Pantheon support as well with no solution.

I may have to take your advice and test it all on a different server environment.

#1352185

Hi Lou,

Thanks for the update and sorry to learn that the issue still persists.

Yes, testing the website on a different server should make it more clear.

Please let me know how it goes.

regards,
Waqar

#1353139

After a lot of testing and reading log files, it came down to a single image that was taking too long to resize when calling the products admin table page. Once I resized the original image down from 8000px wide to 2000px, everything loaded fine.