OpenShift Router Fails with "Cannot bind socket"

Solution In Progress - Updated -

Issue

  • The router container fails to start with this log error:
I1004 19:14:47.177582       1 router.go:238] Router is including routes in all namespaces
W1004 19:14:47.240199       1 router.go:846] a edge terminated route with host app-test.apps.wintermute.com does not have the required certificates.  The route will still be created but no certificates will be written
E1004 19:14:47.281739       1 ratelimiter.go:52] error reloading router: exit status 1
[ALERT] 276/191447 (48) : Starting proxy stats: cannot bind socket [0.0.0.0:1936]
[ALERT] 276/191447 (48) : Starting frontend public: cannot bind socket [0.0.0.0:80]
[ALERT] 276/191447 (48) : Starting frontend public_ssl: cannot bind socket [0.0.0.0:443]

Environment

  • Red Hat OpenShift Container Platform
    • 3.5, 3.6

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content