Portainer

[paolos7709]

Description

Portainer widget is not getting details from Portainer.
My Portainer URL doesn't contain "#!/endpoints/1", only "https://192.168.1.200/#!/1/kubernetes/dashboard"

Then I'm getting an API Error: The string did not match the expected pattern.

homepage version

v0.8.11

Installation method

Other (please describe above)

Configuration

- Portainer:
        icon: portainer.png
        href: https://192.168.1.200
        description: Container management
        siteMonitor: https://192.168.1.200
        statusStyle: "dot"
        widget:
            type: portainer
            url: https://192.168.1.200
            env: 1
            key: ptr_key
            fields: ["running", "stopped", "total"]

Container Logs

No response

Browser Logs

No response

Troubleshooting

curl -L -k -H 'X-Api-Key:ptr_key' 'https://192.168.1.200/api/endpoints/2/docker/containers/json'
{"message":"Unable to find an environment with the specified identifier inside the database","details":"object not found inside the database (bucket=endpoints, key=2)"}

[glime-ai[bot]]

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! ❤️

---

Based on the information provided, it seems that the Portainer widget configuration might be incorrect. The error message from the curl command indicates that the environment with the specified identifier (in this case, 2) cannot be found in the Portainer database. This could mean that the env value in your widget configuration is set incorrectly.

The env value should match the ID of the environment you want to connect to in Portainer. In your provided URL "https://192.168.1.200/#!/1/kubernetes/dashboard", the environment ID appears to be 1, which you have correctly set in your configuration. However, the curl command you tried uses 2 as the environment ID, which does not match your configuration and might not exist in your Portainer setup.

Please ensure that the env value in your widget configuration matches the actual environment ID in Portainer. You can verify the correct environment ID by looking at the URL when you select an environment in the Portainer UI. The ID is typically at the end of the URL after #!/endpoints/.

If you continue to experience issues, please check the following:

1. Ensure that the API key (ptr_key) is correct and has the necessary permissions.
2. Verify that there are no network issues preventing the homepage container from communicating with the Portainer instance.
3. Make sure that the Portainer instance is running and accessible at the URL specified in the widget configuration.

If you need further assistance, please provide additional details such as any error messages from the homepage container logs or browser console logs.

This comment was generated by Glime.

[dnielso5]

i think you are missing your port number in your config, unless you changed it to port 443. the default port is 9002 and should be url: http://192.168.1.200:9002

[paolos7709]

Hello @dnielso5. Thanks for your reply.
Yes, I changed ports for Portainer to 80 and 443. Here is my service yaml...

apiVersion: v1
kind: Service
metadata:
name: portainer
namespace: portainer
labels:
io.portainer.kubernetes.application.stack: portainer
app.kubernetes.io/name: portainer
app.kubernetes.io/instance: portainer
spec:
type: LoadBalancer
loadBalancerIP: 192.168.1.200
ports:
- port: 80
targetPort: 9000
protocol: TCP
name: http
- port: 443
targetPort: 9443
protocol: TCP
name: https
- port: 8000
targetPort: 8000
protocol: TCP
name: edge
selector:
app.kubernetes.io/name: portainer
app.kubernetes.io/instance: portainer

[shamoon]

The widget is not compatible with portainer kubernetes at the moment

[paolos7709]

OK, gotcha. Thanks @shamoon !

[github-actions[bot]]

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

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