Unable to connect to PiHole on MacVLAN network - Weird DNS Issues

[lukemcguire]

Environment

Docker

Version

0.15.4

Describe the problem

I'm trying to add my two PiHole instances to my dashboard and I'm running into a problem connecting to one of them.

I have one instance on a Raspberry Pi and I'm able to connect to that one (although at first I was running into this issue - 1988 but I was able to resolve it by pointing the internal url at the /admin url instead of just the base url (not sure why that worked).

However, for the second one I just get a continuous loading on the ping status. Also, it doesn't show up in the "DNS Hole Controls" widget. I tried to check from inside the shell in the container and I ran into some strange things.

1. There's no ping or curl in the container but I was able to use wget
2. When I try to check my connectivity to this instance I get the following:

root@133bccef2010:/app# wget --spider http://192.168.4.198/admin
Spider mode enabled. Check if remote file exists.
--2024-10-04 19:01:10--  http://192.168.4.198/admin
Connecting to 192.168.4.198:80... failed: No route to host.

This PiHole instance is in a container on the same box (Synology) so I had to create a MacVLAN network to get it to work correctly. I'm wondering if maybe that's where my issues are coming from but I may just be grasping.

Logs

2024-10-04T19:10:10.105938271Z  Exporting hostname...
2024-10-04T19:10:10.156917863Z  Migrating database...
2024-10-04T19:10:11.866572414Z  yarn run v1.22.19
2024-10-04T19:10:12.539664206Z  $ ts-node ./migrate.ts
2024-10-04T19:10:26.120763902Z  Done in 14.26s.
2024-10-04T19:10:26.296674780Z  Starting production server...
2024-10-04T19:10:46.508666607Z  Listening on port 7575 url: http://133bccef2010:7575
2024-10-04T19:13:01.163020428Z
2024-10-04T19:13:01.317236686Z   ERROR  Unexpected response: connect EHOSTUNREACH 192.168.4.198:80
2024-10-04T19:13:01.317356314Z
2024-10-04T19:14:04.318010970Z
2024-10-04T19:14:04.496447918Z   ERROR  Unexpected response: connect EHOSTUNREACH 192.168.4.198:80
2024-10-04T19:14:04.496614911Z

Context

Please tick the boxes

• I confirm that I attached the proper logs
• I've read the docs
• I've checked for duplicate issues
• I've tried to debug myself

[github-actions]

Hi 👋. Thank you for submitting your first issue to Homarr. Please ensure that you've provided all nessesary information. You can use the three dots > Edit button to update your post with additional images and information. Depending on the current volume of requests, the team should get in conact with you shortly.

[manuel-rw]

We are unable to help you with network related issues.
According to your tests, it is likely that you misconfigured something:
Connecting to 192.168.4.198:80... failed: No route to host.

Please check:

• Your firewall
• Your router
• VLANs
• Whether your host can reach it
• Logs
• ...

[github-actions]

Hello 👋, this issue has been open for 60 days without activity. We mark issues to help prioritise and close dead issues. Can you confirm that this issue is still relevant on the latest version? I'll remove the stale label as soon as there is further activity on this issue. Thank you 🙏