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 14 Packages Projects Releases 10 Wiki Activity

Case Sensitivity Issue with CT Naming in Advanced Settings #132

New Issue
Closed
opened 2026-02-04 16:45:35 +03:00 by OVERLORD · 2 comments
OVERLORD commented 2026-02-04 16:45:35 +03:00
Owner
Copy Link

Originally created by @ali2key on GitHub (Dec 3, 2024).

Please verify that you have read and understood the guidelines.

yes

A clear and concise description of the issue.

When creating a container (CT) in Proxmox through script > Advanced Settings, the provided CT name is automatically converted to lowercase.

For example:

Input Name: CT-107-NGINX
Actual Result: ct-107-nginx

What settings are you currently utilizing?

  • Default Settings
  • Advanced Settings

Which Linux distribution are you employing?

Debian 12

If relevant, including screenshots or a code block can be helpful in clarifying the issue.

https://github.com/community-scripts/ProxmoxVE/issues/489
In my previous issue, "I was specifically referring to the CT name displayed in the Proxmox UI, not the hostname. It's worth noting that it is possible to manually create a CT name with uppercase letters directly in the UI.

Regarding point 2, I disagree with the reasoning. Proxmox refers to VMs/CTs using their IDs, not their names, so I don't believe case sensitivity would cause conflicts in this context."

Please provide detailed steps to reproduce the issue.

  1. Run script (e.g. bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/nginx.sh)")
  2. Select Advanced Settings.
  3. Enter a name in mixed case, e.g., CT-107-NGINX.
  4. Complete the setup process.
Originally created by @ali2key on GitHub (Dec 3, 2024). ### Please verify that you have read and understood the guidelines. yes ### A clear and concise description of the issue. When creating a container (CT) in Proxmox through script > Advanced Settings, the provided CT name is automatically converted to lowercase. For example: Input Name: CT-107-NGINX Actual Result: ct-107-nginx ### What settings are you currently utilizing? - [ ] Default Settings - [X] Advanced Settings ### Which Linux distribution are you employing? Debian 12 ### If relevant, including screenshots or a code block can be helpful in clarifying the issue. https://github.com/community-scripts/ProxmoxVE/issues/489 In my previous issue, "I was specifically referring to the CT name displayed in the Proxmox UI, not the hostname. It's worth noting that it is possible to manually create a CT name with uppercase letters directly in the UI. Regarding point 2, I disagree with the reasoning. Proxmox refers to VMs/CTs using their IDs, not their names, so I don't believe case sensitivity would cause conflicts in this context." ### Please provide detailed steps to reproduce the issue. 1. Run script (e.g. bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/nginx.sh)") 2. Select Advanced Settings. 3. Enter a name in mixed case, e.g., CT-107-NGINX. 4. Complete the setup process.
OVERLORD commented 2026-02-04 16:45:45 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Dec 3, 2024):

How many times are you going to open this?

It is rejected. Then rebuild it yourself in the core. I don't take any risks to build possible vulnerabilities into a case sensitive system. You are welcome to get the opinion of others, but I for one will not install anything like that.

@judeibe @newzealandpaul @havardthom @remz1337

@MickLesk commented on GitHub (Dec 3, 2024): How many times are you going to open this? It is rejected. Then rebuild it yourself in the core. I don't take any risks to build possible vulnerabilities into a case sensitive system. You are welcome to get the opinion of others, but I for one will not install anything like that. @judeibe @newzealandpaul @havardthom @remz1337
OVERLORD commented 2026-02-04 16:45:49 +03:00
Author
Owner
Copy Link

@havardthom commented on GitHub (Dec 3, 2024):

Using lowercase letters for hostnames is a recommended best practice, as it helps maintain consistency and minimizes the likelihood of confusion. The scripts in use adhere to this practice.
If you want to deviate from this best practice you can use pct set <VMID> --hostname <newname>

@havardthom commented on GitHub (Dec 3, 2024): Using lowercase letters for hostnames is a recommended best practice, as it helps maintain consistency and minimizes the likelihood of confusion. The scripts in use adhere to this practice. If you want to deviate from this best practice you can use `pct set <VMID> --hostname <newname>`
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
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#132
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?