#199 - [GH-ISSUE #942] Checkmk LXC - Default password unknown, and landing page not in root - starred/ProxmoxVE

kerem commented

2026-02-26 12:44:42 +03:00

Owner

Originally created by @Possemaster on GitHub (Dec 20, 2024).
Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/942

✅ 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). Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/942 ### ✅ 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_

kerem closed this issue

2026-02-26 12:44:42 +03:00

kerem commented

2026-02-26 12:44:43 +03:00

Author

Owner

@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.

kerem commented

2026-02-26 12:44:43 +03:00

Author

Owner

@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 ```

kerem commented

2026-02-26 12:44:43 +03:00

Author

Owner

@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.

kerem commented

2026-02-26 12:44:43 +03:00

Author

Owner

@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 😄

kerem commented

2026-02-26 12:44:43 +03:00

Author

Owner

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

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

@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)

kerem commented

2026-02-26 12:44:43 +03:00

Author

Owner

@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. 😄

@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)

kerem commented

2026-02-26 12:44:43 +03:00

Author

Owner

@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

kerem commented

2026-02-26 12:44:43 +03:00

Author

Owner

@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

@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)

kerem commented

2026-02-26 12:44:43 +03:00

Author

Owner

@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. 😄

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

kerem commented

2026-02-26 12:44:43 +03:00

Author

Owner

@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.

kerem referenced this issue

2026-02-26 13:30:49 +03:00

[PR #199] [MERGED] Remove duplicate acknowledgements from README #2625

Rows
Columns

[GH-ISSUE #942] Checkmk LXC - Default password unknown, and landing page not in root #199

✅ Have you read and understood the above guidelines?

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

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

📝 Provide a clear and concise description of the issue.

⚙️ What settings are you using?

🖥️ Which Linux distribution are you using?

🔄 Steps to reproduce the issue.

❌ Paste the full error output (if available).

🖼️ Additional context (optional).