Scanopy configure_daemon.sh does not work due to api-key mismatch

[durzo]

✅ 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?

scanopy

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

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

⚙️ What settings are you using?

• Default Settings
• Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 13

📈 Which Proxmox version are you on?

9.1.4

📝 Provide a clear and concise description of the issue.

The included script /root/configure_daemon.sh pulls the API key from the database table api_keys and passes it as the value of --daemon-api-key in the created systemd file for scanopy-daemon

The problem is, the API key stored in the api_keys table is a hash of the key, not the key itself. this results in the daemon registration failing due to an invalid api key, and it getting stuck in a retry/restart loop.

it does not look like the api key is obtainable from the db table, so the script itself may have to be removed or altered to prompt for manual api key insertion

🔄 Steps to reproduce the issue.

1. create the lxc using the install script
2. open the webui and create a new account, do nothing else.
3. inside the lxc, run /root/configure_daemon.sh
4. journalctl -fu scanopy-daemon shows the registration failure
5. cat /etc/systemd/system/scanopy-daemon shows the api key hash taken from the DB.
6. note its length (65 chars). api keys are 33 chars in length.
7. in the web ui, create a new API key, note the key and its length (33 chars)
8. select all rows from api_keys table, the api key is 65 chars and not the original key (its a hash)

❌ Paste the full error output (if available).

Dec 30 23:38:33 scanopy scanopy-daemon[18451]: 2025-12-30T23:38:33.177371Z  WARN scanopy::daemon::runtime::service: API key not yet active. This daemon was likely installed before account registration was completed. Waiting for account creation... Retrying in 16 seconds. daemon_id=6c5b6833-9163-405f-aaf4-ad20b796a6af attempt=6

🖼️ Additional context (optional).

No response

[tremor021]

Disregard anything i said.... lol
@vhsdream configure_daemon.sh fetches the hash from DB instead of actual API key. Can we refactor this?

[durzo]

the actual API key is not stored anywhere in the DB that I can see. I guess it needs to be created by the script either via direct DB insert or a call back to scanopy-server but im not sure thats even possible

[tremor021]

We can surely make configure_daemon.sh ask the user to insert the API key generated in the app, just wanna @vhsdream to give his thoughts, since its his script

I mean, thats what I just did. I hardcoded the network ID and API key in the configure_daemon.sh and ran it like that. It worked fine