527 Railgun Listener to Origin Error

For requests being optimized by Railgun, any interruption or failure in the WAN connection from Railgun's sender at Cloudflare's edge and the Railgun Listener at the customer's origin will result in the following error page being displayed in the browser: 

Overview

A 527 error indicates that the requests timeout or failed after the WAN connection has been established. This could result from an interruption or anomaly upstream from the Railgun Sender in the path to the Listener at the site's origin.

The 527 error could also occur due to an issue within the host environment when the Railgun Listener is unable to to complete or establish a connection to the origin server to receive a requested page: 

As there are a number of causes as to why the connection between the Listener and the webserver could have failed, it may be required to increase logging for Railgun in order to troubleshoot further.

Below are details on common scenarios where a 527 error would be presented to a user, and the associated Railgun error that would be found in the local Railgun logs. 


Common Railgun Log Errors

Connection Timeouts

If the Railgun Listener is unable to establish or complete a TCP handshake with the origin server, then the following errors would be produced within the Railgun logs for requests:

connection failed 0.0.0.0:443/example.com: dial tcp 0.0.0.0:443: i/o timeout
no response from origin (timeout) 0.0.0.0:80/example.com

LAN Timeout is Exceeded 

By default, the timeout limit for the origin server to send an HTTP response to the Listener is thirty seconds. This value is determined by the lan.timeout parameter found in the railgun.conf file. If the origin server does not respond within the specified timeout limit, then the following error would be seen in the Listener logs:

connection failed 0.0.0.0:443/example.com: dial tcp 0.0.0.0:443: i/o timeout

Connection Refusals

If requests from the Railgun Listener are being outright refused, then the following errors would be seen in the Railgun logs:

Error getting page: dial tcp 0.0.0.0:80:connection refused

TLS/SSL Related Errors

If TLS requests fail to complete or connect to the origin server from the Railgun Listener, then the following errors could be seen within the Railgun Logs:

connection failed 0.0.0.0:443/example.com: remote error: handshake failure 
connection failed 0.0.0.0:443/example.com: dial tcp 0.0.0.0:443:connection refused
connection failed 127.0.0.1:443/www.example.com: x509: certificate is valid for example.com, not www.example.com

Submitting a Support Ticket for 527 Errors

If a support ticket is to be filed in the event further assistance is needed, please submit the following pieces of information from the Railgun Listener so that Cloudflare Support can troubleshoot further in reviewing the the Railgun configuration.

  • The railgun.conf file.
  • If internal addressing is in use for the host environment, then the railgun-nat.conf file should be submitted in the ticket.
  • Any Railgun log files that detail the errors being seen from the Listener.
Still not finding what you need?

The CloudFlare team is here to help. 95% of questions can be answered using the search tool, but if you can’t find what you need, submit a support request.

Powered by Zendesk