john_smith

Hey @brent3000 as i understand it, this is the process essentially from start to finish on unraid:

# stop teslamate + teslamate-grafana + teslamate-abrp (if you use it) # on postgres v15 container -> console pg_dump -U DBUSERNAME -h IPADDRESS -p 5432 -f /var/lib/postgresql/data/teslamate.bck postgres # this creates the file /mnt/user/appdata/postgres15 # copy the backup file to /mnt/user/appdata/postgres17 # stop postgres v15 container # start postgres v17 container # start adminer -> via webgui create database there named "teslamate" # start teslamate container to initialize database # stop teslamate container # on postgres v17 container -> console: # Drop existing data and reinitialize, to do this: psql -U DBUSERNAME -d teslamate DROP SCHEMA public CASCADE CREATE SCHEMA public CREATE EXTENSION cube WITH SCHEMA public CREATE EXTENSION earthdistance WITH SCHEMA public # then restore your previously backed up data: psql -U DBUSERNAME -h IPADDRESS -p 5432 -d teslamate < /var/lib/postgresql/data/teslamate.bck # start teslamate, verify it works as expected # finally, go to /mnt/user/appdata/teslamate/grafana and delete all folders/contents # since deleting appdata/grafana contents will delete previously configured password, # reconfigure teslamate-grafana user/pass (Default user/pass is admin/admin) # start teslamate-grafana, verify it works as expected # start teslamate-abrp (if you use it) 
FYI i'm still not sure why I had to delete appdata/grafana to get it to work correctly, but it worked for me.

Here's an additional note from the CA store on permissions for teslamate-grafana in case this happens for you, I ran this preemptively just in case but i don't think it should apply: