Grafana kept refreshing by itself, with some error message appears and disappears quickly. about teslamate HOT 28 CLOSED

Want to say, that I have the same problem. I just installed TeslaMate in a LXC Container setup with the following script: https://tteck.github.io/Proxmox/#docker-lxc. Created a docker-compose script file with the content from the installation site. Logged into TeslaMate with the API Token and Refresh Token. Then logged into Grafana and changed the default PW. After logging in to Grafana, I get the following error in Firefox:

My network tab gets spammed with these rotate network calls (if I have the network tools open for more than 30 seconds, Firefox freezes to death), that have an empty JSON as a result:

And got message like this one in my logs:

grafana-1    | logger=context userId=0 orgId=0 uname= t=2024-06-26T19:40:49.486018485Z level=error msg=Unauthorized error="user token not found" remote_addr=10.3.105.106 traceID= 

If you need additional info, I am ready to help.

Edit: Forgot to include the script link

from teslamate.

Ok, I fixed now the issue. uBlock Origin was the culprit. I disabled it last time, but I created the docker container this time on another IP and forgot to disable uBlock Origin on that IP.

from teslamate.

Glad both of you solved your issues. As assumed initially, proxy issue and ad blocker issue.

from teslamate.

please fix my issue.

That's up to you. We can only support on this.

Please share your docker-compose.yml without secrets. Also your system spec, proxy servers, ad blockers etc.

Good news, my grafana backs to normal, no error messages. The bad news is that I don’t know how it recovers. I didn’t do anything, it recovered by itself. I will continue using it for a while to see if that error messages appear again. Thanks!

from teslamate.

Looks like there is authentication errors in the logs. Have you changed anything in your Docker Compose?

Were you using default values? Are there extra spaces by chance?

from teslamate.

Looks like there is authentication errors in the logs. Have you changed anything in your Docker Compose?

Were you using default values? Are there extra spaces by chance?

I removed a proxy setting on docker compose, nothing else except that.
I’m using default values except password. There are no extra spaces in docker compose files. I’m sure all my settings are correct because I’ve running Teslamate for a year and it works fine until recently.
By the way, I think this issue comes after a power loss on my raspberry pi, are these things related?

from teslamate.

Looks like there is authentication errors in the logs. Have you changed anything in your Docker Compose?

Were you using default values? Are there extra spaces by chance?

I also reinstalled the teslamate, include manually remove all related containers, volumes, images. After loading my backup files, this issue happens again.

from teslamate.

I had the same problem. My cloud server did not have a power outage. It started after Tesla updated its API a while ago and has been there ever since.
I tried to deploy it on an external server, and the problem reappeared after I opened the grafana panel, regardless of whether I restored the data or not, and even used new Tesla API tokens.
By the way, for ease of management, I used "Advanced installation with Traefik, Let's Encrypt & HTTP Basic Auth" for deployment.

我出现了同样的问题，我的云服务器并没有出现断电的情况，而是在前段时间Tesla更新了API之后就出现且一直存在的。
我尝试在外网服务器部署，不论恢复数据与否，甚至使用了全新Tesla API tokens，的该问题在打开grafana面板之后再次出现。
对了，我为了方便管理，使用的是“Advanced installation with Traefik, Let's Encrypt & HTTP Basic Auth”部署。

from teslamate.

I removed a proxy setting on docker compose, nothing else except that.

What did that proxy server do? If you put it back, do your errors go away?

By the way, I think this issue comes after a power loss on my raspberry pi, are these things related?

Only thing I could think of from that would be a corrupted SD card.

from teslamate.

I ajsusme a adblocker issue

from teslamate.

I ajsusme a adblocker issue

No, I didn’t install anything about adblocker on my teslamate server and my phone. I use different phones and browsers to access grafana but it ends up same.

from teslamate.

I removed a proxy setting on docker compose, nothing else except that.

What did that proxy server do? If you put it back, do your errors go away?

By the way, I think this issue comes after a power loss on my raspberry pi, are these things related?

Only thing I could think of from that would be a corrupted SD card.

I used to running Clash on my raspberry pi. That proxy is about Clash. I put it back but this issue still exists.

from teslamate.

So it's not an ad blocker but a proxy issue.

from teslamate.

from teslamate.

Which browser are you using?

from teslamate.

from teslamate.

OK.

Obviously, it is an authentication issue. Please double-check your docker-compose.yml and compare it to https://docs.teslamate.org/docs/installation/docker/. Please check if you use correct user and password combinations.

from teslamate.

from teslamate.

Then logged into Grafana and changed the default PW

Only change password in docker-compose.yml

from teslamate.

Ok, I reset Grafana with bringing down the service docker compose rm -sv grafana. Then deleted the volume: docker volume rm root_teslamate-grafana-data and brought the service up docker compose up -d grafana. Now Grafana wants me to change the PW again, but this time I skipped it. Now I am still having the same problems, meaning changing the password was not the problem.

I forgot to include that the above line in the log is followed with another one:

grafana-1    | logger=authn.service t=2024-06-27T10:43:52.136529678Z level=warn msg="Failed to authenticate request" client=auth.client.session error="user token not found"
grafana-1    | logger=context userId=0 orgId=0 uname= t=2024-06-27T10:43:52.136544668Z level=warn msg=Unauthorized error="user token not found" remote_addr=10.3.105.106 traceID=

from teslamate.

Now Grafana wants me to change the PW again

As teslamate-grafana does not have this behavior, we are not able to support on this. Only https://docs.teslamate.org/docs/installation/docker/ is supported. (you use an ip without any port for grafana for example)

As a hint: you need to delete your cookies when messing with your grafana, but this is not a teslamate issue

from teslamate.

Ok, I just throw the LXC Container away and made a fresh start. The only thing this time, I changed, is that I went into the TeslaMate settings and inserted the Grafana Dashboard URL. Then I navigated through the Teslamate link to Grafana, and now I see at least a dashboard. But everywhere is standing "No Data" and it still is spamming rotate network calls. The thing with "No data" is probably because I reset everything, and it needs to collect data, but I still sometimes get a "NetworkError couldn't fetch resources" error

Edit:

Now Grafana wants me to change the PW again

Should have been the right behavior if I deleted the volume of Grafana, or not?. Or does it store the password in Postgres? Also I forgot to say, that I followed this before deleting the container, so that could also be the reason. Sorry for forgetting it.

from teslamate.

I found the reason, it's a proxy problem. The correct way is: first deploy using ports 80 and 443, and after obtaining the complete certificate, change to other ports again, such as 8080/8443 ports and redeploy once. However, the problem with this is: when the SSL certificate expires, you need to manually modify the certificate content, and you may also need to redeploy.
Also, when using the reverse proxy to port 8443, the previous situation will still occur.

我找到原因了，这是一个代理问题。正确的做法是：首先使用80和443端口部署，获取到完整的证书后，再次更换为其他端口，譬如8080/8443端口重新部署一次即可用。但是这样做存在的问题是：当SSL证书过期后需要手动去修改证书内容，也有可能需要重新部署。
还有，当使用反向代理到8443端口后，还是会出现之前的情况。

from teslamate.

Glad both of you solved your issues. As assumed initially, proxy issue and ad blocker issue.

Hey, that’s not me. I didn’t use proxy and adblocker, please fix my issue.

from teslamate.

Glad both of you solved your issues. As assumed initially, proxy issue and ad blocker issue.

Hey, that’s not me. I didn’t use proxy and adblocker, please fix my issue.

Sorry, two others hijacked your issue

from teslamate.

please fix my issue.

That's up to you. We can only support on this.

Please share your docker-compose.yml without secrets. Also your system spec, proxy servers, ad blockers etc.

from teslamate.

please fix my issue.

That's up to you. We can only support on this.

Please share your docker-compose.yml without secrets. Also your system spec, proxy servers, ad blockers etc.

This is my docker-compose.yml file:

services:
teslamate:
image: teslamate/teslamate:latest
restart: always
environment:
- ENCRYPTION_KEY=MYKEY #replace with a secure key to encrypt your Tesla API tokens
- DATABASE_USER=teslamate
- DATABASE_PASS=MYPASSWORD #insert your secure database password!
- DATABASE_NAME=teslamate
- DATABASE_HOST=database
- MQTT_HOST=mosquitto
ports:
- 4000:4000
volumes:
- ./import:/opt/app/import
cap_drop:
- all

database:
image: postgres:16
restart: always
environment:
- POSTGRES_USER=teslamate
- POSTGRES_PASSWORD=MYPASSWORD #insert your secure database password!
- POSTGRES_DB=teslamate
volumes:
- teslamate-db:/var/lib/postgresql/data

grafana:
image: teslamate/grafana:latest
restart: always
environment:
- DATABASE_USER=teslamate
- DATABASE_PASS=MYPASSWORD #insert your secure database password!
- DATABASE_NAME=teslamate
- DATABASE_HOST=database
ports:
- 3000:3000

from teslamate.

please fix my issue.

That's up to you. We can only support on this.
Please share your docker-compose.yml without secrets. Also your system spec, proxy servers, ad blockers etc.

Good news, my grafana backs to normal, no error messages. The bad news is that I don’t know how it recovers. I didn’t do anything, it recovered by itself. I will continue using it for a while to see if that error messages appear again. Thanks!

please fix my issue.

That's up to you. We can only support on this.

Please share your docker-compose.yml without secrets. Also your system spec, proxy servers, ad blockers etc.

I’m using docker running on a raspberry pi5 to run teslamate. I have no proxy servers and no adblockers. The browsers I use are safari and Chrome on iPhone and Mac, the two browsers have no extra plugins and all using default settings.

from teslamate.