You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Open https:// and accept the self-signed certificate, then register the first account. HTTPS is served by nginx (self-signed) because the frontend and passkey/WebAuthn login require a secure browser context.
Passkey/WebAuthn registration does not work against a bare IP address (WebAuthn requires a real domain). Use email/password login on the IP, or put Securo behind a real domain with valid TLS to enable passkeys.
Application secrets and the database URL live in /opt/securo_data/.env, kept outside the app directory so they survive updates. Optional integrations (Pluggy, Enable Banking, SimpleFIN, OIDC, AI agents) can be added there; restart with 'systemctl restart securo securo-worker securo-beat' after changes.
Note: This is not in the official repo yet—it's just a dev version! After merging into ProxmoxVE, it will need to be recreated.
I tried to enable AI Agents by adding the two documented variables to .env:
AGENTS_ENABLED=true
COMPOSE_PROFILES=agents
The service then fails to start:
uvicorn[14392]: pydantic_core._pydantic_core.ValidationError: 2 validation errors for Settings
uvicorn[14392]: agents_enabled
uvicorn[14392]: Extra inputs are not permitted [type=extra_forbidden, input_value='true', input_type=str]
uvicorn[14392]: For further information visit https://errors.pydantic.dev/2.13/v/extra_forbidden
uvicorn[14392]: compose_profiles
uvicorn[14392]: Extra inputs are not permitted [type=extra_forbidden, input_value='agents', input_type=str]
uvicorn[14392]: For further information visit https://errors.pydantic.dev/2.13/v/extra_forbidden
systemd[1]: securo.service: Main process exited, code=exited, status=1/FAILURE
systemd[1]: securo.service: Failed with result 'exit-code'.
Same results with only AGENTS_ENABLED=true.
Removing those two lines makes the service starts normally again.
Hey folks, thanks for bringing Securo to Proxmox, and @p-h-0-x, thanks for testing it and reporting this.
I'm Securo's maintainer. I can confirm the AI Agents issue is on our side rather than a packaging one.
I'll fix it and it ships in tomorrow's release. I'll follow up here once it's out.
Hey folks, as promised, the fix is merged and shipped in v0.14.2.
The AI Agents startup failure is gone: the extra keys in .env no longer abort the backend. @p-h-0-x, if you get a chance to re-run the script and confirm on your side, that would help a lot.
Activity
github-actions commentedon Jul 31, 2026
The Securo script is ready for testing:
Open https:// and accept the self-signed certificate, then register the first account. HTTPS is served by nginx (self-signed) because the frontend and passkey/WebAuthn login require a secure browser context.
Passkey/WebAuthn registration does not work against a bare IP address (WebAuthn requires a real domain). Use email/password login on the IP, or put Securo behind a real domain with valid TLS to enable passkeys.
Application secrets and the database URL live in /opt/securo_data/.env, kept outside the app directory so they survive updates. Optional integrations (Pluggy, Enable Banking, SimpleFIN, OIDC, AI agents) can be added there; restart with 'systemctl restart securo securo-worker securo-beat' after changes.
Note: This is not in the official repo yet—it's just a dev version! After merging into ProxmoxVE, it will need to be recreated.
Discord testing thread: https://discord.com/channels/1302816934508630047/1532715683782066276
p-h-0-x commentedon Aug 7, 2026
I tried to enable AI Agents by adding the two documented variables to
.env:The service then fails to start:
Same results with only
AGENTS_ENABLED=true.Removing those two lines makes the service starts normally again.
tassionoronha commentedon Aug 12, 2026
Hey folks, thanks for bringing Securo to Proxmox, and @p-h-0-x, thanks for testing it and reporting this.
I'm Securo's maintainer. I can confirm the AI Agents issue is on our side rather than a packaging one.
I'll fix it and it ships in tomorrow's release. I'll follow up here once it's out.
Let me know if I can help with anything else.
fix: agents config failures that were silent or unexplained (#577)
tassionoronha commentedon Aug 13, 2026
Hey folks, as promised, the fix is merged and shipped in v0.14.2.
The AI Agents startup failure is gone: the extra keys in
.envno longer abort the backend. @p-h-0-x, if you get a chance to re-run the script and confirm on your side, that would help a lot.Thanks again :)
MickLesk commentedon Aug 13, 2026
i test it tomorrow again ^^
p-h-0-x commentedon Aug 15, 2026
I can confirm that I no longer have the issue.
Thanks a lot :)
github-actions commentedon Aug 15, 2026
A PR has been created for securo: community-scripts/ProxmoxVE#16518
michelroegl-brunner commentedon Aug 15, 2026
Merged with #16518 in ProxmoxVE
github-actions commentedon Aug 15, 2026
Files deleted with PR #2187
Merge upstream: workspace modules, forecast split, mobile cards + 32 …