• Resolved azzurridesigns

    (@azzurridesigns)


    Hi everyone

    The company that owns a website is having issues internally on their Citrix environment. The website is accessible to the public only in the UK – but in their office network with the IP 209.235.144.9 they CANNOT access it. They get a 504 error.

    The IP is for a hosting company with its servers based in the USA, so I created a whitelist entry for that IP and also allowed all visitors from the US through.

    And YET – this IP appears on the list of ‘most blocked hosts’.

    What can we do?

    Thanks

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Pascal

    (@iqpascal)

    504 error is not something the plugin returns.

    If 209.235.144.9 is on your whitelist for the frontend it should be okay. If not could you send me an export of your settings to the mail address listed in the plugin?

    Thread Starter azzurridesigns

    (@azzurridesigns)

    Hi Pascal I have just emailed you the file.
    I understand what you’re saying, I find it so odd. The website was internally viewable just fine until last week, we haven’t done any new config or changes on the site and let somehow, it just gives a 504 to everyone in the office.

    Surely if it really was a global IP issue, the site would be down for everyone, not just internally.

    Thanks

    Plugin Author Pascal

    (@iqpascal)

    I find it odd that the whitelisted ip address is on the list of most blocked (unless you whitelisted it after a couple of blocks already then it would make sense).

    A 504 error is generally something a (reversed) proxy would give if the requested website has a very slow response time and the request eventually has a timeout. If the request would be blocked by the plugin this would be done in like for instance a second and would result in a different HTTP error code.

    Thread Starter azzurridesigns

    (@azzurridesigns)

    Hi Pascal

    After much effort the internal network company finally got their act together and did some testing of their own. It was an internal DNS issue, they deleted the A name record for the domain, re added it back in, and flushed DNS. Fixed.

    It’s amazing how frequently network managers blame web guys, as if we like to add www. redirects for the fun of it just to screw things up.

    Thanks for your help anyway, much appreciated!

    Plugin Author Pascal

    (@iqpascal)

    Super, glad it is resolved either way ??

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Is this plugin causing a 504 gateway timeout for an internal network?’ is closed to new replies.