Pihole in docker new router

Currently reading
Pihole in docker new router

334
67
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

Finally got it dl'd and installed. Had to reconfigure the router.
Replies
4
Views
2,286
Sorry for not replying sooner as I am not getting notification. However, I did manage getting pihole up...
Replies
9
Views
1,695
I'm using adguard/adguardhome and crazymax/unbound. Point Adguard at the unbound box as the upbound server...
Replies
1
Views
2,203
Not sure what's happening but I went drastic. I shut down the PC and did a hard reset of the modem, "enter...
Replies
9
Views
1,961
This indeed is a breaking change. The whole function fix_capabilities() is responsible for the behavior...
Replies
10
Views
2,757
I've been running pihole in Docker on my DS920. The only issue I've had is with doing updates. I dl the...
Replies
0
Views
1,738
sorry, was away for a few days. yes, I was talking about the logs that you find in synology. but...
Replies
4
Views
3,896

Welcome to SynoForum.com!

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

Registration is free, easy and fast!

Back
Top