OutlineVPN CLI - received hangup, terminating...

[aspektr]

Tried run as:

1. sudo outline-cli -transport "ss://secret" >> outline.log
2. sudo outline-cli -transport "ss://secret" >> outline.log &
3. sudo setsid bash -c 'outline-cli -transport "ss://secret" >> outline.log '
4. sudo nohup ...

Always lost ssh connections and had log as:

OutlineVPN CLI (experimental)
[INFO] 2025/11/09 08:06:06 updated global IPv6 support: false
[INFO] 2025/11/09 08:06:06 remote server supports UDP, we will delegate all UDP packets to it
[INFO] 2025/11/09 08:06:06 routing traffic from 10.233.233.1 to 10.233.233.2/32 through nic 10
[INFO] 2025/11/09 08:06:06 routing traffic via gw 10.233.233.2 through nic 10...
[INFO] 2025/11/09 08:06:06 ip rule 'from all not to xxx.xxx.xxx.xxx/32 via table 233' created
[INFO] 2025/11/09 08:06:06 received hangup, terminating...
[INFO] 2025/11/09 08:06:06 routing table '233' has been cleaned up
[INFO] 2025/11/09 08:06:06 ip rule of routing table '233' deleted
[INFO] 2025/11/09 08:06:06 DNS config restored from '/etc/resolv.outlinecli.backup' to '/etc/resolv.conf'
[INFO] 2025/11/09 08:06:06 Outline DNS config '/etc/resolv.conf.head' has been removed
[INFO] 2025/11/09 08:06:06 OutlineDevice -> tun stopped: 40 <nil>
[INFO] 2025/11/09 08:06:06 updated global IPv6 support: true
[INFO] 2025/11/09 08:06:06 tun -> OutlineDevice stopped: 208 read tun: file already closed

found the next thing:

signal.Notify(sigc, os.Interrupt, unix.SIGTERM, unix.SIGHUP)
s := <-sigc
logging.Info.Printf("received %v, terminating...\n", s)
return nil

But I'm out of ideas why I'm getting sigterm

ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
    link/ether d0:0d:19:83:a7:e2 brd ff:ff:ff:ff:ff:ff
    altname enp138s0
    altname ens8
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
    link/ether d0:1d:19:83:a7:e2 brd ff:ff:ff:ff:ff:ff
    altname enp139s0
    altname ens9

route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         10.129.0.1      0.0.0.0         UG    100    0        0 eth0
0.0.0.0         10.129.0.1      0.0.0.0         UG    200    0        0 eth1
10.129.0.0      0.0.0.0         255.255.255.0   U     100    0        0 eth0
10.129.0.0      0.0.0.0         255.255.255.0   U     200    0        0 eth1
10.129.0.1      0.0.0.0         255.255.255.255 UH    100    0        0 eth0
10.129.0.1      0.0.0.0         255.255.255.255 UH    200    0        0 eth1
10.129.0.2      0.0.0.0         255.255.255.255 UH    100    0        0 eth0
10.129.0.2      0.0.0.0         255.255.255.255 UH    200    0        0 eth1

 ls -l /dev/net/tun || sudo modprobe tun
crw-rw-rw- 1 root root 10, 200 Nov  9 07:23 /dev/net/tun

 cat /etc/os-release
PRETTY_NAME="Ubuntu 24.04.3 LTS"
NAME="Ubuntu"
VERSION_ID="24.04"
VERSION="24.04.3 LTS (Noble Numbat)"
VERSION_CODENAME=noble
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=noble
LOGO=ubuntu-logo

 uname -r
6.8.0-87-generic

[jyyi1]

Hi @aspektr , it seems you are running outline-cli within an SSH session?

If so, you're observing is likely expected. Because outline-cli modifies the routing table which breaks the active SSH connection. When the SSH connection drops, outline-cli receives SIGHUP and terminates.

To keep outline-cli running reliably, maybe try something like tmux?