Site is being served via the Traefik load balancer, version 1.6.0-rc5.

Works fine on Chrome in Windows, Firefox on Mac, but Chrome on the same Mac hitting the same site will not load the page.

Unfortunately it's an internal development site that won't be accessible to outside testers, but we were hoping something would jump out of the log.

david.sanftenberg@ Thanks for the issue.

As the setup Traefik load balancer is not available at TE end to test this issue, requesting someone from Internals>Network team to look into this issue and help in further triaging.

Thanks..

Alrighty, no worries.

I'll attach our Traefik config.toml file here so your team can replicate the same config. We are using the Rancher backend at the moment although I would imagine you could set it up in Docker and it would be fine.

The cert we're serving is the same one served at the production site, https://compass.cardano.com

I would pay attention to the cipher suites we are serving, as if I had to guess this is where the problem would lie. 

Deleted: traefik.toml 3.8 KB

traefik.toml 3.8 KB Download

The production site, by the way, uses Traefik 1.5.4. It also does not serve HSTS and CSP headers, while our dev site does (this is a change due to be pushed out).

We cannot reproduce the issue on the production site. 

From the log, the SSL handshake itself seems to be completing just fine. Rather the timeouts look like they're in waiting for the server response. We send an HTTP request and then the server doesn't respond for another 10 seconds.

Additionally, your server appears to be sending us on a redirect loop, from / to /dashboard and from /dashboard back to /. We would eventually give up after 20 redirects with ERR_TOO_MANY_REDIRECTS, but since every other redirect leg is taking 10 seconds, it takes a while to get there.

Specifically, the /dashboard requests (which redirect to /) take 10 seconds, while the / requests (which redirect to /dashboard) are pretty quick.

Is it possible you've misconfigured your server somehow? Perhaps there are some server-side logs that might shed some light on what it's doing?

Any chance you're able to answer the questions in comment #6? Thanks!

Closing this for now, if you're still experiencing the issues with the server and can get server-side logs, feel free to reopen a new bug.