504 Gateway Time-out (nginx)

  • Resolved cultoftheshadow

    (@cultoftheshadow)


    9 months ago

    I have created 3 sites using the free version. There are several pages and each page displays 20-40 feeds of 5-6 items in every feed. Semi dedicated Plex server.

    Apparently, all these feeds are eating so much resources that the whole server goes down giving a “504 Gateway Time-out (nginx)” error. I am not an expert but I found that when I go to domain > Hosting & DNS > Apache & nginx > Clear cashe then everyting comes back and works like charm. Then it depends, it might all go down after 2 minutes or after two days. I login to server, delete the nginx cashe and comes back…. over and over again… this has been going on for some time now…

    Is it due to 1-2 feeds being problematic? Or is it some general configurations? Need to find a solution asap.

Viewing 1 replies (of 1 total)
  • Plugin Support AndreeaR

    (@andreearadacina21)

    Hey @cultoftheshadow,

    Thank you for using Feedzy and for reaching out!

    The 504 Gateway Timeout Error indicates that the server didn’t receive a timely response from an upstream server it needed to access in order to complete a request.

    This is not something related to how Feedzy works, but more an isolated issue. There are some basic steps that you can follow to find the root cause:

    1. Verify network: Make sure there are no network issues affecting the connection between your server and upstream servers. Try accessing other websites to confirm your internet connection is stable.
    2. Review server configuration: Check that your server settings are configured correctly, including timeouts and connection limits. Adjust these settings if necessary to handle traffic or resource demands.
    3. Optimize website performance: Enhance your website’s performance by optimizing code, reducing image sizes, and minimizing resource-heavy plugins or scripts.
    4. Reconsider the Hosting Plan: Consider upgrading your hosting plan if your website consistently experiences high traffic or resource usage.
    5. Check error logs: Review server and application error logs to identify any specific errors or issues causing the timeouts.
    6. Contact hosting provider: If the issue persists or if you’re unsure how to proceed, reach out to your hosting provider for assistance.
Viewing 1 replies (of 1 total)
  • The topic ‘504 Gateway Time-out (nginx)’ is closed to new replies.