starred/ProxmoxVE

Fork 0

mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-04-25 09:15:59 +03:00

[GH-ISSUE #5930] replay from config file, password cannot be empty #1260

New issue

Closed

opened 2026-02-26 12:48:17 +03:00 by kerem · 2 comments

kerem commented

2026-02-26 12:48:17 +03:00

Owner

Originally created by @MBlaschek on GitHub (Jul 11, 2025).
Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/5930

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). Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/5930 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!!!

kerem

2026-02-26 12:48:17 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-26 12:48:17 +03:00

Author

Owner

@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

kerem commented

2026-02-26 12:48:17 +03:00

Author

Owner

@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

kerem referenced this issue

2026-02-26 13:32:21 +03:00

[PR #1261] [MERGED] Add RAM and Disk units #3083

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/ProxmoxVE#1260

No description provided.

Rows
Columns