Pi-Hole blocking access to NAS (docker install)

Help
1

Hi everybody,

I am experiencing a big problem.

I have a QNAP 653D NAS.
The IP of my NAS is 192.168.1.2.

I had Jellyfin working on a container without any issue. Accessing through http://192.168.1.2:8096/
I installed Pi-hole container, giving a static address of 192.168.1.50 but did not have a chance to setup a password for Pi-hole.

After installation, I instantly lost access to QTS and I lost file sharing access as well.

However, I can still perfectly access:

  • Jellyfin at http://192.168.1.2:8096/
  • Pi-Hole at 192.168.1.50 (which I can't log to because I could not set the password

Is it possible that Pi-Hole is blocking access to the NAS / 192.168.1.2?

All I am getting now is:

This site can’t be reached

192.168.1.2 took too long to respond.
Try:

Thank you very much.

2

Pi-hole is a domain blocker, and does not block IP's. When you request a web page at an IP address, no domain resolution is required and no DNS server is involved.

For example, to run ping dns.google, the domain must first be resolved to the IP for that domain. If you run ping 8.8.8.8 there is no domain name resolution involved.

3

@jfb is right, Pi-hole does not block IP addresses (it simply cannot). However, even if it would block it (when you would request my.nas.home or whatever), you'd not have to wait until a timeout appears such as:

because Pi-hole immediately blocks by sending 0.0.0.0. The error you would see in this case would be like "destination not reachable" and the effect would be instantaneous.

4

Hi guys,
Thanks a lot for your answers.

I think the issue is due to the fact that somehow Pi-hole service has taken over the normal access to 192.168.1.2.

It feels like dedicating 192.168.1.50 to Pi-hole on the Network1 interface which was already in use for 192.168.1.2 actually deactivated access to 192.168.1.2.

Maybe should have I used 192.168.1.2:port rather than 192.168.1.50?
=> is that possible?

I think the issue is not Pi-hole itself but the access to the NAS's address.

On this NAS there is 2 network access.
Strangely the second access (not fixed IP, being given 192.168.1.241 by DHCP) is not accessible either.

Maybe the fact that I installed Pi-hope container in bridge mode closed access to the NAS?

5

Hi Guys,
I think the issue was caused by ContainerStation, nothing to do with Pi-hole.
Maybe the error was caused by Jellyfin.

I hard-reset the QNAP 653D (hold the reset button 3s), then I was able to login normally.

  • ContainerStation was stopped, so I restarted it.
  • Pi-hole was happily running
  • Jellyfin was not

I deleted Jellyfin and re-installed it with the following configuration:

version: "3.3"
services:
jellyfin:
image: jellyfin/jellyfin
container_name: jellyfin
user: 1002:100
network_mode: "host"
volumes:
- /share/appdata/jellyfin/config:/config
- /share/appdata/jellyfin/cache:/cache
- /share/Films/A-Jellyfin:/media
restart: "unless-stopped"

All is well now, I have access to:

Thank you

6

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.