Teslamate "Bad Gateway" #2820
Replies: 6 comments 3 replies
-
Can you share your docker-compose.yml file? (don't forget to delete your passwords) |
Beta Was this translation helpful? Give feedback.
-
I'd like to bring this back into the spot light. I have received three separate "Bad Gateway" instances after attempting to logging into Teslamate's web GUI from a public and secured web address. I experienced these Bad Gateway errors consistently with Teslamate 1.27.1. From this last Bad Gateway instance, about about a day or two so ago prior to receiving the message, the web GUI was very slow and almost non-responsive. The web GUI returned back to being responsive later in the day. IIRC, I had Teslamate 1.25.2 prior to 1.27.1 and didn't experience any such Bad Gateway errors. I shutdown Teslamate and I tried to retrieve logs for both 'Teslamate' and 'database' services from docker-compose, this is what I get from both:
That's it. I'm not sure what caused the logs to get cut off and only be that short. --Update: looks like if I shutdown Teslamate prior to pulling the logs, the logs get wiped out. So I should've pulled the logs before shutting it down to restart it up later.-- I was hoping that the logs would be helpful in searching for the reason why I'm receiving Bad Gateway three times, the last two times within about a couple of weeks of each other. Anything to look into while I await for the next round of Bad Gateway? I see that docker-compose.yml was requested, but nothing came to light about it. The next time the Bad Gateway comes around, I'll try to pull the logs to see what's going on. So far, the Bad Gateway errors happen during/after charging my car (usually when I check on Teslamate). I'm not sure if there's any correlation with that though. I went looking with Google how to capture previous logs, I came across how to find the current logging, but one must set up rotating logs in order to see pervious logs. |
Beta Was this translation helpful? Give feedback.
-
FYI, after 2 weeks, I'm getting "Bad Gateway" again. I'm trying to review the logs, but I'm currently running into issues. When I run the command: Update: holy crap that was some learning experience with Linux. Good thing I set up logrotate so that it could save the logs in the event of a crash. It took me a while to get the most recent log file (*.log.2.gz) due to permissions (I'm mainly a Windows user, but thank goodness for Google searching). If anybody went through setting up the rotating logs posted above (especially in Google Cloud/Compute Engine/Virtual Machine), you will need to set the file ownership to yourself (command: chown user:group filename; be in sudo su first) from root:root (shows up in Log file brief analysis:
Here's the log file:
|
Beta Was this translation helpful? Give feedback.
-
I am having an issue (bad gateway) after upgrading from 1.27.1 to 1.27.2 : Here is my docker-compose.yml file: version: "3" services: database: grafana:
mosquitto: proxy: volumes: |
Beta Was this translation helpful? Give feedback.
-
I'm still facing this issue with version 1.27.3 I restart the GCP VM Instance also every day, and then it works. Any ideas how to resolve this issue? Thanks in advance, Tom |
Beta Was this translation helpful? Give feedback.
-
i got the same problem, but i just found if visit the site with the devtools open (chrome browser). and never see this gateway error. 😂 |
Beta Was this translation helpful? Give feedback.
-
Is there an existing issue for this?
What happened?
After I log in into teslamate, it shows "Bad Gateway"
Expected Behavior
No response
Steps To Reproduce
No response
Relevant log output
Screenshots
No response
Additional data
No response
Type of installation
Docker
Version
v1.27.0
Beta Was this translation helpful? Give feedback.
All reactions