Failed to fetch - Restored /backed up - MacOS Docker -> Raspberry Pi

[bolyki01]

Hi

I have migrated from a MacOS based docker (it's horrible to use) to a Pi (debian) based system.

I summed up what I have done and submitting some logs.

The issue:

Database "works" and keeps writing, I can query from terminal and I can see changes. However the webUI gives the "failed to fetch" on every single page and then crashes.

If I view the state of the car, it shows and also can see the state of charge.

Using Teslamate v2.1.0 with Postgres 17.5. :4000 UI works, data counts OK (drives=1232, positions=4445809, charges=87539, geofences=19038). :3000 loads but dashboards show "Failed to fetch" / N/A.

Grafana data source configured as host=database:5432, db=teslamate, user=teslamate, pass=XX, SSL disable. Save & Test succeeds. Browser console: no specific errors, just failed fetch on panels.

What causes this? How to fix?

Commands Used for Restore

These I used AFTER I tried the normal restore way and it didn't work. So I tried to google and figure out other ways, but stuck as is.

docker-compose stop teslamate grafana
docker-compose exec database psql -U teslamate -d postgres -c "DROP DATABASE teslamate WITH (FORCE);"
docker-compose exec database psql -U teslamate -d postgres -c "CREATE DATABASE teslamate;"
docker-compose exec -T database pg_restore --clean --if-exists --no-owner --disable-triggers -U teslamate -d teslamate < backup.dump
docker-compose start teslamate grafana
docker-compose exec database psql -U teslamate -d teslamate -c "\dt"
docker-compose exec database psql -U teslamate -d teslamate -c "SELECT count() FROM pg_tables WHERE schemaname = 'public';"
docker-compose exec database psql -U teslamate -d teslamate -c "SELECT count() FROM drives;"
docker-compose exec database psql -U teslamate -d teslamate -c "SELECT count() FROM positions;"
docker-compose exec database psql -U teslamate -d teslamate -c "SELECT count() FROM charges;"
docker-compose exec database psql -U teslamate -d teslamate -c "SELECT count(*) FROM geofences;"
docker-compose logs teslamate | tail -n 20
docker-compose logs database | tail -n 20
docker-compose logs grafana | tail -n 20

Info for Community

• Setup: Teslamate v2.1.0, PostgreSQL 17.5, Grafana latest from teslamate/grafana:latest, Docker Compose.
• docker-compose.yml:

services:
  teslamate:
    image: teslamate/teslamate:latest
    restart: always
    environment:
      - ENCRYPTION_KEY=XX
      - DATABASE_USER=teslamate
      - DATABASE_PASS=XX
      - DATABASE_NAME=teslamate
      - DATABASE_HOST=database
      - MQTT_HOST=mosquitto
    ports:
      - 4000:4000
    volumes:
      - ./import:/opt/app/import
    cap_drop:
      - all

  database:
    image: postgres:17
    restart: always
    environment:
      - POSTGRES_USER=teslamate
      - POSTGRES_PASSWORD=XX
      - POSTGRES_DB=teslamate
    volumes:
      - teslamate-db:/var/lib/postgresql/data

  grafana:
    image: teslamate/grafana:latest
    restart: always
    environment:
      - DATABASE_USER=teslamate
      - DATABASE_PASS=XXX
      - DATABASE_NAME=teslamate
      - DATABASE_HOST=database
    ports:
      - 3000:3000
    volumes:
      - teslamate-grafana-data:/var/lib/grafana

  mosquitto:
    image: eclipse-mosquitto:2
    restart: always
    command: mosquitto -c /mosquitto-no-auth.conf
    volumes:
      - mosquitto-conf:/mosquitto/config
      - mosquitto-data:/mosquitto/data

volumes:
  teslamate-db:
  teslamate-grafana-data:
  mosquitto-conf:
  mosquitto-data:


**Logs (teslamate tail -n 20):**

teslamate_1  | 2025-08-06 16:42:10.074 car_id=1 [info] Start / :offline
teslamate_1  | 2025-08-06 16:42:10.356 [info] MQTT connection has been established
teslamate_1  | 2025-08-06 16:43:56.554 [notice] SIGTERM received - shutting down
teslamate_1  | 
teslamate_1  | 2025-08-06 16:44:49.730 [info] Migrations already up
teslamate_1  | 2025-08-06 16:44:51.562 [info] System Info: Erlang/OTP 26 (jit)
teslamate_1  | 2025-08-06 16:44:51.562 [info] Version: 2.1.0
teslamate_1  | PostgreSQL version 17.5 is compatible (17.x series).
teslamate_1  | 2025-08-06 16:44:51.991 [info] POST https://auth.tesla.com/oauth2/v3/token -> 200 (366.195 ms)
teslamate_1  | 2025-08-06 16:44:51.992 [info] Refreshed api tokens
teslamate_1  | 2025-08-06 16:44:51.995 [info] Scheduling token refresh in 6 h
teslamate_1  | 2025-08-06 16:44:52.001 [info] Running TeslaMateWeb.Endpoint with cowboy 2.13.0 at :::4000 (http)
teslamate_1  | 2025-08-06 16:44:52.001 [info] Access TeslaMateWeb.Endpoint at http://localhost
teslamate_1  | 2025-08-06 16:44:52.098 [info] Starting logger for 'Athena'
teslamate_1  | 2025-08-06 16:44:52.374 car_id=1 [info] Start / :offline
teslamate_1  | 2025-08-06 16:44:52.656 [info] MQTT connection has been established

**- Logs (database tail -n 20):**

database_1   | 2025-08-06 16:44:49.756 UTC [288] ERROR:  count(*) must be used to call a parameterless aggregate function at character 8
database_1   | 2025-08-06 16:44:49.756 UTC [288] STATEMENT:  SELECT count() FROM pg_tables WHERE schemaname = 'public';
database_1   | 2025-08-06 16:44:50.264 UTC [295] ERROR:  count(*) must be used to call a parameterless aggregate function at character 8
database_1   | 2025-08-06 16:44:50.264 UTC [295] STATEMENT:  SELECT count() FROM drives;
database_1   | 2025-08-06 16:44:50.764 UTC [302] ERROR:  count(*) must be used to call a parameterless aggregate function at character 8
database_1   | 2025-08-06 16:44:50.764 UTC [302] STATEMENT:  SELECT count() FROM positions;
database_1   | 2025-08-06 16:44:51.268 UTC [309] LOG:  skipping vacuum of "positions" --- lock not available
database_1   | 2025-08-06 16:45:37.470 UTC [27] LOG:  checkpoint complete: wrote 3262 buffers (19.9%); 0 WAL file(s) added, 0 removed, 33 recycled; write=173.748 s, sync=0.030 s, total=174.581 s; sync files=4, longest=0.030 s, average=0.008 s; distance=535752 kB, estimate=535752 kB; lsn=0/E15D2898, redo lsn=0/D742DD78
database_1   | 2025-08-06 16:45:37.470 UTC [27] LOG:  checkpoint starting: immediate force wait
database_1   | 2025-08-06 16:45:37.825 UTC [27] LOG:  checkpoint complete: wrote 2 buffers (0.0%); 0 WAL file(s) added, 0 removed, 10 recycled; write=0.022 s, sync=0.036 s, total=0.355 s; sync files=2, longest=0.031 s, average=0.018 s; distance=165522 kB, estimate=498729 kB; lsn=0/E15D2968, redo lsn=0/E15D2910


**Logs (grafana tail -n 20):**

grafana_1    | logger=provisioning.dashboard t=2025-08-06T16:44:49.674476831Z level=info msg="starting to provision dashboards"
grafana_1    | logger=grafana-apiserver t=2025-08-06T16:44:52.648340663Z level=info msg="Adding GroupVersion featuretoggle.grafana.app v0alpha1 to ResourceManager"
grafana_1    | logger=grafana-apiserver t=2025-08-06T16:44:52.650287757Z level=info msg="Adding GroupVersion folder.grafana.app v1beta1 to ResourceManager"
grafana_1    | logger=grafana-apiserver t=2025-08-06T16:44:52.656776686Z level=info msg="Adding GroupVersion iam.grafana.app v0alpha1 to ResourceManager"
grafana_1    | logger=grafana-apiserver t=2025-08-06T16:44:52.658027483Z level=info msg="Adding GroupVersion userstorage.grafana.app v0alpha1 to ResourceManager"
grafana_1    | logger=grafana-apiserver t=2025-08-06T16:44:52.659263409Z level=info msg="Adding GroupVersion playlist.grafana.app v0alpha1 to ResourceManager"
grafana_1    | logger=grafana-apiserver t=2025-08-06T16:44:52.66471506Z level=info msg="Adding GroupVersion dashboard.grafana.app v1beta1 to ResourceManager"
grafana_1    | logger=grafana-apiserver t=2025-08-06T16:44:52.665820079Z level=info msg="Adding GroupVersion dashboard.grafana.app v0alpha1 to ResourceManager"
grafana_1    | logger=grafana-apiserver t=2025-08-06T16:44:52.666810061Z level=info msg="Adding GroupVersion dashboard.grafana.app v2alpha1 to ResourceManager"
grafana_1    | logger=app-registry t=2025-08-06T16:44:52.740797781Z level=info msg="app registry initialized"
grafana_1    | logger=provisioning.dashboard t=2025-08-06T16:44:53.182886523Z level=info msg="finished to provision dashboards"
grafana_1    | logger=context userId=1 orgId=1 uname=admin t=2025-08-06T16:44:59.714615163Z level=info msg="Request Completed" method=GET path=/api/live/ws status=-1 remote_addr=192.168.8.2 time_ms=8 duration=8.604949ms size=0 referer= handler=/api/live/ws status_source=server
grafana_1    | logger=live t=2025-08-06T16:45:41.583726392Z level=info msg="Initialized channel handler" channel=grafana/dashboard/uid/be2m9kga7b8qoc address=grafana/dashboard/uid/be2m9kga7b8qoc
grafana_1    | logger=context userId=1 orgId=1 uname=admin t=2025-08-06T16:45:43.105978375Z level=info msg="Request Completed" method=GET path=/api/live/ws status=-1 remote_addr=192.168.8.2 time_ms=3 duration=3.224408ms size=0 referer= handler=/api/live/ws status_source=server
grafana_1    | logger=infra.usagestats t=2025-08-06T16:46:47.556932345Z level=info msg="Usage stats are ready to report"
grafana_1    | logger=context userId=1 orgId=1 uname=admin t=2025-08-06T16:47:23.319455328Z level=info msg="Request Completed" method=GET path=/api/live/ws status=-1 remote_addr=192.168.8.2 time_ms=3 duration=3.224408ms size=0 referer= handler=/api/live/ws status_source=server
grafana_1    | logger=provisioning.alerting t=2025-08-06T16:47:24.319455328Z level=info msg="starting to provision alerting"
grafana_1    | logger=provisioning.alerting t=2025-08-06T16:47:24.319483865Z level=info msg="finished to provision alerting"
grafana_1    | logger=provisioning.dashboard t=2025-08-06T16:47:24.319483865Z level=info msg="starting to provision dashboards"
grafana_1    | logger=provisioning.dashboard t=2025-08-06T16:47:24.319483865Z level=info msg="finished to provision dashboards"

[brianmay]

It appears teslamate is working fine, your problem is getting the data out using grafana.

Sorry, based on the information provided, I have no idea why grafana is not working.

[bolyki01]

Thanks, me neither hence I came here as last resort :D

[JakobLichterfeld]

docker-compose

this is a deprecated command since ages, you need to use docker compose (not docker-compose see info in docs as well) and exactly follow https://docs.teslamate.org/docs/maintenance/backup_restore

[bolyki01]

@brianmay @JakobLichterfeld

Guess what was the issue!

Patience.

I didn't wait long enough for the indexing or whatever it does after a restore. After a few hours it works fine.