Invalid backend response. HTTP error 502

  • Resolved SJNBham

    (@sjnbham)


    4 years, 10 months ago

    When using WPFM to access our site files it works well until we try to open the wp-content/uploads folder. It spins a long time and then returns:

    Invalid backend response. Error occurred on the server side. HTTP error 502.

    We have about 35,000 files at the root of our uploads directory. Maybe the number of files is causing an issue?

    Found this discussion online: https://wordpress.org/support/topic/how-to-handle-a-lot-of-media-files-in-the-uploads-folder-10-000/

    We used an FTP client and could list all of the contents of the uploads directory without errors. We host with WPEngine.com and asked their support if any config points on their end might be to problem. They weren’t aware of any and also didn’t know of any WP Core restrictions on how many files can be kept in a single directory.

    Having all of our media files in the main uploads folder will help with our current site migration efforts, allow us to use shorter URLs for docs, and simplify future migrations if needed.

    Any ideas on a possible root cause or fix?

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author mndpsingh287

    (@mndpsingh287)

    4 years, 10 months ago

    Hey @sjnbham,

    Thanks for contacting our support. Yes, If you have lots of files and file manager can take time to load these files, in this case, increase max_execution_time from the php.ini file, it may solve your issue.

    Maybe your request to load all files can be getting timed out before it loads all files. Increasing execution time from the php.ini file can solve this issue.

    Regards,
    Mandeep

    Thread Starter SJNBham

    (@sjnbham)

    4 years, 10 months ago

    WPEngine isn’t willing to adjust the max_execution_time setting for their hosted environment. Maybe a paging option for directories with a large number of files could be added as an enhancement request for this plugin. Thanks for the quick response to this support ticket 😉

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Invalid backend response. HTTP error 502’ is closed to new replies.