Outline keeps reconnecting

[dripfeeder]

Outline v 1.11.0 ArchLinux (6.4.12) When trying to connect to a valid Outline server, it connects but can't keep it up for more then 2 seconds. It stays in an infinite loop reconnecting every 2 seconds.

[vbua]

Same problem.

[r7vme]

Same issue.

[r7vme]

Some logs from OUTLINE_DEBUG=true outline-client

connecting to 3f6769e2-ae8c-4bca-804c-d17c4d8b0f59...
using tun2socks to check connectivity
[EXIT - tun2socks]: Exited with code 0
UDP support: true
starting routing daemon
[STDERR - tun2socks]: 2023/09/16 09:53:23 tun2socks running...

tun2socks started
2023/09/16 09:53:23 tun2socks running...
connected to 3f6769e2-ae8c-4bca-804c-d17c4d8b0f59
reconnecting to 3f6769e2-ae8c-4bca-804c-d17c4d8b0f59
reconnected to 3f6769e2-ae8c-4bca-804c-d17c4d8b0f59
using tun2socks to check connectivity
[EXIT - tun2socks]: Exited with code 0
reconnecting to 3f6769e2-ae8c-4bca-804c-d17c4d8b0f59
reconnected to 3f6769e2-ae8c-4bca-804c-d17c4d8b0f59
using tun2socks to check connectivity
[EXIT - tun2socks]: Exited with code 0
reconnecting to 3f6769e2-ae8c-4bca-804c-d17c4d8b0f59
reconnected to 3f6769e2-ae8c-4bca-804c-d17c4d8b0f59
using tun2socks to check connectivity

[seethesky]

Same issue. Arch Linux 6.5.3 Outline Appimage built from git clone

[egmaleta]

I have the same issue Arch linux 6.5.3-arch1-1 Outline 1.11.0

[seethesky]

Any news or feedback from the customer support, please?

[maddyhof]

Thanks for reaching out! We don't currently support ArchLinux but we do have an open issue requesting support: #1685. I'll close this as a duplicate.

[seethesky]

There is no fix for this. For those still struggling with it - just switch to Nekoray and create Shadowsocks connection using your Outline server links.

[r7vme]

thanks, @seethesky , Nekoray worked for me. After installation just copy outline key (ss://...) into clipboard and Ctrl+V into Nekoray. Enable "Tun Mode" and "Start" created profile.

[vpkopylov]

I have two devices with Arch Linux, both with the most recent updates, but one of them has this problem, and another doesn't. The one with the problem has just installed system, and the working one runs Arch for a few years. So maybe there is some difference in network configuration introduced in more recent packages that outline client can't handle. Also I noticed this message in the journal that precedes an attempt to reconnect (192.168.1.1 is my router address.):

[INFO] [routing polluted] extra non-Outline default gateway: default via 192.168.1.1 dev wlp0s20f3 proto dhcp src 192.168.1.101 metric 600

Looks like the wifi connection (NetworkManager) and outline client are in a race trying to set the default gateway.

[aycanozcan]

I'm having the same problem in Ubuntu 23.10. I tried wired and wireless, the result did not change. It disconnects and reconnects every 2 seconds.

[aycanozcan]

I'm having the same problem in Ubuntu 23.10. I tried wired and wireless, the result did not change. It disconnects and reconnects every 2 seconds.

[Legion112]

@seethesky I wanna mention here that on Kubuntu I have experience the same issue Like mentioned before

connecting to 85c7e6da-0c25-4ed5-b746-ed54b2cdd0ae...
using tun2socks to check connectivity
[EXIT - tun2socks]: Exited with code 0
UDP support: true
starting routing daemon
tun2socks started
connected to 85c7e6da-0c25-4ed5-b746-ed54b2cdd0ae
reconnecting to 85c7e6da-0c25-4ed5-b746-ed54b2cdd0ae
reconnected to 85c7e6da-0c25-4ed5-b746-ed54b2cdd0ae
using tun2socks to check connectivity
[EXIT - tun2socks]: Exited with code 0
reconnecting to 85c7e6da-0c25-4ed5-b746-ed54b2cdd0ae
reconnected to 85c7e6da-0c25-4ed5-b746-ed54b2cdd0ae
using tun2socks to check connectivity
[EXIT - tun2socks]: Exited with code 0
reconnecting to 85c7e6da-0c25-4ed5-b746-ed54b2cdd0ae
reconnected to 85c7e6da-0c25-4ed5-b746-ed54b2cdd0ae
using tun2socks to check connectivity

Usage of nekoray helped to solve the issue.

@maddyhof hi thank you for your support. I think this issue also appears on ubuntu distro Do you support it. Should be this issue be re open?

[adequacy1]

It's been almost a year, the error persists.

[Yukigaru]

Same issue on Ubuntu 24.04, please reopen or link with https://github.com/Jigsaw-Code/outline-apps/issues/1959. Outline client: Version 1.13.1 (476278).

[lagunovartur]

Та же проблема на Ubuntu 24.04

[gggallahad]

Same issue, Ubuntu 23.10

[Sofitt]

Same issue, Ubuntu 24.04

[glow12121]

Same in Fedora 39.

[m-aghazadeh]

Same issue in Linux Mint 22

[K4dZuO]

Ubuntu 24.04 is the same problem plus after the running outline client I can't restore any connection. Only the machine reboot helps.

[glow12121]

It has been almost a year. Outline Client is unusable in Linux.

What makes things worse, at least in Fedora, the client automatically adds itself on the list of auto-start programs, so at times you need to reboot twice to get non-VPN connection back.

Please fix, this is a critical problem in Linux environment.

[starrabb1t]

Same issue, Ubuntu 24.04

[Nika1ex]

Same in Ubuntu 24.04

[konovaltsev]

Disabling IPv6 in network interface settings (and restarting NetworkManager) solve this problem for me in Ubuntu 24.04.

[vpkopylov]

@konovaltsev your workaround also works on Fedora 40, thanks!

[easmith]

@konovaltsev hey! If you mean this, it does not work for me on kubuntu 24.04

sudo sysctl -w net.ipv6.conf.all.disable_ipv6=1
sudo sysctl -w net.ipv6.conf.default.disable_ipv6=1
sudo sysctl -w net.ipv6.conf.lo.disable_ipv6=1
sudo systemctl restart NetworkManager

and out put for ./Outline-Client.AppImage --no-sandbox is

Outline is starting
loading web app from file:///tmp/.mount_OutlinOQXwjj/resources/app.asar/client/www/index_electron.html?appName=Outline
Could not load active tunnel:  null
Checking for update
Update for version 1.13.1 is not available (latest version: 1.13.1, downgrade is disallowed).
connecting to 48299d49-67a5-4655-071a-49d66ce1102f...
using tun2socks to check connectivity
[EXIT - tun2socks]: Exited with code 0
UDP support: true
starting routing daemon
tun2socks started
connected to 48299d49-67a5-4655-071a-49d66ce1102f
reconnecting to 48299d49-67a5-4655-071a-49d66ce1102f
reconnected to 48299d49-67a5-4655-071a-49d66ce1102f
using tun2socks to check connectivity
[EXIT - tun2socks]: Exited with code 0
reconnecting to 48299d49-67a5-4655-071a-49d66ce1102f
reconnected to 48299d49-67a5-4655-071a-49d66ce1102f
using tun2socks to check connectivity
[EXIT - tun2socks]: Exited with code 0
reconnecting to 48299d49-67a5-4655-071a-49d66ce1102f
reconnected to 48299d49-67a5-4655-071a-49d66ce1102f
using tun2socks to check connectivity
...

[konovaltsev]

@easmith

sudo sysctl -w net.ipv6.conf.all.disable_ipv6=1 sudo sysctl -w net.ipv6.conf.default.disable_ipv6=1 sudo sysctl -w net.ipv6.conf.lo.disable_ipv6=1

This doesn't work for me, too. But from GUI (Gnome): Settings -> Network (or Wi-Fi) -> Network Options (on network connection or wifi network) -> IPv6 -> IPv6 Method -> select "Disable" radiobutton and press "Apply". Then type in console "sudo service NetworkManager restart". This works for me. I don't know how to do it from the console only.

[NaumovEvgeniy]

Disabling IPv6 in network interface settings (and restarting NetworkManager) solve this problem for me in Ubuntu 24.04.

It works for me! Thanks man!

[sbruens]

Thanks everyone for your patience. We're aware of this issue and are looking into it. We welcome any comments on workarounds that worked for you.