Overleaf: "Unable to connect" message - but it connects

Created on 10 Jan 2020  路  4Comments  路  Source: overleaf/overleaf

Steps to Reproduce


  1. Installed Overleaf using docker
  2. Open any project or create a new one

Expected Behaviour


Everything should load without showing any "Unable to connect" message.

Observed Behaviour



The "Unable to connect" message is shown but after a few seconds (typically ~10) everything loads just fine.

Context


It is not a huge issue but requires me to point this out to every user/collaborator to ignore that message at startup and just be patient. It also renders the message useless when there really is a problem connecting.

Note: If I first SSH onto the server and then do the same steps from within the server network the message does not appear and everything loads just fine (using the same browsers).

Technical Info

  • Browser Name and version: Firefox 72, Chromium 79
  • Operating System and version (desktop or mobile): I'm running Arch Linux (desktop), the server runs Ubuntu 18.04. Overleaf is the latest docker image pulled yesterday.

Analysis


I can't find anything out of the ordinary in any of the log files, but would be happy to provide any if helpful.

Most helpful comment

Sorry for the delay, yes, adding these two lines to the reverse proxy config does indeed solve the issue! Thanks @Zeawiel!

All 4 comments

Hello,
I had also this issue, it was related to websocket.
If you open the network dev tool of your navigator you'll see that there is some request that gets 404.

Do you enable websocket in your (reverse) proxy ? You need to add this to the config:

        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";

See : https://github.com/overleaf/overleaf/wiki/HTTPS-reverse-proxy-using-Nginx

Hi, thanks for bringing this to our attention. Given @Zeawiel 's comment, I suspect this has something to do with the local network, especially as a direct connection works fine.

Can you try adding the configuration @Zeawiel posted? If this fixes the problem we can add this to th e general documentation.

Sorry for the delay, yes, adding these two lines to the reverse proxy config does indeed solve the issue! Thanks @Zeawiel!

Excellent!

Was this page helpful?
0 / 5 - 0 ratings

Related issues

jamiees2 picture jamiees2  路  9Comments

ASalvail picture ASalvail  路  3Comments

ghuser221 picture ghuser221  路  4Comments

adrianvb picture adrianvb  路  5Comments

mithodin picture mithodin  路  4Comments