-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
[Bug]: Outline Client can't establish stable connection on Ubuntu 24.04 #2001
Comments
Previously I had Ubuntu 22.04, Outline Client was working perfectly there. |
Try ufw disable reboot server and check again. |
I have no firewall on my server, my Outline app on the phone works just fine. A windows laptop, that I could get my hands on connects just fine too. Server: $ sudo ufw status
Status: inactive Outline CLI works stable on my Ubuntu machine still. |
I am issuing this problem too. I'm using version 1.13.1. Also, I have to start client with command |
Also I noticed the following behavior:
I used
Also, on fresh Ubuntu 24.04 Outline-Client reports error
when I start it without It seems like For now I use |
I have the same issue. How can i solve it ? |
Hi @heilkit @iloginov @AdriCQ , the sandbox issue seems to be caused by a known electron bug: electron/electron#41066. You may try these arguments when launching Outline: And yes, please also feel free to continue using |
the same problem :( |
Application
Outline Client
Describe the bug
Can't establish stable connection to Outline server after upgrading to Ubuntu 24.04 with my own surely working OK Outline Server, instead client constantly tries to reconnect.
Everything was fine until the upgrade to Ubuntu 24.04, using Outline CLI gets you connected, but the client won't.
I'm including debug log below.
Steps to reproduce
What did you expect to happen?
No response
What actually happened?
DEBUG LOG (some keys where changed for privacy reasons)
Outline Version
1.13.0 (475480)
What operation system are you using?
Linux
Operating System Version
Ubuntu 24.04 LTS x86_64
Screenshots and Videos
No response
The text was updated successfully, but these errors were encountered: