Pihole in docker new router

Currently reading
Pihole in docker new router

349
70
NAS
Synology DS920+
Operating system
  1. Windows
Mobile operating system
  1. Android
Recently updated my internet speed which included new modem and separate router. After several hours trying to access my DS920 through the router I finally got it to work. However I'm also running Pihole. I was notified that Pihole kept restarting and I can't seem to figure out why.

I stopped it and went into the Pihole Environment and changed the server IP to the Synologies new IP. Although that didn't help. Any suggestions appreciated. TIA
 
I see you cross posted this over on the pi.hole forums. I do a lot of docker replies for pi.hole over there and did reply over there.
 
I attached the log from docker which is were it's running from.

I also found this in my e-mail this morning, "Due to changes in default gateway settings, the feature of port forwarding rules has been disabled. Please check your network settings. From DS920." Thank you!
 

Attachments

  • docker_log.zip
    2 KB · Views: 10
Sorry, am a noob but I should have realized. I do see that for some reason Pihole is still using the old ip of .0.2 even though I stopped Pihole and typed in the new serverip.
 

Attachments

  • Pihole-Synology.zip
    36.4 KB · Views: 11
Appart from seeing complaint about the lighthttp configuration (which seem to be the reason your container is killed), there is nothing that hits the eye. You seem to have two server Ips configured: 192.168.0.2 and 192.168.1.2.

This seem to be the reason you container is killed:
2021-09-26 14:21:32stdout[cont-init.d] 20-start.sh: exited 1.
2021-09-26 14:21:32stdout2021-09-26 14:21:32: (configfile.c.1296) source: /etc/lighttpd/lighttpd.conf line: 98 pos: 1 parser failed somehow near here: (EOL)
2021-09-26 14:21:32stdout2021-09-26 14:21:32: (configfile.c.1296) source: find /etc/lighttpd/conf-enabled -name '*.conf' -a ! -name 'letsencrypt.conf' -printf 'include "%p"\n' 2>/dev/null line: 4 pos: 1 parser failed somehow near here: (EOL)
2021-09-26 14:21:32stdout2021-09-26 14:21:32: (configfile.c.1296) source: /etc/lighttpd/conf-enabled/15-fastcgi-php.conf line: 16 pos: 16 parser failed somehow near here: (COMMA)
2021-09-26 14:21:32stdout::: Testing lighttpd config: Error: duplicate array-key: ServerIP. Please get rid of the duplicate entry.

Though, the general network setup is unclear - did you replace your router? Did you chain the routers? Seems 192.168.1.2 is your main ip, is it the NAS ip and pihole is running in a bridged network - or is it using the host network or a macvlan ip?
 
Last edited:
Appart from seeing complaint about the lighthttp configuration (which seem to be the reason your container is killed), there is nothing that hits the eye. You seem to have two server Ips configured: 192.168.0.2 and 192.168.1.2.

This seem to be the reason you container is killed:


Though, the general network setup is unclear - did you replace your router? Did you chain the routers? Seems 192.168.1.2 is your main ip, is it the NAS ip and pihole is running in a bridged network - or is it using the host network or a macvlan ip?
Yes cable co replaced it with a pos router, took me forever to configure as I needed a smartphone app to do it. 192.168.1.2 is my nas ip and pihole is pointing to it. I believe it's bridge. Attaching a pick from pihole network tab as I'm not sure.
-- post merged: --

Don't know if this will help. But as you can see it's pointing to the nas under the variable Serverip
 

Attachments

  • docker.zip
    16 KB · Views: 13
  • pihole-2.zip
    81.4 KB · Views: 11

Create an account or login to comment

You must be a member in order to leave a comment

Create account

Create an account on our community. It's easy!

Log in

Already have an account? Log in here.

Similar threads

For the heck of it, I just checked again in docker container, and it announced an update was available. I...
Replies
4
Views
485
  • Question
Do realize, that enabling any user to run docker containers is largely the same as giving that user full...
Replies
6
Views
1,079
Hello, I already have it configured perfectly with wireguard. I was looking at the Gluetun configuration...
Replies
4
Views
760
Thanks... I tried something similar with rsync. The docker volume lived in...
Replies
7
Views
764
I can’t find any option to restore just the settings. 1710356648 Phew, managed to fix it. Within the...
Replies
4
Views
580
Good to hear. Deluge has not been updated for almost two years now as an app, nevertheless. But it gives...
Replies
12
Views
1,271
  • Question
Open an issue on that GitHub page. The developers will be glad to assist. OP has posted two threads on...
Replies
5
Views
1,234

Welcome to SynoForum.com!

SynoForum.com is an unofficial Synology forum for NAS owners and enthusiasts.

Registration is free, easy and fast!

Back
Top