Proxmox integration is working, but ping fails

I am running into a small issue. My Proxmox integration is working meaning I can use the widget, but the app ping is failing. My configuration. Integration configuration Host = https://<localdomain>:8006 App configuration Host = https://<localdomain>:8006 I also tried using an alternate ping using http:<localip>:8006. Both options give "Fetch failed" on the front end.
49 Replies
Cakey Bot
Cakey Bot2mo ago
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?
CrankyPunisher
CrankyPunisherOP2mo ago
The corresponding log entries
2025-07-03T19:56:02.816Z error Failed to send ping request to "https://<localdomain>"
2025-07-03T19:56:02.818Z error Executing ping for url https://<localdomain> failed with error: fetch failed
2025-07-03T19:56:02.816Z error Failed to send ping request to "https://<localdomain>"
2025-07-03T19:56:02.818Z error Executing ping for url https://<localdomain> failed with error: fetch failed
The log only shows an error for the specified host, but I don't see any error messages for the alternative ping.
Meierschlumpf
Meierschlumpf2mo ago
Hmm weird that it just says fetch failed, most of the times it also has an error below that Is this from the homarr logs page or from docker / unraid logs?
CrankyPunisher
CrankyPunisherOP2mo ago
homarr logs page
Meierschlumpf
Meierschlumpf2mo ago
Okay can you check what it says in the docker / unraid logs? The logs page somehow only shows the first row or something
CrankyPunisher
CrankyPunisherOP2mo ago
No description
Meierschlumpf
Meierschlumpf2mo ago
Yes here it just extracts the error message, but in the logs you should find more infos
CrankyPunisher
CrankyPunisherOP2mo ago
The log shows a lot of tlines. I have only included the two lines repeating themselves every couple of seconds.
Meierschlumpf
Meierschlumpf2mo ago
But there should be something like
at /path/to/file.js
at /path/to/file.js
at /path/to/file.js
at /path/to/file.js
at /path/to/file.js
at /path/to/file.js
at /path/to/file.js
at /path/to/file.js
in multiple lines in the logs (that are not inside homarrs webui)
CrankyPunisher
CrankyPunisherOP2mo ago
Let me copy a few messages around the messages shown No, I don't see any lines like that
2025-07-03T19:55:57.758Z warn The callback of 'mediaServer' succeeded but took 16.08ms longer than expected (2500ms). This may indicate that your network performance, host performance or something else is too slow. If this happens too often, it should be looked into.
2025-07-03T19:56:02.768Z info Found 11 resources in Proxmox cluster node=1 lxc=0 qemu=6 storage=3
2025-07-03T19:56:02.816Z error Failed to send ping request to "https://localdomain>"
2025-07-03T19:56:02.818Z error Executing ping for url https://<localdomain> failed with error: fetch failed
2025-07-03T19:56:03.646Z warn The callback of 'dnsHole' succeeded but took 26.20ms longer than expected (2500ms). This may indicate that your network performance, host performance or something else is too slow. If this happens too often, it should be looked into.
2025-07-03T19:56:03.902Z warn The callback of 'mediaRequestList' succeeded but took 293.52ms longer than expected (2500ms). This may indicate that your network performance, host performance or something else is too slow. If this happens too often, it should be looked into.
2025-07-03T19:56:05.760Z info No active video sessions found in MediaContainer
2025-07-03T19:55:57.758Z warn The callback of 'mediaServer' succeeded but took 16.08ms longer than expected (2500ms). This may indicate that your network performance, host performance or something else is too slow. If this happens too often, it should be looked into.
2025-07-03T19:56:02.768Z info Found 11 resources in Proxmox cluster node=1 lxc=0 qemu=6 storage=3
2025-07-03T19:56:02.816Z error Failed to send ping request to "https://localdomain>"
2025-07-03T19:56:02.818Z error Executing ping for url https://<localdomain> failed with error: fetch failed
2025-07-03T19:56:03.646Z warn The callback of 'dnsHole' succeeded but took 26.20ms longer than expected (2500ms). This may indicate that your network performance, host performance or something else is too slow. If this happens too often, it should be looked into.
2025-07-03T19:56:03.902Z warn The callback of 'mediaRequestList' succeeded but took 293.52ms longer than expected (2500ms). This may indicate that your network performance, host performance or something else is too slow. If this happens too often, it should be looked into.
2025-07-03T19:56:05.760Z info No active video sessions found in MediaContainer
I currently only have one recurring "error" in my log
2025-07-03T20:08:58.057Z error Failed to run integration job integration=b93mhywzinnfk2bkesi8xu02 inputHash='W3sic2hvd09ubHlQbGF5aW5nIjp0cnVlfV0='
2025-07-03T20:08:58.057Z error Failed to run integration job integration=b93mhywzinnfk2bkesi8xu02 inputHash='W3sic2hvd09ubHlQbGF5aW5nIjp0cnVlfV0='
Meierschlumpf
Meierschlumpf2mo ago
Hmm, but where did you take the above logs now?
CrankyPunisher
CrankyPunisherOP2mo ago
All from Tools -> Logs Lots of info messages
Meierschlumpf
Meierschlumpf2mo ago
Okay can you take them from your proxmox service now? As I said there is probably an issue with the logs webui page that it only shows the first line of log messages
CrankyPunisher
CrankyPunisherOP2mo ago
Very few warning messages. Most on 'mediaServer'. Oh, ok. One second. I misunderstood.
Meierschlumpf
Meierschlumpf2mo ago
No problem 😉
Meierschlumpf
Meierschlumpf2mo ago
Created an issue regarding the multiline problem in the logs webui: https://github.com/homarr-labs/homarr/issues/3537
GitHub
bug: webui logs only show first line · Issue #3537 · homarr-labs/...
Describe the bug It seems like the logs in the webui only show the first line of the logs. This is especially a problem with error logs which have the cause in them and so don&#39;t show the actual...
CrankyPunisher
CrankyPunisherOP2mo ago
OK. I am looking at the proxmox log now. There are no error messages I can identify as related. Here is a snapshot of the last two hours.
Jul 03 11:06:46 pve1 smartd[844]: Device: /dev/sdc [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 27 to 28
Jul 03 11:17:01 pve1 CRON[3500659]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jul 03 11:17:01 pve1 CRON[3500660]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Jul 03 11:17:01 pve1 CRON[3500659]: pam_unix(cron:session): session closed for user root
Jul 03 11:22:53 pve1 systemd[1]: Starting apt-daily.service - Daily apt download activities...
Jul 03 11:22:55 pve1 systemd[1]: apt-daily.service: Deactivated successfully.
Jul 03 11:22:55 pve1 systemd[1]: Finished apt-daily.service - Daily apt download activities.
Jul 03 11:22:55 pve1 systemd[1]: apt-daily.service: Consumed 1.634s CPU time.
Jul 03 12:17:01 pve1 CRON[3509940]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jul 03 12:17:01 pve1 CRON[3509941]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Jul 03 12:17:01 pve1 CRON[3509940]: pam_unix(cron:session): session closed for user root
Jul 03 12:36:46 pve1 smartd[844]: Device: /dev/sdc [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 28 to 31
Jul 03 13:12:38 pve1 pvedaemon[2252007]: <root@pam> successful auth for user 'root@pam'
Jul 03 13:16:02 pve1 pveproxy[3479903]: worker exit
Jul 03 13:16:02 pve1 pveproxy[3054846]: worker 3479903 finished
Jul 03 13:16:02 pve1 pveproxy[3054846]: starting 1 worker(s)
Jul 03 13:16:02 pve1 pveproxy[3054846]: worker 3519633 started
Jul 03 11:06:46 pve1 smartd[844]: Device: /dev/sdc [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 27 to 28
Jul 03 11:17:01 pve1 CRON[3500659]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jul 03 11:17:01 pve1 CRON[3500660]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Jul 03 11:17:01 pve1 CRON[3500659]: pam_unix(cron:session): session closed for user root
Jul 03 11:22:53 pve1 systemd[1]: Starting apt-daily.service - Daily apt download activities...
Jul 03 11:22:55 pve1 systemd[1]: apt-daily.service: Deactivated successfully.
Jul 03 11:22:55 pve1 systemd[1]: Finished apt-daily.service - Daily apt download activities.
Jul 03 11:22:55 pve1 systemd[1]: apt-daily.service: Consumed 1.634s CPU time.
Jul 03 12:17:01 pve1 CRON[3509940]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jul 03 12:17:01 pve1 CRON[3509941]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Jul 03 12:17:01 pve1 CRON[3509940]: pam_unix(cron:session): session closed for user root
Jul 03 12:36:46 pve1 smartd[844]: Device: /dev/sdc [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 28 to 31
Jul 03 13:12:38 pve1 pvedaemon[2252007]: <root@pam> successful auth for user 'root@pam'
Jul 03 13:16:02 pve1 pveproxy[3479903]: worker exit
Jul 03 13:16:02 pve1 pveproxy[3054846]: worker 3479903 finished
Jul 03 13:16:02 pve1 pveproxy[3054846]: starting 1 worker(s)
Jul 03 13:16:02 pve1 pveproxy[3054846]: worker 3519633 started
As you can see it shows me logging on as root just a few minutes ago.
Meierschlumpf
Meierschlumpf2mo ago
Sorry I didn't meant that either 😂 I meant the homarr logs from your proxmox vm (or whatever it is in proxmox) where your homarr service is running. So just that what is logged from running homarr. For example when I run homarr with docker I can do docker container logs <containerId>
CrankyPunisher
CrankyPunisherOP2mo ago
docker log?
Meierschlumpf
Meierschlumpf2mo ago
I guess you are running the proxmox community script, right?
CrankyPunisher
CrankyPunisherOP2mo ago
Not sure. What does it do?
Meierschlumpf
Meierschlumpf2mo ago
How did you install homarr?
CrankyPunisher
CrankyPunisherOP2mo ago
Ubuntu server install on proxmox. Then dockstarter. I have created an override in dockstarter that pulls and iexecutes a compose.
Meierschlumpf
Meierschlumpf2mo ago
Okay so you are running homarr with docker behind the hood (by using dockstarter) I would guess, can you run docker container ls? this will list all containers that are running
CrankyPunisher
CrankyPunisherOP2mo ago
I am seeing tons of the errors you are looking for in the homarr container docker log Trying to get to the latest entries Oh, my, it is scrolling for like 5 minutes now... 😉 Let me see if there is a linux command to get the last 50 linesor so.
2025-07-03T20:32:03.479Z error: Executing ping for url https://<localdomain.> failed with error: fetch failed
242:C 03 Jul 2025 20:32:03.514 * DB saved on disk
242:C 03 Jul 2025 20:32:03.521 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB
2025-07-03T20:32:03.571Z info: Found 11 resources in Proxmox cluster node=1 lxc=0 qemu=6 storage=3
2025-07-03T20:32:03.479Z error: Executing ping for url https://<localdomain.> failed with error: fetch failed
242:C 03 Jul 2025 20:32:03.514 * DB saved on disk
242:C 03 Jul 2025 20:32:03.521 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB
2025-07-03T20:32:03.571Z info: Found 11 resources in Proxmox cluster node=1 lxc=0 qemu=6 storage=3
I found the line giving thec error above
Error: connect ECONNREFUSED 192.168.68.16:443 errno="-111" code="ECONNREFUSED" syscall="connect" address="192.168.68.16" port="443"
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1636:16)
Error: connect ECONNREFUSED 192.168.68.16:443 errno="-111" code="ECONNREFUSED" syscall="connect" address="192.168.68.16" port="443"
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1636:16)
This message seems to indicate that proxmox is refusing the request.
Meierschlumpf
Meierschlumpf2mo ago
Do you use the ip or domain for the pingUrl / integrationUrl?
CrankyPunisher
CrankyPunisherOP2mo ago
In the integration I am using https://<url>:8006
Meierschlumpf
Meierschlumpf2mo ago
And the ping is using 443 it seems, no? So you'll need to add the port I would guess
CrankyPunisher
CrankyPunisherOP2mo ago
The proxmox firewall has only one rule at the moment. It allows ping requests. I have added a second rule to accept https requests. No change. Maybe this sectionof the log is more helpful?
Meierschlumpf
Meierschlumpf2mo ago
No I meant your pingUrl probably has https://<url> instead of https://<url>:8006
CrankyPunisher
CrankyPunisherOP2mo ago
2025-07-03T20:45:02.700Z error: Failed to send ping request to "https://<localdomain>"
at sendPingRequestAsync (/app/apps/tasks/tasks.cjs:640487:18)
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
at async pingAsync (/app/apps/tasks/tasks.cjs:640518:22)
at async Promise.allSettled (index 4)
at async /app/apps/tasks/tasks.cjs:640515:3
at async catchingCallbackAsync (/app/apps/tasks/tasks.cjs:625478:9)
caused by TypeError: fetch failed
at fetch6 (/app/apps/tasks/tasks.cjs:20625:17)
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
at async sendPingRequestAsync (/app/apps/tasks/tasks.cjs:640485:12)
at async pingAsync (/app/apps/tasks/tasks.cjs:640518:22)
at async Promise.allSettled (index 4)
at async /app/apps/tasks/tasks.cjs:640515:3
at async catchingCallbackAsync (/app/apps/tasks/tasks.cjs:625478:9)
caused by Error: connect ECONNREFUSED 192.168.68.16:443 errno="-111" code="ECONNREFUSED" syscall="connect" address="192.168.68.16" port="443"
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1636:16)
2025-07-03T20:45:02.714Z error: Executing ping for url https://<localdomain> failed with error: fetch failed
2025-07-03T20:45:02.700Z error: Failed to send ping request to "https://<localdomain>"
at sendPingRequestAsync (/app/apps/tasks/tasks.cjs:640487:18)
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
at async pingAsync (/app/apps/tasks/tasks.cjs:640518:22)
at async Promise.allSettled (index 4)
at async /app/apps/tasks/tasks.cjs:640515:3
at async catchingCallbackAsync (/app/apps/tasks/tasks.cjs:625478:9)
caused by TypeError: fetch failed
at fetch6 (/app/apps/tasks/tasks.cjs:20625:17)
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
at async sendPingRequestAsync (/app/apps/tasks/tasks.cjs:640485:12)
at async pingAsync (/app/apps/tasks/tasks.cjs:640518:22)
at async Promise.allSettled (index 4)
at async /app/apps/tasks/tasks.cjs:640515:3
at async catchingCallbackAsync (/app/apps/tasks/tasks.cjs:625478:9)
caused by Error: connect ECONNREFUSED 192.168.68.16:443 errno="-111" code="ECONNREFUSED" syscall="connect" address="192.168.68.16" port="443"
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1636:16)
2025-07-03T20:45:02.714Z error: Executing ping for url https://<localdomain> failed with error: fetch failed
CrankyPunisher
CrankyPunisherOP2mo ago
No description
CrankyPunisher
CrankyPunisherOP2mo ago
I do have the port
Meierschlumpf
Meierschlumpf2mo ago
Do you have a pingUrl configured (when you check the box below?) maybe we have a bug, that once defined you have to remove the value and can not only remove the checkbox
CrankyPunisher
CrankyPunisherOP2mo ago
Yes, I have tried using it. Let me check it and uncheck it. That should fix it, right?
Meierschlumpf
Meierschlumpf2mo ago
No, check it and if there is content in the pingUrl input, remove it and then uncheck it again
CrankyPunisher
CrankyPunisherOP2mo ago
When I checked it again, it didn't bring my previous configuration back. It remained blank. So, I unchecked it and saved it again, but no change.
Meierschlumpf
Meierschlumpf2mo ago
Hmm okay, I'll need to check the code quickly, but it's weird that it says that ECONNREFUSED with port 443
CrankyPunisher
CrankyPunisherOP2mo ago
No worries. I was already happy that I could finally get the widget back to work! 🙂
Meierschlumpf
Meierschlumpf2mo ago
Okay doesn't seem like we remove the port somewhere, is the above log really from proxmox and not from another app?
CrankyPunisher
CrankyPunisherOP2mo ago
I am puzzled that I don't see log entries when I am trying to use the alternative option. Shouldn't it show the fail for that in the log as well? At the moment, I can add a ping alternative and there is no change in the log at all... Nope. The port seems to be specified everywhere. The log sent at 13:17 is proxmox 13:47 is homarr docker log Sorry, if I wasn't clear on that
Meierschlumpf
Meierschlumpf2mo ago
I know that, sorry I meant that the ping error shown in the docker container log could be from another app that is pinged
CrankyPunisher
CrankyPunisherOP2mo ago
nope
Meierschlumpf
Meierschlumpf2mo ago
Hmm okay
CrankyPunisher
CrankyPunisherOP2mo ago
From my point of view, I am not surprised that the https ping is failing from within the docker container, but I was expecting the http://<ip>:8006 alternative to work. But then I am not a developer... 😉
Hachikö
Hachikö2mo ago
how did you get it to work? Mine is not working. getting "The certificate has expired." even though when checking: "Valid from Wednesday, March 13, 2024 at 1:00:00 AM GMT+1 Valid to Saturday, March 13, 2027 at 12:59:59 AM GMT+1" Even tried making a new integration with new user and everything but get same error, says certificate has expired even though its just created.
Meierschlumpf
Meierschlumpf2mo ago
Is this the ca / root certificate or something else?
CrankyPunisher
CrankyPunisherOP2mo ago
I looked up the raw root certificate in proxmox, copied the begin/end block into a cert.crt file and then I imported this file into homarr. I still got a warning messaqge in homarr when setting up the integration, but it gives an option to override the warning. Once confirmed the integration is saved and activated!
Hachikö
Hachikö2mo ago
did not work for me. tried it several times and now my old proxmox integration dont work either. So i'll guess i just have to wait until it gets fixed.

Did you find this page helpful?