proxmox integration not working after migration
I just migrated an instance of 0.15 to 1.19, and realised that a proxmox integration is not working. It works still on the old, but not on the new. I tried creating a new one, but the error message is still the same
FaILED to call GET https://192.168.10.1:8006/api2/json/nodes cause by:certificate has expired
I tried setting up a new credentials, same thing
Docker logs
2025-05-15T14:42:29.257957898Z 2025-05-15T14:42:29.257Z error: tRPC Error with mutation on 'integration.create'
2025-05-15T14:42:29.258028342Z at Object.onError (/app/apps/nextjs/.next/server/app/api/trpc/[trpc]/route.js:1:5059)
2025-05-15T14:42:29.258039323Z at Object.onError (/app/apps/nextjs/.next/server/app/api/trpc/[trpc]/route.js:1:4213)
2025-05-15T14:42:29.258047471Z at /app/apps/nextjs/.next/server/chunks/4047.js:98:5069
2025-05-15T14:42:29.258054842Z at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
2025-05-15T14:42:29.258099952Z at async /app/apps/nextjs/.next/server/chunks/4047.js:98:7029
2025-05-15T14:42:29.258109545Z at async /app/apps/nextjs/.next/server/chunks/4047.js:86:869918
2025-05-15T14:42:29.258116841Z caused by Error: Checking integration connection failed key="internalServerError" detailMessage="FaILED to call GET https://192.168.10.1:8006/api2/json/nodes cause by:certificate has expired"
2025-05-15T14:42:29.258124878Z at /app/apps/nextjs/.next/server/chunks/8148.js:6:16836
2025-05-15T14:42:29.258131674Z at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
2025-05-15T14:42:29.258138693Z at async sD.testConnectionAsync (/app/apps/nextjs/.next/server/chunks/8148.js:6:16799)
2025-05-15T14:42:29.258145600Z at async s1 (/app/apps/nextjs/.next/server/chunks/8148.js:6:24488)
2025-05-15T14:42:29.258187729Z at async u (/app/apps/nextjs/.next/server/chunks/4047.js:92:68)
Proxmox, docker,
Version 1.19.14 Replies
Thank you for submitting a support request.
Depending on the volume of requests, our team should get in contact with you shortly.
⚠️ Please include the following details in your post or we may reject your request without further comment: - Log (See https://homarr.dev/docs/community/faq#how-do-i-open-the-console--log) - Operating system (Unraid, TrueNAS, Ubuntu, ...) - Exact Homarr version (eg. 0.15.0, not latest) - Configuration (eg. docker-compose, screenshot or similar. Use ``your-text`` to format) - Other relevant information (eg. your devices, your browser, ...)
Frequently Asked Questions | Homarr documentation
Can I install Homarr on a Raspberry Pi?
certificate has expired -> your certificate has expired, update the certificate and upload the updated certificate to Homarrdoes that mean that homaar 1.19, in comparisson to 0.15, requires a certificate? because, my instance of 0.15 can connect without problems to proxmox, and 1.19 has the error. Same configuration parameters. I migrated to 1.19 with the migration tool.
I did not create a certificate for the 0.15 instance.
It seems more to me like a bug. I see that others had the same error if the realm information was still attached. judging on this, I would rather say that the error message might not be correct.
See https://homarr.dev/docs/management/certificates/ , the message is correct. This or next week's update will contain a huge update about how we handle certificates. You might want to wait for that update.
Certificates | Homarr documentation
On this page you can manage your trusted certificates.