starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-02-05 00:29:55 +03:00
Code Issues 11 Packages Projects Releases 10 Wiki Activity

replay from config file, password cannot be empty #1260

New Issue
Closed
opened 2026-02-04 23:58:53 +03:00 by OVERLORD · 2 comments
OVERLORD commented 2026-02-04 23:58:53 +03:00
Owner
Copy Link

Originally created by @MBlaschek on GitHub (Jul 11, 2025).

Originally assigned to: @michelroegl-brunner on GitHub.

✅ Have you read and understood the above guidelines?

yes

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

caddy.sh

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

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

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

📝 Provide a clear and concise description of the issue.

Using advanced setting deploying the container works, but the second time, when using the written config it fails, with:
✖️ Password cannot be empty

which is a result of the config-file.func that is not aware that all passwords are written as: PW=-password [PWD] and here is a space, hence the error.

I guess fixing the config-file.func or the part in build.func where the config file is written should be it.

🔄 Steps to reproduce the issue.

create a container and replay with the written config file.

❌ Paste the full error output (if available).

   ______          __    __     
  / ____/___ _____/ /___/ /_  __
 / /   / __ `/ __  / __  / / / /
/ /___/ /_/ / /_/ / /_/ / /_/ / 
\____/\__,_/\__,_/\__,_/\__, /  
                       /____/   
  💡    Using Config File on node devx1
  💡  Using config File: /opt/community-scripts/caddy.conf
  🆔  Container ID: 102
  📦  Container Type: Unprivileged
   ✖️   Password cannot be empty

🖼️ Additional context (optional).

Thanks for the great scripts!!!

Originally created by @MBlaschek on GitHub (Jul 11, 2025). Originally assigned to: @michelroegl-brunner on GitHub. ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? caddy.sh ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/caddy.sh)" ### ⚙️ What settings are you using? - [ ] Default Settings - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📝 Provide a clear and concise description of the issue. Using advanced setting deploying the container works, but the second time, when using the written config it fails, with: ✖️ Password cannot be empty which is a result of the `config-file.func` that is not aware that all passwords are written as: `PW=-password [PWD]` and here is a space, hence the error. I guess fixing the `config-file.func` or the part in build.func where the config file is written should be it. ### 🔄 Steps to reproduce the issue. create a container and replay with the written config file. ### ❌ Paste the full error output (if available). ``` ______ __ __ / ____/___ _____/ /___/ /_ __ / / / __ `/ __ / __ / / / / / /___/ /_/ / /_/ / /_/ / /_/ / \____/\__,_/\__,_/\__,_/\__, / /____/ 💡 Using Config File on node devx1 💡 Using config File: /opt/community-scripts/caddy.conf 🆔 Container ID: 102 📦 Container Type: Unprivileged ✖️ Password cannot be empty ``` ### 🖼️ Additional context (optional). Thanks for the great scripts!!!
OVERLORD added the bug label 2026-02-04 23:58:53 +03:00
OVERLORD commented 2026-02-04 23:58:58 +03:00
Author
Owner
Copy Link

@reichbc commented on GitHub (Jul 12, 2025):

for what it's worth, I get the same issue with ntfy.sh

@reichbc commented on GitHub (Jul 12, 2025): for what it's worth, I get the same issue with ntfy.sh
OVERLORD commented 2026-02-04 23:59:01 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jul 15, 2025):

https://github.com/community-scripts/ProxmoxVE/discussions/1637#discussioncomment-13761117 & #5978

@MickLesk commented on GitHub (Jul 15, 2025): https://github.com/community-scripts/ProxmoxVE/discussions/1637#discussioncomment-13761117 & #5978
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
🛑 Failure to comply with the guidelines
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#1260
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?