mirror of
https://github.com/community-scripts/ProxmoxVE-Local.git
synced 2026-03-31 06:23:54 -04:00
Changing SSH port on server add causes failure #71
Reference in New Issue
Block a user
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?
Originally created by @gdeeble on GitHub (Oct 18, 2025).
✅ Have you read and understood the above guidelines?
Yes
📝 Provide a clear and concise description of the issue.
When you are adding a server, if you happen to switch to the port field because you are tabbing, you might end up trying to type your password. When doing this, it causes the field to switch to text and causes the add to fail.
🔄 Steps to reproduce the issue.
❌ Paste the full error output (if available).
Oct 18 13:05:07 pve-scripts-local npm[2878]: Invalid
prisma.server.create()invocation:Oct 18 13:05:07 pve-scripts-local npm[2878]: {
Oct 18 13:05:07 pve-scripts-local npm[2878]: data: {
Oct 18 13:05:07 pve-scripts-local npm[2878]: name: "Server",
Oct 18 13:05:07 pve-scripts-local npm[2878]: ip: "x.x.x.x",
Oct 18 13:05:07 pve-scripts-local npm[2878]: user: "redacted",
Oct 18 13:05:07 pve-scripts-local npm[2878]: password: "redacted",
Oct 18 13:05:07 pve-scripts-local npm[2878]: auth_type: "password",
Oct 18 13:05:07 pve-scripts-local npm[2878]: ssh_key: "",
Oct 18 13:05:07 pve-scripts-local npm[2878]: ssh_key_passphrase: "",
Oct 18 13:05:07 pve-scripts-local npm[2878]: ssh_port: "22",
Oct 18 13:05:07 pve-scripts-local npm[2878]: ~~~~
Oct 18 13:05:07 pve-scripts-local npm[2878]: ssh_key_path: null,
Oct 18 13:05:07 pve-scripts-local npm[2878]: key_generated: false,
Oct 18 13:05:07 pve-scripts-local npm[2878]: color: "#3b82f6"
Oct 18 13:05:07 pve-scripts-local npm[2878]: }
Oct 18 13:05:07 pve-scripts-local npm[2878]: }
🖼️ Additional context (optional).
This might be a UI issue but it might be worth adding a try except to try to cast the port on the backend as well because when I did it, I put in 22 as expected and it still failed after.
@michelroegl-brunner commented on GitHub (Oct 18, 2025):
Thank you, i will address that begining of next week!