starred/ProxmoxVE-Local

Fork 0

mirror of https://github.com/community-scripts/ProxmoxVE-Local.git synced 2026-04-26 13:15:49 +03:00

[GH-ISSUE #312] Issue with SSHPASS and or rsync #97

New issue

Closed

opened 2026-02-26 12:40:10 +03:00 by kerem · 4 comments

kerem commented

2026-02-26 12:40:10 +03:00

Owner

Originally created by @Kolyangus on GitHub (Nov 12, 2025).
Original GitHub issue: https://github.com/community-scripts/ProxmoxVE-Local/issues/312

✅ Have you read and understood the above guidelines?

yes

📝 Provide a clear and concise description of the issue.

When attempting to install a script after downloading, error log is presented per the below with the installation not being completed and the process has to be stopped.

Update of existing LXC's works smoothly and testing is showing that connection to server has been successful, including a manual SSH attempt on the LXC itself.

🔄 Steps to reproduce the issue.

Install ProxmoxVE-Local script using defaults
Login first time
Create server and connect to it - Test to verify connection is successful
Find example script to install (e.g. OpenWebUI, Debian, Alpine) and download
Once downloaded select install and select server previously created
Error occurs

❌ Paste the full error output (if available).

[13:44:52] [START] Starting SSH execution of scripts/ct/openwebui.sh on
[13:44:52] [ERROR] SSHPASS: Failed to run command: No such file or directory

[13:44:52] [ERROR] rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(232) [sender=3.4.1]

[13:44:52] [ERROR] SSH execution failed: rsync failed with code 12
[13:44:52] [ERROR] Failed to start SSH execution: rsync failed with code 12

🖼️ Additional context (optional).

I have also connected to both the Proxmox host and the machine to verify things such as SSHPASS and rsync are installed given it appears to be erroring on these areas.

Unsure if the LXC needs to be privileged or not however given the default is unprivileged it has been setup in this configuration. Have also verified that the firewall is not blocking the traffic as far as I can see.

Originally created by @Kolyangus on GitHub (Nov 12, 2025). Original GitHub issue: https://github.com/community-scripts/ProxmoxVE-Local/issues/312 ### ✅ Have you read and understood the above guidelines? yes ### 📝 Provide a clear and concise description of the issue. When attempting to install a script after downloading, error log is presented per the below with the installation not being completed and the process has to be stopped. Update of existing LXC's works smoothly and testing is showing that connection to server has been successful, including a manual SSH attempt on the LXC itself. ### 🔄 Steps to reproduce the issue. 1. Install ProxmoxVE-Local script using defaults 2. Login first time 3. Create server and connect to it - Test to verify connection is successful 4. Find example script to install (e.g. OpenWebUI, Debian, Alpine) and download 5. Once downloaded select install and select server previously created 6. Error occurs ### ❌ Paste the full error output (if available). [13:44:52] [START] Starting SSH execution of scripts/ct/openwebui.sh on **<Server>** [13:44:52] [ERROR] SSHPASS: Failed to run command: No such file or directory [13:44:52] [ERROR] rsync: connection unexpectedly closed (0 bytes received so far) [sender] rsync error: error in rsync protocol data stream (code 12) at io.c(232) [sender=3.4.1] [13:44:52] [ERROR] SSH execution failed: rsync failed with code 12 [13:44:52] [ERROR] Failed to start SSH execution: rsync failed with code 12 ### 🖼️ Additional context (optional). I have also connected to both the Proxmox host and the machine to verify things such as SSHPASS and rsync are installed given it appears to be erroring on these areas. Unsure if the LXC needs to be privileged or not however given the default is unprivileged it has been setup in this configuration. Have also verified that the firewall is not blocking the traffic as far as I can see.

kerem

2026-02-26 12:40:10 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-26 12:40:10 +03:00

Author

Owner

@michelroegl-brunner commented on GitHub (Nov 13, 2025):

Sadly i can not reproduce this issue. Can you try and recreate the LXC and try again?

@michelroegl-brunner commented on GitHub (Nov 13, 2025): Sadly i can not reproduce this issue. Can you try and recreate the LXC and try again?

kerem commented

2026-02-26 12:40:10 +03:00

Author

Owner

@Kolyangus commented on GitHub (Nov 13, 2025):

No worries, I'll let you know the outcome.

@Kolyangus commented on GitHub (Nov 13, 2025): No worries, I'll let you know the outcome.

kerem commented

2026-02-26 12:40:10 +03:00

Author

Owner

@Kolyangus commented on GitHub (Nov 14, 2025):

An interesting update, I have now switched over to using SSH Key compared with password that I was using originally, understanding this is not best practise. Now without going into too much detail the following symbols are used within the password { and -.

As soon as I switched over to SSH Key it worked flawlessly so I'm not sure whether there is something that is causing a conflict with the password that is being entered which is not escaped and causing the code to interpret the symbols as command?

Clutching at strings here but so far this is what I have.

@Kolyangus commented on GitHub (Nov 14, 2025): An interesting update, I have now switched over to using SSH Key compared with password that I was using originally, understanding this is not best practise. Now without going into too much detail the following symbols are used within the password { and -. As soon as I switched over to SSH Key it worked flawlessly so I'm not sure whether there is something that is causing a conflict with the password that is being entered which is not escaped and causing the code to interpret the symbols as command? Clutching at strings here but so far this is what I have.

kerem commented

2026-02-26 12:40:10 +03:00

Author

Owner

@michelroegl-brunner commented on GitHub (Nov 14, 2025):

An interesting update, I have now switched over to using SSH Key compared with password that I was using originally, understanding this is not best practise. Now without going into too much detail the following symbols are used within the password { and -.

As soon as I switched over to SSH Key it worked flawlessly so I'm not sure whether there is something that is causing a conflict with the password that is being entered which is not escaped and causing the code to interpret the symbols as command?

Clutching at strings here but so far this is what I have.

Tbf. SSH-KEY should be used over password when possible. But i thank you for sharing the Chars you have in your PW, i suspect the { to be the issue here. I look at the password validation code again.

@michelroegl-brunner commented on GitHub (Nov 14, 2025): > An interesting update, I have now switched over to using SSH Key compared with password that I was using originally, understanding this is not best practise. Now without going into too much detail the following symbols are used within the password { and -. > > As soon as I switched over to SSH Key it worked flawlessly so I'm not sure whether there is something that is causing a conflict with the password that is being entered which is not escaped and causing the code to interpret the symbols as command? > > Clutching at strings here but so far this is what I have. Tbf. SSH-KEY should be used over password when possible. But i thank you for sharing the Chars you have in your PW, i suspect the `{` to be the issue here. I look at the password validation code again.

kerem referenced this issue

2026-02-26 12:40:36 +03:00

[PR #97] [MERGED] feat: Add SSH key authentication and custom port support #208