Zwave JS UI Install error on line 23

[nickleman]

I'm trying to install the Zwave JS UI image however, I keep getting an error on line 23 message and the setup stops, there is no zwavjs service on the container at this point. Do I have to have my zwave stick already plugged in to the proxmox box in order for this to install correctly?

[tteck]

No issue here

 _____                                  _______    __  ______
/__  /_      ______ __   _____         / / ___/   / / / /  _/
  / /| | /| / / __ `/ | / / _ \   __  / /\__ \   / / / // /  
 / /_| |/ |/ / /_/ /| |/ /  __/  / /_/ /___/ /  / /_/ // /   
/____/__/|__/\__,_/ |___/\___/   \____//____/   \____/___/   
                                                             
Using Advanced Settings
Using Distribution: debian
Using debian Version: 12
Using Container Type: 0
Using Root Password: Automatic Login
Container ID: 111
Using Hostname: zwave-js-ui
Using Disk Size: 4
Allocated Cores: 2
Allocated RAM: 1024
Using Bridge: vmbr0
Using IP Address: dhcp
Using Gateway IP Address: Default
Using APT-Cacher IP Address: Default
Disable IPv6: yes
Using Interface MTU Size: Default
Using DNS Search Domain: Host
Using DNS Server IP Address: Host
Using MAC Address: AE:1A:60:07:B7:59
Using Vlan: Default
Enable Root SSH Access: no
Enable Verbose Mode: no
Creating a Zwave-JS-UI LXC using the above advanced settings
 ✓ Using local for Template Storage.
 ✓ Using thin-pool for Container Storage.
 ✓ Updated LXC Template List
 ✓ LXC Container 111 was successfully created.
 ✓ Started LXC Container
 ✓ Set up Container OS
 ✓ Network Connected: 192.168.86.250 
 ✓ IPv4 Internet Connected
 ✗ IPv6 Internet Not Connected
 ✓ DNS Resolved github.com to 140.82.113.4
 ✓ Updated Container OS
 ✓ Installed Dependencies
 ✓ Installed Z-Wave JS UI
 ✓ Created Service
 ✓ Customized Container
 ✓ Cleaned
Zwave-JS-UI should be reachable by going to the following URL.
         http://192.168.86.250:8091 

[tteck]

When encountering the error message [ERROR] in line 23: exit code *: while executing command "$@" > /dev/null 2>&1, make sure to run the script in verbose mode to accurately determine the underlying issue.

[nickleman]

Well, I just ran it again after you posted this and this time it ran and completed. I wonder if there was some source system that was down or updating or something, I ran it twice with the same result prior to posting. Thanks.