Netvisor - Daemon fails to build

[bourkey]

✅ Have you read and understood the above guidelines?

Yes

🔎 Did you run the script with verbose mode enabled?

Yes, verbose mode was enabled and the output is included below

📜 What is the name of the script you are using?

netvisor

📂 What was the exact command used to execute the script?

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/netvisor.sh)"

⚙️ What settings are you using?

• Default Settings
• Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 13

📈 Which Proxmox version are you on?

pveversion pve-manager/9.1.1/42db4a6cf33dac83 (running kernel: 6.14.11-4-pve)

📝 Provide a clear and concise description of the issue.

Netvisor daemon fails to install properly. No configuation file available at /root/.config/daemon/config.json

🔄 Steps to reproduce the issue.

Install Script, discovery daemon reports as successful.

❌ Paste the full error output (if available).

The integrated daemon config is located at /root/.config/daemon/config.json

No errors. Backend works fine. No Daemon installed in the backend, or not configured.

Manual Daemon installation works fine

🖼️ Additional context (optional).

`  ✔️   Created frontend UI
  ✔️   Built Netvisor-server
  ✔️   Built Netvisor-daemon
  ✔️   Netvisor server & daemon configured and running
  ✔️   Customized Container
  ✔️   Cleaned
file /etc/pve/storage.cfg line 48 (skip section 'truenas'): unsupported type 'truenasplugin'
  ✔️   Completed Successfully!

  🚀  NetVisor setup has been successfully initialized!
  💡   Access it using the following URL:
    🌐  http://192.168.xxx.xxx:60072

Adv Install with verbose output:

Tailed as no errors above

    Compiling netvisor-server v0.11.0 (/opt/netvisor/backend)
    Finished `release` profile [optimized] target(s) in 5m 00s
  ✔️   Built Netvisor-server
  ⏳   Building Netvisor-daemon   Compiling netvisor-server v0.11.0 (/opt/netvisor/backend)
    Finished `release` profile [optimized] target(s) in 46.26s
  ✔️   Built Netvisor-daemon
  ✔️   Netvisor server & daemon configured and running
Summary:                        
  Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 0
npm warn using --force Recommended protections disabled.
     Removed 5466 files, 1.5GiB total
Journal file /var/log/journal/a3a149279fa04217b43c9c5e57405ea5/system.journal is truncated, ignoring file.
Vacuuming done, freed 0B of archived journals from /var/log/journal/a3a149279fa04217b43c9c5e57405ea5.
Vacuuming done, freed 0B of archived journals from /run/log/journal.
Vacuuming done, freed 0B of archived journals from /var/log/journal.
  ✔️   Cleaned
file /etc/pve/storage.cfg line 48 (skip section 'truenas'): unsupported type 'truenasplugin'
  ✔️   Completed Successfully!

  🚀  NetVisor setup has been successfully initialized!
  💡   Access it using the following URL:
    🌐  http://192.168.xxx.xxx:60072


root@netvisor:~# pwd
/root
root@netvisor:~# ls -ls
total 4
4 -rw-r--r-- 1 root root 84 Dec  5 12:30 netvisor.creds
root@netvisor:~# ls -la
total 40
drwx------  6 root root 4096 Dec  5 12:30 .
drwxr-xr-x 18 root root 4096 Dec  5 12:29 ..
-rw-r--r--  1 root root  657 Dec  5 12:36 .bashrc
drwxr-xr-x  4 root root 4096 Dec  5 12:31 .cargo
-rw-r--r--  1 root root    7 Dec  5 12:30 .netvisor
-rw-r--r--  1 root root   84 Dec  5 12:30 netvisor.creds
drwxr-xr-x  3 root root 4096 Dec  5 12:36 .npm
-rw-r--r--  1 root root  190 Dec  5 12:30 .profile
drwxr-xr-x  6 root root 4096 Dec  5 12:30 .rustup
drwx------  2 root root 4096 Oct  2 00:43 .ssh
root@netvisor:~# cd .config
-bash: cd: .config: No such file or directory
root@netvisor:~# 

[tremor021]

@vhsdream also while you're at it, you have a typo here, in the repo url:

ProxmoxVE/ct/netvisor.sh

Line 6 in 33ce3fd

# Source: https://github.com/maynayza/netvisor

[vhsdream]

OK I see what's happened. The new version breaks my method of automatically setting up the daemon via querying the DB for the network_id and api_key, which now do not exist until you go into the GUI and create your account.

I'll have to find another way to configure the daemon, or it will instead be left up to the user, since technically there is a way to use the GUI to do that.

[vhsdream]

@bourkey I've submitted a PR. Thank you for creating this issue! 👍🏼