Skip to content Skip to sidebar Skip to footer
Home / Firefox / Gateway / Geckodriver / Python / Selenium

504 Gateway Time-out Error Using Firefox 68.9.0esr In Headless Mode With Geckodriver Selenium And Python

Post a Comment
I made a container image with selenium. I used a ubi image from RedHat as base image. I installed the following versions of the geckodriver and Mozilla Firefox geckodriver 0.26.0

Solution 1:

This error message...

selenium.common.exceptions.WebDriverException: Message: <html><body><h1>504 Gateway Time-out</h1>
The server didn't respond in time.

...implies that the Firefox v68.9.0esr was unable to establish a connection with the application server and the following WebDriverException error was raised.

504 Gateway Timeout errors are inconclusive as they indicate what happened to your website, but they doesn't convey what exactly went wrong, making it difficult to analyze the root cause and solve the issue. However, there can be many reasons behind the error 504 Gateway Time-out and a couple of approaches to solve the issue are as follows:

  • Look for server connectivity issues: Check if the server is down for maintenance or any other reason, your website could serve visitors a 504 Gateway Timeout Error page. The only way to troubleshoot this issue is to wait for your server to finish maintenance or fix the problem causing the error.
  • Check for any DNS changes: If the application have recently changed host servers or moved the website to a different IP address website’s DNS server is changed, it could cause your website to serve its visitors a 504 Gateway Timeout Error page. Then the website won't be up and running until the DNS changes take full effect, which can take a couple of hours.
  • Browse through the logs: Logs will provide details about the server’s behavior and status. Analyze them to uncover any useful information.
  • Fix faulty firewall configurations: Firewall is a website's gatekeeper, protecting your site from malicious visitors or distributed denial-of-service (DDoS) attacks. A faulty firewall configuration will cause your firewall to deem requests from a content delivery network as an attack on your server and reject them, resulting in a 504 Gateway Timeout error. Check your firewall configuration to pinpoint and fix the issue.

This usecase

However as of this usecase, this error message...

1593770085639   geckodriver::marionette DEBUG   Waiting 60sto connect to browser on127.0.0.1:34835
Failed to open connection to"session" message bus: Address does not contain a colon
Running without a11y support!

...indicates that there was an issue with the Firefox v68.9.0esr build.

Solution

As per the comment within the discussion (firefox:28877): GConf-WARNING **: Client failed to connect to the D-BUS daemon: Address does not contain a colon the solution is to revert back to the previous version of Firefox ESR build.

Post a Comment for "504 Gateway Time-out Error Using Firefox 68.9.0esr In Headless Mode With Geckodriver Selenium And Python"