R
Runtipi•2w ago
o1

Long load time for the tipi dashboard

Hey looks like these two requests take a few seconds * latest version of tipi * raspberrypi 5 (8gb)
No description
8 Replies
Nicolas
Nicolas•2w ago
Probably your server was not ready to respond Does it happen when reloading the page aswell?
o1
o1OP•2w ago
yeah the server is up for at least a day ok, something interesting.. I checked the error.log and see 2 errors every time I refresh the dashboard backend: 2025-01-14T20:12:13.291Z - error > TypeError: fetch failed backend: 2025-01-14T20:12:18.414Z - error > TypeError: fetch failed Unfortunately, I don't have the stacktrace to share
o1
o1OP•2w ago
a bit more debugging.. the request of getting the user context returns 
{
    "version": {
        "current": "v3.8.1",
        "latest": "v3.8.1",
        "body": ""
    },
    "isLoggedIn": true,
    "isConfigured": true,
    "isGuestDashboardEnabled": false,
    "allowAutoThemes": true,
    "allowErrorMonitoring": false
}
{
    "version": {
        "current": "v3.8.1",
        "latest": "v3.8.1",
        "body": ""
    },
    "isLoggedIn": true,
    "isConfigured": true,
    "isGuestDashboardEnabled": false,
    "allowAutoThemes": true,
    "allowErrorMonitoring": false
}
which looks like this case. the screenshot may shed light on the issue. not sure if it's because of my setup (I have a pi-hole as the dns)
No description
Nicolas
Nicolas•2w ago
Okay, it fails to fetch GitHub and the latest version can you ping the api.github.com from your server?
o1
o1OP•2w ago
from the raspberrypi I can, but it fails inside the runtipi container
Nicolas
Nicolas•2w ago
Restart: ./runtipi-cli restart
o1
o1OP•2w ago
I'm not sure how or when it started happening.. but other containers could not query pi-hole for dns records. I followed the first answer here and manually updated the pihole docker-compose.yml file. now it works
Stack Overflow
docker-compose internal DNS server 127.0.0.11 connection refused
Suddenly when I deployed some new containers with docker-compose the internal hostname resolution didn't work. When I tried to ping one container from the other using the service name from the docker-
Nicolas
Nicolas•2w ago
Nice! I will solve the problem on our side by fetching in the background So it will not slow down the page load

Did you find this page helpful?