Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Connecting..." message appear every 10 seconds when using Caddy as a proxy #6618

Closed
Gerporgl opened this issue Apr 6, 2017 · 3 comments
Closed

Comments

@Gerporgl
Copy link

Gerporgl commented Apr 6, 2017

Rocket.Chat Version: 0.54.2
Running Instances: 1
DB Replicaset OpLog: OpLog Disabled
Node Version: 4.7.3
Caddy Version: 0.9.5

When using the client interface (any of them: web, desktop, mobile) the "Connecting..." message bar at the top with show up briefly (flashes) at an intervals of about 10 seconds.
This only happen when Caddy is setup as the proxy.

I followed the Caddy instruction found in the documentation. Here is what my Caddyfile looks like:
http://rc.example.com, https://rc.example.com
proxy / 127.0.0.1:3000 {
websocket
transparent
}

If I use nginx as the proxy, or if I access rocket chat directly on port 3000, it works fine, I don't see the connecting message.
Also, even when this message show briefly, Rocket Chat and its core functionalities appear to be working fine. But it is still very annoying.

I haven't seen any mention of such issue, but I've done at least 2 installations on different servers (AWS and another local machine, one with Mint 17 and the other Ubuntu 16.04) and got the same issue.

@graywolf336
Copy link
Contributor

Please see: caddyserver/caddy#1562 (comment)

@Gerporgl
Copy link
Author

Gerporgl commented Apr 7, 2017

I see, disabling Caddy's timeouts solved my issue.

I was suspecting something related to timeouts, I was just being dumb here since there was documentation that seemed to tell how to configure Caddy, so I just followed that without really thinking. Thanks a lot for your time.

@graywolf336
Copy link
Contributor

No problem, I experienced it as well so I know the feeling. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants