Husarnet install fails on Ubuntu 22.04

Raspberry Pi Ubuntu 22.04 installing the husarnet package fails with this error:

$ curl https://install.husarnet.com/install.sh | sudo bash
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  2771  100  2771    0     0   3646      0 --:--:-- --:--:-- --:--:--  3646
========================================
Installing Husarnet...
========================================
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
ca-certificates is already the newest version (20230311ubuntu0.22.04.1).
curl is already the newest version (7.81.0-1ubuntu1.15).
gnupg is already the newest version (2.2.27-3ubuntu2.1).
apt-transport-https is already the newest version (2.4.11).
The following packages were automatically installed and are no longer required:
  fonts-noto-color-emoji linux-headers-5.15.0-1038-raspi linux-image-5.15.0-1038-raspi linux-modules-5.15.0-1038-raspi linux-raspi-headers-5.15.0-1038
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)).
Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)).
OK
Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)).
OK
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)).
100  4345  100  4345    0     0   5758      0 --:--:-- --:--:-- --:--:--  5754
OK
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  4066  100  4066    0     0   5727      0 --:--:-- --:--:-- --:--:--  5726
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100    96  100    96    0     0    133      0 --:--:-- --:--:-- --:--:--   133
Hit:1 http://ports.ubuntu.com/ubuntu-ports jammy InRelease
Get:2 http://ports.ubuntu.com/ubuntu-ports jammy-updates InRelease [119 kB]
Hit:3 http://ports.ubuntu.com/ubuntu-ports jammy-backports InRelease
Get:4 http://ports.ubuntu.com/ubuntu-ports jammy-security InRelease [110 kB]
Get:5 https://download.docker.com/linux/ubuntu jammy InRelease [48.8 kB]
Hit:6 http://packages.osrfoundation.org/gazebo/ubuntu-stable jammy InRelease
Hit:8 http://packages.ros.org/ros2/ubuntu jammy InRelease
Get:10 http://ports.ubuntu.com/ubuntu-ports jammy-updates/main arm64 Packages [1098 kB]
Hit:11 https://install.husarnet.com/deb all InRelease
Hit:7 https://formant.jfrog.io/formant/debian jammy InRelease
Hit:9 https://packagecloud.io/greenfieldincorporated/robotapps/ubuntu jammy InRelease
Get:12 http://ports.ubuntu.com/ubuntu-ports jammy-updates/main Translation-en [258 kB]
Get:13 http://ports.ubuntu.com/ubuntu-ports jammy-updates/restricted arm64 Packages [834 kB]
Get:14 http://ports.ubuntu.com/ubuntu-ports jammy-updates/restricted Translation-en [202 kB]
Fetched 2670 kB in 3s (769 kB/s)
Reading package lists... Done
W: https://repo.formant.io/formant/debian/dists/jammy/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
N: Usage of apt_auth.conf(5) should be preferred over embedding login information directly in the sources.list(5) entry for 'https://packagecloud.io/greenfieldincorporated/robotapps/ubuntu'
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages were automatically installed and are no longer required:
  linux-headers-5.15.0-1038-raspi linux-image-5.15.0-1038-raspi linux-modules-5.15.0-1038-raspi linux-raspi-headers-5.15.0-1038
Use 'sudo apt autoremove' to remove them.
The following NEW packages will be installed:
  husarnet
0 upgraded, 1 newly installed, 0 to remove and 3 not upgraded.
Need to get 0 B/6721 kB of archives.
After this operation, 13.1 MB of additional disk space will be used.
Selecting previously unselected package husarnet.
(Reading database ... 219352 files and directories currently installed.)
Preparing to unpack .../husarnet_1%3a2.0.180_arm64.deb ...
Unpacking husarnet (1:2.0.180) ...
Setting up husarnet (1:2.0.180) ...
exit status 1
Scanning processes...
Scanning processor microcode...
Scanning linux images...

Running kernel seems to be up-to-date.

Failed to check for processor microcode upgrades.

No services need to be restarted.

No containers need to be restarted.

No user sessions are running outdated binaries.

No VM guests are running outdated hypervisor (qemu) binaries on this host.
Job for husarnet.service failed because a fatal signal was delivered causing the control process to dump core.
See "systemctl status husarnet.service" and "journalctl -xeu husarnet.service" for details.

We’ve had this failure on two different systems now – on the other one (1 week ago), it just started working with no explanation. We’ve also had this install succeed on numerous RPi Ubuntu 22.04 systems very similar to the one that is failing now.

I’ve tried removing/reinstalling multiple times and it fails every time. One other thing of interest is the /var/lib/husarnet directory is created but is empty.

Here is part of the journalctl output:

Dec 12 17:47:11 robot64 systemd[1]: husarnet.service: Scheduled restart job, restart counter is at 83.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ Automatic restarting of the unit husarnet.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Dec 12 17:47:11 robot64 systemd[1]: Stopped Husarnet.
░░ Subject: A stop job for unit husarnet.service has finished
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A stop job for unit husarnet.service has finished.
░░
░░ The job identifier is 89410 and the job result is done.
Dec 12 17:47:11 robot64 systemd[1]: Starting Husarnet...
░░ Subject: A start job for unit husarnet.service has begun execution
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit husarnet.service has begun execution.
░░
░░ The job identifier is 89410.
Dec 12 17:47:11 robot64 husarnet-daemon[5246]: libc++abi: terminating with uncaught exception of type nlohmann::detail::parse_error: [json.exception.parse_error.101] parse error at line 1, column 1: synt>
Dec 12 17:47:12 robot64 systemd[1]: husarnet.service: Main process exited, code=dumped, status=6/ABRT
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ An ExecStart= process belonging to unit husarnet.service has exited.
░░
░░ The process' exit code is 'dumped' and its exit status is 6.
Dec 12 17:47:12 robot64 systemd[1]: husarnet.service: Failed with result 'core-dump'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit husarnet.service has entered the 'failed' state with result 'core-dump'.
Dec 12 17:47:12 robot64 systemd[1]: Failed to start Husarnet.
░░ Subject: A start job for unit husarnet.service has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit husarnet.service has finished with a failure.
░░
░░ The job identifier is 89410 and the job result is failed.

Thanks for any help

Good Morning @ahelten :wave:

Can you send us results from following command to e-mail address support@husarnet.com?

sudo journalctl --unit husarnet --since yesterday

In your e-mail please mention this forum thread.

Regards, Filip

The log has been emailed. Thank you!

hello i am facing the same issue, have you solved this please?

Check these files (and folder):

  • /var/lib/husarnet/license.json
  • /var/lib/husarnet/config.json
  • /var/lib/husarnet/notifications.json

For me that entire folder did not exist. At some point it was created but that was after I stopped messing with it. I actually had switched to Tailscale and, when working with Tailscale, I noticed the Husarnet interface was up… and those above files (and folder) now existed. I tried multiple uninstall/installs and nothing fixed the missing files/folder… and I’m still not sure what fixed it. But I haven’t used Husarnet since.

Hi @khalil-heracles. Have you tried sudo systemctl restart husarnet?

If yes, and still don’t work, please send here a log from journalctl:

journalctl --unit husarnet --since=yesterday > log.txt

Thanks