SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-07-24 23:04:55 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

Checkmk LXC - Default password unknown, and landing page not in root #221

New Issue
Closed
opened 2025-11-20 04:45:08 -05:00 by saavagebueno · 10 comments
saavagebueno commented 2025-11-20 04:45:08 -05:00
Owner
Copy Link

Originally created by @Possemaster on GitHub (Dec 20, 2024).

✅ Have you read and understood the above guidelines?

yes

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

Checkmk LXC

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

bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/checkmk.sh)"

📝 Provide a clear and concise description of the issue.

Default username and password are not chown.
Website default username and password do not work so something must go wrong in the script as it also does not echo the credentials.

This part of the script does not function;

PASSWORD=$(omd create monitoring | grep "password:" | awk '{print $NF}')
$STD omd start
{
    echo "Application-Credentials"
    echo "Username: cmkadmin"
    echo "Password: $PASSWORD"
} >> ~/checkmk.creds

2nd issue is that the tool is installed with the landing page in the folder /monitoring and the root is empty. Please recreate this so the root is the landing page. This is unusable for reverse proxy without rewrites and stuff while there is no use to have the landing page under /monitoring for a standalone instance.

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

🔄 Steps to reproduce the issue.

Install script

❌ Paste the full error output (if available).

No visible error.
Only username and password are unknown

🖼️ Additional context (optional).

No response

Originally created by @Possemaster on GitHub (Dec 20, 2024). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Checkmk LXC ### 📂 What was the exact command used to execute the script? bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/checkmk.sh)" ### 📝 Provide a clear and concise description of the issue. Default username and password are not chown. Website default username and password do not work so something must go wrong in the script as it also does not echo the credentials. This part of the script does not function; ``` PASSWORD=$(omd create monitoring | grep "password:" | awk '{print $NF}') $STD omd start { echo "Application-Credentials" echo "Username: cmkadmin" echo "Password: $PASSWORD" } >> ~/checkmk.creds ``` 2nd issue is that the tool is installed with the landing page in the folder /monitoring and the root is empty. Please recreate this so the root is the landing page. This is unusable for reverse proxy without rewrites and stuff while there is no use to have the landing page under /monitoring for a standalone instance. ### ⚙️ What settings are you using? - [X] Default Settings - [X] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 🔄 Steps to reproduce the issue. Install script ### ❌ Paste the full error output (if available). No visible error. Only username and password are unknown ### 🖼️ Additional context (optional). _No response_
saavagebueno commented 2025-11-20 04:45:10 -05:00
Author
Owner
Copy Link

@michelroegl-brunner commented on GitHub (Dec 20, 2024):

Part 1 we have to check.

Part two: This is how checkmk works. we can not easily change the webroot, as checkmk is intendet ro support more then one Monitoringsite. The root for the webpage needs to be /site-name to work properly.

@michelroegl-brunner commented on GitHub (Dec 20, 2024): Part 1 we have to check. Part two: This is how checkmk works. we can not easily change the webroot, as checkmk is intendet ro support more then one Monitoringsite. The root for the webpage needs to be /site-name to work properly.
saavagebueno commented 2025-11-20 04:45:10 -05:00
Author
Owner
Copy Link

@Possemaster commented on GitHub (Dec 20, 2024):

I think this is the culprit the $ is misplaced

PASSWORD=$(omd create monitoring | grep "password:" | awk '{print $NF}')
$STD omd start
{
    echo "Application-Credentials"
    echo "Username: cmkadmin"
    echo "Password: $PASSWORD"
} >> ~/checkmk.creds

Should be

$PASSWORD=(omd create monitoring | grep "password:" | awk '{print $NF}')
$STD omd start
{
    echo "Application-Credentials"
    echo "Username: cmkadmin"
    echo "Password: $PASSWORD"
} >> ~/checkmk.creds
@Possemaster commented on GitHub (Dec 20, 2024): I think this is the culprit the $ is misplaced ``` PASSWORD=$(omd create monitoring | grep "password:" | awk '{print $NF}') $STD omd start { echo "Application-Credentials" echo "Username: cmkadmin" echo "Password: $PASSWORD" } >> ~/checkmk.creds ``` Should be ``` $PASSWORD=(omd create monitoring | grep "password:" | awk '{print $NF}') $STD omd start { echo "Application-Credentials" echo "Username: cmkadmin" echo "Password: $PASSWORD" } >> ~/checkmk.creds ```
saavagebueno commented 2025-11-20 04:45:10 -05:00
Author
Owner
Copy Link

@michelroegl-brunner commented on GitHub (Dec 20, 2024):

In bash you have no leading $ when declaring a variable, this is not the issue.

@michelroegl-brunner commented on GitHub (Dec 20, 2024): In bash you have no leading $ when declaring a variable, this is not the issue.
saavagebueno commented 2025-11-20 04:45:10 -05:00
Author
Owner
Copy Link

@Possemaster commented on GitHub (Dec 20, 2024):

In bash you have no leading $ when declaring a variable, this is not the issue.

OK, then I will leave it to the Pros 😄

@Possemaster commented on GitHub (Dec 20, 2024): > In bash you have no leading $ when declaring a variable, this is not the issue. OK, then I will leave it to the Pros 😄
saavagebueno commented 2025-11-20 04:45:10 -05:00
Author
Owner
Copy Link

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

idk what you do, for me the script is working absolutely correctly.

image

image

image

@MickLesk commented on GitHub (Dec 20, 2024): idk what you do, for me the script is working absolutely correctly. ![image](https://github.com/user-attachments/assets/1828b2dd-a6be-4fc7-a969-c41512b617cb) ![image](https://github.com/user-attachments/assets/81e0d124-2b3e-45ac-a3e5-5501fdb71902) ![image](https://github.com/user-attachments/assets/ae8eaea7-beab-4908-9143-605d0efc6c79)
saavagebueno commented 2025-11-20 04:45:10 -05:00
Author
Owner
Copy Link

@Possemaster commented on GitHub (Dec 20, 2024):

I do not see anywhere I need to get my credentials from a file.
Maybe I am blind but I do not see any instruction at the script and during running of the script that I need to get my credentials from the checkmk.creds file. I am not a scripting Guru or Unix hero. That is why I rely on these scripts. 😄
image

@Possemaster commented on GitHub (Dec 20, 2024): I do not see anywhere I need to get my credentials from a file. Maybe I am blind but I do not see any instruction at the script and during running of the script that I need to get my credentials from the checkmk.creds file. I am not a scripting Guru or Unix hero. That is why I rely on these scripts. 😄 ![image](https://github.com/user-attachments/assets/13488740-c295-43be-a5fa-feec336128c3)
saavagebueno commented 2025-11-20 04:45:11 -05:00
Author
Owner
Copy Link

@Possemaster commented on GitHub (Dec 20, 2024):

So consider it a User issue then and not a "bug".
But imo you should at least communicate it somewhere for the NON Scriptkiddies

@Possemaster commented on GitHub (Dec 20, 2024): So consider it a User issue then and not a "bug". But imo you should at least communicate it somewhere for the NON Scriptkiddies
saavagebueno commented 2025-11-20 04:45:11 -05:00
Author
Owner
Copy Link

@michelroegl-brunner commented on GitHub (Dec 20, 2024):

Thats on me, i missed it when i created the json file. @MickLesk fixed it and is now visible on the website
image

@michelroegl-brunner commented on GitHub (Dec 20, 2024): Thats on me, i missed it when i created the json file. @MickLesk fixed it and is now visible on the website ![image](https://github.com/user-attachments/assets/a406f41c-dff6-4dc4-b42f-d247da97ffd6)
saavagebueno commented 2025-11-20 04:45:11 -05:00
Author
Owner
Copy Link

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

I do not see anywhere I need to get my credentials from a file.
Maybe I am blind but I do not see any instruction at the script and during running of the script that I need to get my credentials from the checkmk.creds file. I am not a scripting Guru or Unix hero. That is why I rely on these scripts. 😄
image

Clear your Cache

@MickLesk commented on GitHub (Dec 20, 2024): > I do not see anywhere I need to get my credentials from a file. > Maybe I am blind but I do not see any instruction at the script and during running of the script that I need to get my credentials from the checkmk.creds file. I am not a scripting Guru or Unix hero. That is why I rely on these scripts. 😄 > ![image](https://github.com/user-attachments/assets/13488740-c295-43be-a5fa-feec336128c3) > Clear your Cache
saavagebueno commented 2025-11-20 04:45:11 -05:00
Author
Owner
Copy Link

@Possemaster commented on GitHub (Dec 20, 2024):

Thanks so much for the support.
Works great.

@Possemaster commented on GitHub (Dec 20, 2024): Thanks so much for the support. Works great.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
🛑 Failure to comply with the guidelines
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
Implemented in VED waiting push to Main
in project pipeline
invalid
investigation
json
maintenance
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
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/ProxmoxVE#221
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?