R
Runtipi‱2w ago
Whar

Connection reset by peer

Hi! Every time I try to install a new app, I get the following error:
2025-11-27T08:28:53.297Z - error > Failed to install app lidarr:migrated: failed to copy: read tcp [2a0c:5a86:3d87:8000:a2b5:60b2:da6c:459a]:34978->[2606:50c0:8001::154]:443: read: connection reset by peer
2025-11-27T08:28:53.297Z - error > Failed to install app lidarr:migrated: failed to copy: read tcp [2a0c:5a86:3d87:8000:a2b5:60b2:da6c:459a]:34978->[2606:50c0:8001::154]:443: read: connection reset by peer
But before I'll add a bit of context. Yesterday, the error I was getting was the Timeout one. When I tried to install something, the installation would get stuck and Runtipi would force a Sync, changing the status from "Installing" to "Stopped". Then, after trying to run the "App", it would get stuck and remove it since, I suppose, I didn't got installed in the first place. I read a few of the GitHub issues and found, not the same, but similar cases. So I did the following:
sudo ./runtipi-cli stop
sudo ./runtipi-cli update latest
sudo ./runtipi-cli stop
sudo ./runtipi-cli update latest
Sadly, with this I lost those logs and can't share them, but then the problem changed and wasn't able to find anything similar either here or GitHub. At first I though, "maybe pihole is slowing the connection?". Since I was able to install apps before configuring it. But even if I stopped it and used Clouflare or Google DNS, I had the same problems. I also tried using a different store than migrated, but it doesn't work either. I'm sharing the logs and the runtipi-cl debug results. I don't know why but the debug command returns no containers found when I have 6 app installed, running and working! There's only logs for two apps, because I've restarted Runtipi a few times while trying things and those are my last tries, but I get the same error with any app I try to install. Hardware: Raspberry Pi 5 16GB OS: Raspberry Pi OS
35 Replies
MOUETTE03
MOUETTE03‱2w ago
Hello, it looks like a connection problem between your hardware and github. Have you tried restarting your raspberry and router ?
InfBoumcyCastle
InfBoumcyCastle‱2w ago
any active vpn connection on the tipi server?
Whar
WharOP‱2w ago
I'll try at night when I don't bother anyone and report the results, thank you. @InfBoumcyCastle no, I'm not using any VPN.
Whar
WharOP‱2w ago
I don't know if this is good or bad news, but after restarting we're back at the timeout error!
MOUETTE03
MOUETTE03‱2w ago
It really looks like a connection problem. Did you change anything just before the problem started ?
Whar
WharOP‱7d ago
The only thing network related I've installed was pihole, but even if I disable it I get one of the two errors. The other thing I've changed is that I added a new disk and mounted it on /media, but the apps that are already installed don't seem to have a problem with it.
MOUETTE03
MOUETTE03‱7d ago
How did you set up the new media? In every application? And have you tried to completely uninstall pihole?
Whar
WharOP‱7d ago
I mounted the disk, recreated runtipis original directories and gave permissions for 1000:1000. I think only Sonarr and qBittorrent are touching /media đŸ€” No, I haven't tried reinstalling PiHole, I was afraid I wouldn't be able to do it again (due to the errors), haha. What I was worried about was about the hardware/os combo, if maybe it wasn't powerful enough or if I should move to Ubuntu server instead. Do you think it's fine? I only had this installed for a couple of weeks so I'm relatively fine starting again from scratch since for now it's just a hobby and don't have anything valuable in it. Tonight I'll uninstall PiHole and check if it works and come back with the results.
MOUETTE03
MOUETTE03‱7d ago
I also use raspberryOS on RPI 5 8GB and no problem On host can you try this command and send the result ? : echo "=== Diagnostic Réseau RPi ===" && \ echo "DNS: $(nslookup registry-1.docker.io 8.8.8.8 2>/dev/null | grep -m1 Address echo 'KO')" && \ echo "Ping: $(ping -c1 8.8.8.8 | tail -1 echo 'KO')" && \ echo "Docker: $(docker --version 2>/dev/null | head -1 echo 'non installé')" && \ echo "Curl: $(curl -I https://registry-1.docker.io/v2/ 2>/dev/null | head -1 echo 'KO')"
Whar
WharOP‱6d ago
Hi! Sorry I didn't update before, but PiHole didn't want to be uninstalled, I got a similar error to the timeout one !! Now my Raspi is working directly with my router and you can check that the error persist, even trying to update an already existing app. You can see the error is not related to the migrated store since I tried with a different one too. The error log is attached. @Mouette03 the results for that command (with Pihole out of the way):
=== Diagnostic Réseau RPi ===
DNS: KO
Ping: rtt min/avg/max/mdev = 8.627/8.627/8.627/0.000 ms
Docker: Docker version 29.0.4, build 3247a5a
Curl:
=== Diagnostic Réseau RPi ===
DNS: KO
Ping: rtt min/avg/max/mdev = 8.627/8.627/8.627/0.000 ms
Docker: Docker version 29.0.4, build 3247a5a
Curl:
So, it seems DNS is the problem, right?
MOUETTE03
MOUETTE03‱6d ago
check with this command which DNS resolvers are registered " cat /etc/resolv.conf " but yes it seems that it is the DNS that is the problem
Whar
WharOP‱6d ago
Thank you for everything, this is the result:
# Generated by NetworkManager
nameserver 94.140.14.14
nameserver 94.140.15.15
nameserver 2a0c:5a80:0:2::1
# NOTE: the libc resolver may not support more than 3 nameservers.
# The nameservers listed below may not be recognized.
nameserver 2a0c:5a84:0:2::1
nameserver fe80::1%wlan0
# Generated by NetworkManager
nameserver 94.140.14.14
nameserver 94.140.15.15
nameserver 2a0c:5a80:0:2::1
# NOTE: the libc resolver may not support more than 3 nameservers.
# The nameservers listed below may not be recognized.
nameserver 2a0c:5a84:0:2::1
nameserver fe80::1%wlan0
Edit: you're going to hate me, but digging from my side I discovered I hadn't installed dnsutils, these are the actual results from before:
=== Diagnostic Réseau RPi ===
DNS: Address: 8.8.8.8#53
Ping: rtt min/avg/max/mdev = 21.238/21.238/21.238/0.000 ms
Docker: Docker version 29.0.4, build 3247a5a
Curl: HTTP/2 401
=== Diagnostic Réseau RPi ===
DNS: Address: 8.8.8.8#53
Ping: rtt min/avg/max/mdev = 21.238/21.238/21.238/0.000 ms
Docker: Docker version 29.0.4, build 3247a5a
Curl: HTTP/2 401
MOUETTE03
MOUETTE03‱6d ago
Does it work now ? Have you checked the DNS resolvers in your router ? 94.140.14.14 It seems strange to me Adguard is installed on runtipi because this address 94.140.14.14 corresponds to it. And if it is KO the resolution will not work
Whar
WharOP‱6d ago
They're the public Adguard DNS, I was using them on my router before I was using Pihole, so I installed all the containers/app that are working now with them: https://adguard-dns.io/en/public-dns.html I'm going to attach the iptables and nftables because I see a lot of things and I'm not sure if the rules are fine or not.
Connect to public AdGuard DNS server
AdGuard DNS — ad-blocking DNS server
Create your ad-blocking DNS server that will protect your personal data, prevent tracking and allow you to control access to specific content on the Internet.
Whar
WharOP‱6d ago
Is not installed, they are used on my router directly now that I unistalled pihole, you were faster than my reply, haha. Edit: for better context. - I was using the public Adguard DNS servers before buying the Raspi and using Runtipi. - I install a bunch of apps with those DNS servers with Runtipi on my Raspberry. - I configure Pihole and switch my router to use the Raspi as DNS server. - Errors start happening, not sure if I installed any app during this time. Maybe I did. - I uninstall Pihole and configure my router back to the public Adguard DNS.
MOUETTE03
MOUETTE03‱6d ago
Try those from google on your router and delete dns ipv6 if it doesn't work. We'll see if it comes from the router's dns resolvers.
Whar
WharOP‱6d ago
Do you mean delete IPv6 from the Raspi? My ISP router doesn't have config options for IPv6. And, if that's the case, how do I do it?
MOUETTE03
MOUETTE03‱6d ago
Are you French ?
Whar
WharOP‱6d ago
No, I'm Spanish
MOUETTE03
MOUETTE03‱6d ago
Just try on the router to put solve google sometimes ipv6 configurable also on router
Whar
WharOP‱6d ago
Ok, I'll come back later with the results (I'm working from home and I don't want to break something đŸ€Ł ) Thank you again!
MOUETTE03
MOUETTE03‱6d ago
Then restart rpi and verify that modification has been made with "cat /etc/resolv.conf"
Whar
WharOP‱6d ago
Hasn't changed, I guess I'll have to restart the router. I'll try on my lunch break.
MOUETTE03
MOUETTE03‱6d ago
cat /etc/resolv.conf Will tell you if change applied
Whar
WharOP‱6d ago
Changed DNS to Google, restarted both the Raspberry and the router but still gettin errors:
=== Diagnostic Réseau RPi ===
DNS: Address: 8.8.8.8#53
Ping: rtt min/avg/max/mdev = 213.226/213.226/213.226/0.000 ms
Docker: Docker version 29.0.4, build 3247a5a
Curl: HTTP/2 401
=== Diagnostic Réseau RPi ===
DNS: Address: 8.8.8.8#53
Ping: rtt min/avg/max/mdev = 213.226/213.226/213.226/0.000 ms
Docker: Docker version 29.0.4, build 3247a5a
Curl: HTTP/2 401
# Generated by NetworkManager
nameserver 8.8.8.8
nameserver 8.8.4.4
nameserver fe80::1%wlan0
# NOTE: the libc resolver may not support more than 3 nameservers.
# The nameservers listed below may not be recognized.
nameserver 2a0c:5a80:0:2::1
nameserver 2a0c:5a84:0:2::1
# Generated by NetworkManager
nameserver 8.8.8.8
nameserver 8.8.4.4
nameserver fe80::1%wlan0
# NOTE: the libc resolver may not support more than 3 nameservers.
# The nameservers listed below may not be recognized.
nameserver 2a0c:5a80:0:2::1
nameserver 2a0c:5a84:0:2::1
2025-12-01T15:21:03.544Z - error > The queue timed out while processing the request. Try restarting your instance before retrying.
2025-12-01T15:21:03.545Z - error > Failed to install app glances:migrated: RPC response timed out
2025-12-01T15:23:43.275Z - error > The queue timed out while processing the request. Try restarting your instance before retrying.
2025-12-01T15:23:43.277Z - error > Failed to start app jellyseerr:migrated: RPC response timed out
2025-12-01T15:21:03.544Z - error > The queue timed out while processing the request. Try restarting your instance before retrying.
2025-12-01T15:21:03.545Z - error > Failed to install app glances:migrated: RPC response timed out
2025-12-01T15:23:43.275Z - error > The queue timed out while processing the request. Try restarting your instance before retrying.
2025-12-01T15:23:43.277Z - error > Failed to start app jellyseerr:migrated: RPC response timed out
As you see, one app fails to install and the other fails to start (maybe wasn't installed properly)
MOUETTE03
MOUETTE03‱5d ago
Edit this file "sudo nano /etc/docker/daemon.json" if it exists otherwise create it to stop ipv6 on docker and add this content «  { "Ipv6": false }  « And restart docker or the system
Whar
WharOP‱5d ago
The file didn't exist, I created it with that content and I got this after starting runtipi again:
sudo ./runtipi-cli start
✓ User permissions are ok
✓ Copied system files
✓ Generated .env file
✓ File permissions ok
✓ Images pulled
✓ Existing containers stopped
✗ Failed to start containers

Debug: Container runtipi-queue Creating
Container runtipi-db Creating
Container runtipi-queue Created
Container runtipi-db Created
Container runtipi Creating
Container runtipi Created
Container runtipi-reverse-proxy Creating
Container runtipi-reverse-proxy Created
Container runtipi-queue Starting
Container runtipi-db Starting
Container runtipi-queue Started
Container runtipi-db Started
Container runtipi-db Waiting
Container runtipi-db Healthy
Container runtipi Starting
Container runtipi Started
Container runtipi Waiting
Container runtipi Error
dependency failed to start: container runtipi is unhealthy
sudo ./runtipi-cli start
✓ User permissions are ok
✓ Copied system files
✓ Generated .env file
✓ File permissions ok
✓ Images pulled
✓ Existing containers stopped
✗ Failed to start containers

Debug: Container runtipi-queue Creating
Container runtipi-db Creating
Container runtipi-queue Created
Container runtipi-db Created
Container runtipi Creating
Container runtipi Created
Container runtipi-reverse-proxy Creating
Container runtipi-reverse-proxy Created
Container runtipi-queue Starting
Container runtipi-db Starting
Container runtipi-queue Started
Container runtipi-db Started
Container runtipi-db Waiting
Container runtipi-db Healthy
Container runtipi Starting
Container runtipi Started
Container runtipi Waiting
Container runtipi Error
dependency failed to start: container runtipi is unhealthy
I guess it's better to start from the beginning and say bye to this first dip in self-hosting? Edit: it's alive again! Going to check if turning IPv6 off worked.
MOUETTE03
MOUETTE03‱5d ago
Did it work ? 🙏
Whar
WharOP‱5d ago
When it does, yes, but it keeps dying sadly and I'm not sure why 😭 So IPv6 was definitely part of the issue but I probably broke something in the way.
MOUETTE03
MOUETTE03‱5d ago
Have you tried reinstalling runtipi? sudo ./runtipi-cli update latest
Whar
WharOP‱4d ago
Hi, yes, I did! Now it's not unhealthy but I still can't install anything. I thought I had removed the app stores or something, because I couldn't use the search, it returned an empty list. I deleted them manually and added them again (included migrated, the default one), even if they were there, and after a few restarts the search worked again. It turned out I didn't remove the stores, Runtipi is doing it or something (?) and that's why nothing is getting installed (logs attached).
Whar
WharOP‱4d ago
And, thank you again, you've been so nice!
MOUETTE03
MOUETTE03‱4d ago
Hmmm. Last attempt that I can suggest to you, after that will exceed my skills. Delete the previously created daemon.json file then deactivate ipv6 directly on the hote To deactivate on hote « sudo nano /etc/sysctl.conf » And add at the end «  net.ipv6.conf.all.disable_ipv6 = 1 net.ipv6.conf.default.disable_ipv6 = 1 net.ipv6.conf.lo.disable_ipv6 = 1 « To apply « sudo sysctl -p » And «  cat /proc/sys/net/ipv6/conf/all/disable_ipv6 «  Must answer 1 if ipv6 is deactivated
Whar
WharOP‱4d ago
@MOUETTE03 Thanks for your help, finally I decided to start clean again and reinstall both Raspi OS and Runtipi from zero, I probably did something that I shouldn't have, not sure.

Did you find this page helpful?