- Platform information:
- Hardware:Pi4b 1GB RAM, USB SSD for influxdb data.
- OS: openhabian 1.6.3 zram enabled
- Java Runtime Environment: default
- openHAB version: 3 stable, static IP
TL;DR Has anyone successfully setup wireguard via openhabian?
- Issue of the topic: After setting up a new openHAB3 installation on a new Pi4b and new 16GB card I thought I would try the wireguard VPN. I ran through the process which seemed to run fine and added the config to the client using the QR code. I tried to connect but it failed. I then realised openHAB and SSH/putty were not responding. The green activity light was still flashing and the network activity light was still flashing but I couldn’t access file shares, openHAB or SSH. I don’t currently have a monitor connection so tried a power cycle.
This didn’t go well as the Pi failed to boot. I used the SD card that I’d setup for mirror backup and booted into that. Copied back the system to the original 16GB card and booted. Tried the setup again and afterwards, took the following code details.
2021-03-21_10:32:41_GMT [openHABian] Checking for root privileges... OK 2021-03-21_10:32:42_GMT [openHABian] Loading configuration file '/etc/openhabian.conf'... OK 2021-03-21_10:32:42_GMT [openHABian] openHABian configuration tool version: [openHAB3]patchday-20210316-1251(9334918) 2021-03-21_10:32:42_GMT [openHABian] Checking for changes in origin branch openHAB3... OK 2021-03-21_10:32:47_GMT [openHABian] Switching to branch openHAB3... OK 2021-03-21_10:32:57_GMT [openHABian] Updating Linux package information... OK 2021-03-21_10:32:57_GMT [openHABian] Installing Wireguard and enabling VPN remote access... net.ipv4.ip_forward = 1 net.ipv6.conf.all.forwarding = 1 Created symlink /firstname.lastname@example.org → /lib/systemd/system/wg-quick@.service. Job for email@example.com failed because the control process exited with error code. See "systemctl status firstname.lastname@example.org" and "journalctl -xe" for details. 2021-03-21_10:36:32_GMT [openHABian] Generating QR to load config on the client side (download Wireguard app from PlayStore or AppStore)...
So I ran
systemctl status email@example.com
enhabian@openhabian:~ $ systemctl status firstname.lastname@example.org ● email@example.com - WireGuard via wg-quick(8) for wg0 Loaded: loaded (/lib/systemd/system/wg-quick@.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sun 2021-03-21 10:34:53 GMT; 9min ago Docs: man:wg-quick(8) man:wg(8) https://www.wireguard.com/ https://www.wireguard.com/quickstart/ https://git.zx2c4.com/wireguard-tools/about/src/man/wg-quick.8 https://git.zx2c4.com/wireguard-tools/about/src/man/wg.8 Process: 27047 ExecStart=/usr/bin/wg-quick up wg0 (code=exited, status=1/FAILURE) Main PID: 27047 (code=exited, status=1/FAILURE) Mar 21 10:34:53 openhabian systemd: Starting WireGuard via wg-quick(8) for wg0... Mar 21 10:34:53 openhabian wg-quick: wg-quick: `/etc/wireguard/wg0.conf' does not exist Mar 21 10:34:53 openhabian systemd: firstname.lastname@example.org: Main process exited, code=exited, status=1/FAILURE Mar 21 10:34:53 openhabian systemd: email@example.com: Failed with result 'exit-code'. Mar 21 10:34:53 openhabian systemd: Failed to start WireGuard via wg-quick(8) for wg0.
I then tried
systemctl start firstname.lastname@example.org incase that might help and openHAB was not reachable again.
I left it running for 15mins and again all activity lights seemed to indicate the system was fine but openHAB was unreachable. A network scan didn’t show any other devices on the network indicating that the IP address had changed and
openhabian:8080 didn’t connect either. Due to me pulling the power to try a restart, I’d possibly caused issues with the original and backup cards, so I coudn’t get either to boot. I ended up starting with a fresh install of openhabian 1.6.4 on a new 16GB card and reloading my backed up .item/.thing etc text files. I’m holding off trying wireguard again through fear of more issues.