Having trouble getting Proxmox Widget working

[korishan]

Description

I am new to the Homepage world. I'm wanting a dedicated homepage away from Firefox/Chrome's default page that is bleh.
So I've been trying to add the various services and web sites that I use on the regular.

What I've stumbled upon is getting Proxmox, and a few other services, properly working with the API logins. I've followed the steps at Homepage - Proxmox several times, and each time Homepage will only show the error of

and here's the code in services.yml:

I'm not sure what I'm missing or misconfiguring.

homepage version

v0.8.7 (05a7c0f, Jan 26, 2024)

Installation method

Docker

Configuration

No response

Container Logs

No response

Browser Logs

No response

Troubleshooting

From the logs:

[2024-02-14T02:17:47.583Z] error: <credentialedProxyHandler> HTTP Error 401 calling https://192.168.2.20:8006/api2/json/cluster/resources
[2024-02-14T02:17:47.584Z] error: <credentialedProxyHandler> HTTP Error 401 calling https://192.168.2.20:8006/api2/json/cluster/resources
[2024-02-14T02:17:47.585Z] error: <credentialedProxyHandler> HTTP Error 401 calling https://192.168.2.21:8006/api2/json/cluster/resources
[2024-02-14T02:17:50.317Z] error: undefined
[2024-02-14T02:17:55.373Z] error: <credentialedProxyHandler> HTTP Error 401 calling https://192.168.2.20:8006/api2/json/cluster/resources
[2024-02-14T02:17:55.374Z] error: <credentialedProxyHandler> HTTP Error 401 calling https://192.168.2.20:8006/api2/json/cluster/resources
[2024-02-14T02:17:56.447Z] error: undefined

[glime-ai[bot]]

Based on the error logs you've provided, it appears that the HTTP Error 401 is occurring when Homepage is trying to call the Proxmox API. An HTTP 401 error typically indicates that authentication has failed. This could be due to incorrect credentials or an issue with the API token setup.

Here are some steps you can take to troubleshoot this issue:

1. Verify API Token and Credentials: Ensure that the API token and credentials you are using in your services.yml are correct. Double-check the username and password fields. The username should be in the format user@realm!tokenid and the password should be the secret associated with the API token.

2. Check Proxmox Permissions: Make sure that the user associated with the API token has the correct permissions in Proxmox to access the resources you are trying to display.

3. Use CURL to Test API Access: You can test the API access using curl with the correct authentication headers to ensure that the API token is working outside of Homepage. If this works, but Homepage does not, it could indicate a configuration issue within Homepage.

4. Review Homepage Configuration: Review the services.yml configuration for any typos or formatting issues. Ensure that the URL does not end with a trailing slash as per the documentation.

5. Check Container Networking: If you are running Homepage in Docker, ensure that the container can reach the Proxmox server. You can use docker exec to run a ping command from within the container to the Proxmox server's IP address.

6. Review Homepage Logs: Check the homepage.log file for any additional information that might help diagnose the issue.

7. Consult the Documentation and Troubleshooting Guides: Review the official documentation and troubleshooting guides for additional tips and common issues.

If you continue to experience issues after following these steps, you may want to seek further assistance from the Homepage community, either by opening a GitHub issue or by asking for help in the #ai-support channel on Discord.

Remember to replace any sensitive information such as API tokens and passwords when sharing your configuration for troubleshooting.

---

Thanks for posting a discussion about homepage here on GitHub. Homepage now uses a fancy new AI tool thanks to our friends at Glime, so the answer below is the AI bot's attempt to answer your question. If you feel it's sufficient you can mark the answer and close this post, otherwise feel free to leave it open of course!

Thanks for using Homepage! ❤️

This comment was generated by Glime.

[korishan]

I have already done what the bot suggested and I'm still lost on the details. The homepage.log isn't providing must more details than what I already posted.
I already know that authentication is failing, I want to know "why" it is and "how" to fix it, even though I've followed the directions in the Proxmox Widget page.

[Whiskey103]

I think you have wrong credential settings... no need for that API part i think. Unless ofcourse THAT IS the name u used to generate the token for hehe.
here is my config:

    icon: proxmox
    href: https://xxxxxxxxxxxxxxxxxxxxx.nl
    description: Virtual Machine HOST
    ping: https://xxxxxxxxxxxxxxxxxxxxx.nl
    widget:
        type: proxmox
        url: https://xxxxxxxxxxxxxxxxxxx.nl
        username: root@pam!homepage
        password: 7b4axxxxxxxxxxxxxxxxxxxxxxxxxxxxxxa42a
        node: # optional to specify a node instead of a cluster

[eBarazi]

Hi,
I would command the "node" if you are not using it, and comparing to mine (Your Proxmox had no port, shoud be :8006), here're my proxmox service and widget all wotking:

 - Proxmox:
        icon: /icons/Proxmox.svg
        href: https://192.168.1.123:8006
        description:
        siteMonitor: 192.168.1.123
        widget:
            type: proxmox
            url: https://192.168.1.123:8006
            username: "{{HOMEPAGE_VAR_PROXMOX_USER}}"
            password: "{{HOMEPAGE_VAR_PROXMOX_API_KEY}}"

[nbris95]

Just adding in here as I've been sealing with the issue of not being able to connect..
I had this:
HOMEPAGE_VAR_PROXMOX_URL=https://192.xxx.x.xxx:8006/

The issue was the / at the end of 8006. Once I removed that, all worked.

[github-actions[bot]]

This discussion has been automatically closed due to inactivity. See our contributing guidelines for more details.

[cwilson1776]

When you use PAM realm accounts, I think you need to actually create a user by that name (shell: useradd ). You might need to do it first, as I had no luck creating the corresponding user after going through the Homepage - Proxmox procedure.

On the other hand, using the "Proxmox VE authentication server" realm, the documented procedure worked with no problems, given that small modification.

[github-actions[bot]]

This discussion has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns. See our contributing guidelines for more details.