Andyman
September 16, 2021, 11:28am
1
Hi everyone,
as the subject already suggests my pihole doesn't working anymore after the update.
More precisely I get a "connection refused" if I want to connect to the web admin interface.
This pihole runs on a raspi 4 8GB with twisterOS.
I already did a debug for this pihole. Please find the token below.
For further information:
I did also an update on my synology docker, where my second pihole runs.
After the update -> recreating the docker container, I ran into the same issue. But in this case, I switched back to the previous (older) container and it works again.
Thanks a lot in advance for your help!!
Debug Token:
https://tricorder.pi-hole.net/PwIgVS0e/
jfb
September 16, 2021, 1:36pm
2
What is the exact URL you are using to access the web admin GUI?
Andyman
September 16, 2021, 1:51pm
3
thx for your reply.
I have tested it with..
and nothing works. Generally I am always working with this bookmarked URL http://192.168.1.199:8888/admin/ .
The web server listens on port 80, not 8888.
Andyman
September 16, 2021, 2:00pm
5
yes, but I changed it to 8888, because of deCONZ/phoscon and it works flawlessly until I updated the pihole to the newest version.
In the meantime, I deactivated deconz completely, but this wasn't the solution.
pihole -d "tells" me that too, that port 80 is now free.
Update:
I found the issue... unfortunately, my /etc/lighttpd/lighttpd.conf was overwritten and the /etc/lighttpd/external.conf was deleted (by the update of the pihole?!) ...
I changed the port of the web admin/server back to 8888 and now it works.
Thanks a lot for your help!! Topic can be closed.
jfb
September 16, 2021, 2:28pm
6
Yes, as clearly indicated in the prominent header in that file:
###############################################################################
# FILE AUTOMATICALLY OVERWRITTEN BY PI-HOLE INSTALL/UPDATE PROCEDURE. #
# ANY CHANGES MADE TO THIS FILE AFTER INSTALL WILL BE LOST ON THE NEXT UPDATE #
# #
# CHANGES SHOULD BE MADE IN A SEPARATE CONFIG FILE: #
# /etc/lighttpd/external.conf #
###############################################################################
Changes to the lighttpd port should be made in the external.conf file, which is not subject to be overwritten by a Pi-hole repair or update.
Thank you! This worked for me
1 Like
Andyman
September 16, 2021, 3:53pm
7
I didn't dive so deep into it, thats why I couldn't help myself this time.
Thanks again!
But one more question please, are there any known issues with updating the docker container?
I did it now a few times, but it still doesn't work. The container keeps restarting.
It is unfortunately also not possible to do a debug.
jfb
September 16, 2021, 4:41pm
8
You don't use the pihole -up command with a container. You load a new container image that already has the latest version. I believe we have updated the image - @PromoFaux can you confirm?
1 Like
Yep, there is a new image for latest Pi-holes. Though I have seen a couple people mention that they're having issues updating
opened 03:55AM - 13 Sep 21 UTC
<!-- pick ONE: Bug,
Feature Request,
Run Issue… (running Pi-hole container failing),
Build Issue (Building image failing)
Enter in line below: -->
This is a: Run issue
## Details
After upgrade to a newest version of Pihole I can't start it anymore.
Pihole log:
```
pihole | [s6-init] making user provided files available at /var/run/s6/etc...exited 0.
pihole | [s6-init] ensuring user provided files have correct perms...exited 0.
pihole | [fix-attrs.d] applying ownership & permissions fixes...
pihole | [fix-attrs.d] 01-resolver-resolv: applying...
pihole | [fix-attrs.d] 01-resolver-resolv: exited 0.
pihole | [fix-attrs.d] done.
pihole | [cont-init.d] executing container initialization scripts...
pihole | [cont-init.d] 20-start.sh: executing...
pihole | ::: Starting docker specific checks & setup for docker pihole/pihole
pihole | Assigning random password: yNlWOoIF
pihole |
pihole | [i] Installing configs from /etc/.pihole...
pihole | [i] Existing dnsmasq.conf found... it is not a Pi-hole file, leaving alone!
[✓] Installed /etc/dnsmasq.d/01-pihole.conf
[✓] Installed /etc/dnsmasq.d/06-rfc6761.conf
pihole | sed: cannot rename /etc/pihole/sedjiaqIV: Device or resource busy
pihole | [cont-init.d] 20-start.sh: exited 4.
pihole | [cont-finish.d] executing container finish scripts...
pihole | [cont-finish.d] done.
pihole | [s6-finish] waiting for services.
pihole | [s6-finish] sending all processes the TERM signal.
pihole | [s6-finish] sending all processes the KILL signal and exiting.
pihole | [s6-init] making user provided files available at /var/run/s6/etc...exited 0.
pihole | [s6-init] ensuring user provided files have correct perms...exited 0.
pihole | [fix-attrs.d] applying ownership & permissions fixes...
pihole | [fix-attrs.d] 01-resolver-resolv: applying...
pihole | [fix-attrs.d] 01-resolver-resolv: exited 0.
pihole | [fix-attrs.d] done.
pihole | [cont-init.d] executing container initialization scripts...
pihole | [cont-init.d] 20-start.sh: executing...
pihole | ::: Starting docker specific checks & setup for docker pihole/pihole
pihole | Assigning random password: o5lztVC0
pihole |
pihole | [i] Installing configs from /etc/.pihole...
pihole | [i] Existing dnsmasq.conf found... it is not a Pi-hole file, leaving alone!
[✓] Installed /etc/dnsmasq.d/01-pihole.conf
[✓] Installed /etc/dnsmasq.d/06-rfc6761.conf
pihole | sed: cannot rename /etc/pihole/sednAGmC1: Device or resource busy
pihole | [cont-init.d] 20-start.sh: exited 4.
pihole | [cont-finish.d] executing container finish scripts...
pihole | [cont-finish.d] done.
pihole | [s6-finish] waiting for services.
pihole | [s6-finish] sending all processes the TERM signal.
pihole | [s6-finish] sending all processes the KILL signal and exiting.
pihole | [s6-init] making user provided files available at /var/run/s6/etc...exited 0.
pihole | [s6-init] ensuring user provided files have correct perms...exited 0.
pihole | [fix-attrs.d] applying ownership & permissions fixes...
pihole | [fix-attrs.d] 01-resolver-resolv: applying...
pihole | [fix-attrs.d] 01-resolver-resolv: exited 0.
pihole | [fix-attrs.d] done.
pihole | [cont-init.d] executing container initialization scripts...
pihole | [cont-init.d] 20-start.sh: executing...
pihole | ::: Starting docker specific checks & setup for docker pihole/pihole
pihole | Assigning random password: 6cgD9vR8
pihole |
pihole | [i] Installing configs from /etc/.pihole...
pihole | [i] Existing dnsmasq.conf found... it is not a Pi-hole file, leaving alone!
[✓] Installed /etc/dnsmasq.d/01-pihole.conf
[✓] Installed /etc/dnsmasq.d/06-rfc6761.conf
pihole | sed: cannot rename /etc/pihole/sed98enT1: Device or resource busy
pihole | [cont-init.d] 20-start.sh: exited 4.
pihole | [cont-finish.d] executing container finish scripts...
pihole | [cont-finish.d] done.
pihole | [s6-finish] waiting for services.
pihole | [s6-finish] sending all processes the TERM signal.
pihole | [s6-finish] sending all processes the KILL signal and exiting.
```
If I rollback to pihole/pihole:v5.8.1 - everything works fine.
## Related Issues
- [x] I have searched this repository/Pi-hole forums for existing issues and pull requests that look similar
## How to reproduce the issue
1. Environment data
* Operating System: Raspbian GNU/Linux 10
* Hardware: Raspberry PI 4
* Kernel Architecture: armv7l
* Docker Install Info and version:
- Software source: docker-ce, docker-compose
- Supplimentary Software:
* Hardware architecture: ARMv7
2. docker-compose.yml contents, docker run shell command, or paste a screenshot of any UI based configuration of containers here
```
pihole:
container_name: pihole
image: pihole/pihole:latest
hostname: pi-hole
mac_address: d0:ca:ab:cd:ef:01
cap_add:
- NET_ADMIN
ports:
- 443/tcp
- 53/tcp
- 53/udp
# - 67/udp # Uncomment if you want to use Pi-Hole for DHCP
- 80/tcp
# - 22/tcp
environment:
ServerIP: 192.168.88.5
# WEBPASSWORD: ${WEBPASSWORD}
DNS1: 192.168.88.6
volumes:
- ./work_pihole:/etc/pihole:rw
- ./config-pihole/hosts:/etc/hosts:ro
- ./config-pihole/resolv.conf:/etc/resolv.conf:ro
- ./config-pihole/dnsmasq.conf:/etc/dnsmasq.d/02-network.conf:ro
- ./config-pihole/pihole-FTL.conf:/etc/pihole/pihole-FTL.conf:ro
networks:
home:
ipv4_address: 192.168.88.5
restart: unless-stopped
unbound:
container_name: unbound
image: mvance/unbound-rpi:latest
hostname: syn-unbound
mac_address: d0:ca:ab:cd:ef:02
ports:
- 53/tcp
- 53/udp
volumes:
- ./config-unbound:/opt/unbound/etc/unbound:rw
networks:
home:
ipv4_address: 192.168.88.6
restart: unless-stopped
```
3. any additional info to help reproduce
## These common fixes didn't work for my issue
- [X] I have tried removing/destroying my container, and re-creating a new container
- [x] I have tried fresh volume data by backing up and moving/removing the old volume data
- [ ] I have tried running the stock `docker run` example(s) in the readme (removing any customizations I added)
- [x] I have tried a newer or older version of Docker Pi-hole (depending what version the issue started in for me)
- [ ] I have tried running without my volume data mounts to eliminate volumes as the cause
If the above debugging / fixes revealed any new information note it here.
Add any other debugging steps you've taken or theories on root cause that may help.
1 Like
system
Closed
October 7, 2021, 5:46pm
10
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.