502 Bad Gateway error

Created on 26 March 2020, over 4 years ago
Updated 28 November 2023, 10 months ago

I am having a 502 Bad Gateway error when syncing content in the client.

For your information, I am using Cloudflare CDN and when syncing content I am having the following error (see screenshot attached).

I have also noticed that if I opened my browser console and synchronise an entity, it synchronises successfully, however this does not always work.

I have checked the Drupal logs and the server logs but there is nothing stored.

Any help with this issue?

💬 Support request
Status

Fixed

Version

2.0

Component

Code

Created by

🇲🇺Mauritius Diveshh Mauritius

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • 🇮🇳India Sivaji_Ganesh_Jojodae Chennai

    I have similar issues. Getting 504 timeout in the interim of the batch process after 3 minutes of starting. Not sure if it is the timeout on the client (guzzle, php-fpm, nginx, or database) or the server's.

    Someone from our team indicated checking HTTP 499 which is the client's initiation to discard the request from processing further and the server could respect the same.

    The issue seems to be with the entity reference field,

    If you have access to your server and PHP configuration, you can extend the max_execution_time in the php.ini.

    If there is the usage of PHP-FPM to serve PHP scripts, you have also to adjust the request_terminate_timeout in your FPM config to the same value.

    If PHP-FPM has a reverse proxy like Nginx in the front to the user, the fastcgi_read_timeout also needs to be set to the same value, and to all other proxies in the front, you may adjust the proxy_read_timeout value.

    Anyway I'm going to try https://www.drupal.org/docs/contributed-modules/entity-share/troubleshoo...

Production build 0.71.5 2024