Skip Navigation

[Resolved] URGENT: 502 bad gateway since latest update

This support ticket is created 5 years, 6 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
- 12:00 – 17:00 12:00 – 17:00 12:00 – 17:00 12:00 – 17:00 12:00 – 17:00 -
- 18:00 – 21:00 18:00 – 21:00 18:00 – 21:00 18:00 – 21:00 18:00 – 21:00 -

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

This topic contains 10 replies, has 2 voices.

Last updated by Noman 5 years, 6 months ago.

Assisted by: Noman.

Author
Posts
#1118404

Hi,

I get on specific pages a 502 bad request, on some pages, where views are inserted. My hoster says disabling views plugin solves this issue and so it is.

Can you please solve this problem as soon as possible?

Thanks and regards,

#1118478

Noman
Supporter

Languages: English (English )

Timezone: Asia/Karachi (GMT+05:00)

Hi,

Thank you for contacting Toolset support. I tried to login to your site but it says “401 Authorization Required” (security username and password needed).

Please enable WordPress debugging in your site and look for any errors on the page or error log file and let us know the errors if you see (any screenshot incase of errors will help us as well): https://toolset.com/documentation/programmer-reference/debugging-sites-built-with-toolset/

Thank you

#1118870

Hi,

please use:

User: demo
Passwort: serv34782276-dev01

Regards.

#1118898

Noman
Supporter

Languages: English (English )

Timezone: Asia/Karachi (GMT+05:00)

Hi,

I have logged in to your site and visited number of pages but I can not see any issue in them. Could you please provide me page/view link where I can see that issue.

Thank you

#1118908

Hi,

sorry, the plugin was disabled. A link would be: hidden link

Regards,

#1118951

Noman
Supporter

Languages: English (English )

Timezone: Asia/Karachi (GMT+05:00)

Hi,

Thanks for the link, Now I can see the 502 issue. To further debug this issue I need to request you please provide temporary access (WP-Admin and FTP Login info) to your site (preferably staging site), so that I can look into your setup and check the issue.

Your next answer will be private which means only you and I have access to it.

=== Please backup your database and website ===

✙ I would additionally need your permission to de-activate and re-activate Plugins and the Theme, and to change configurations on the site. This is also a reason the backup is really important.

Thank you

#1118958
#1119963

Noman
Supporter

Languages: English (English )

Timezone: Asia/Karachi (GMT+05:00)

Hello,

I have thoroughly debugged this issue, when I remove resize='proportional' attribute from the Specialist Image field, all seems to be working fine and the design still looks the same on the frontend, please check and confirm: hidden link

Thank you

#1119971

Hi,

thanks, yes it works again. Is this a toolset bug? When will you release a bug fix?

Regards,

#1120179

Noman
Supporter

Languages: English (English )

Timezone: Asia/Karachi (GMT+05:00)

Basically its not a bug, it looks some sort of conflict either on server side or with the data in the database for the terms, which happens only in this particular site. Because I tried to reproduce this same issue in my test site and the resize='proportional' attribute works fine for me.

#1120437

When this error occurs after a toolset update, it seems to be a bug.

Also there is no solution available. This filter was set because we need it - the only workaround deleting it is no solution.

#1120792

Noman
Supporter

Languages: English (English )

Timezone: Asia/Karachi (GMT+05:00)

Are you seeing any difference in the image size when we remove it? On frontend I always see same image with size 300px

This ticket is now closed. If you're a WPML client and need related help, please open a new support ticket.