New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Teslamate not running on Synology DS713+ #765
Comments
Which version of Docker do you have? |
Docker version 18.09.8, build bfed4f5
|
It could be another broken version of the Docker package. What is the output of the following two commands after starting the containers and waiting a while?
Even though it is a different problem, you could also try to downgrade Docker (see #108 (comment)). |
I am on the same version on Synology and this is working OK. From what I could gather from your video the only difference I caught was the explicit IP but it was too quick so I might be wrong. Here is my docker compose file if it helps.
|
Hi @dyxyl ,
The second one
|
I've also tried downgrading the docker version previously, no luck. |
The config looks good, but Some more commands to try (5433 is not a typo):
|
@dyxyl
|
FWIW, the 5 second delay is caused by the -w 5 argument so that is expected. The timeout for port 5433 strongly suggests a firewall problem that is blocking all communication between docker containers (it should have given "Connection refused"). The firewall is controlled by the iptables rules but none of the docker-specific rules are referenced in the FORWARD rule, so that would explain why it doesn't work. Interestingly, the packet count for some of the docker-specific rules is non-zero, so it looks like they were referenced for a short time in the past. Is this the standard firewall config? Can you turn off the firewall temporarily (if that is safe) to see if that fixes it? |
Hi, @dyxyl |
I tried uninstalling the docker package and starting over and now get different logs for Teslamate :
I looks like it did manage to connect to the database and run some queries (or am I misreading this ?) |
Yes, it apparently did manage to run the initial migrations, but initialization of teslamate itself failed. You could try setting DATABASE_POOL_SIZE: 20 in environment section of the teslamate containing in docker-compose.yml (where MQTT_HOST is set) but I don't know if that will help. |
Hi Dyxyl, |
Sorry, I'm running out of ideas. The only thing I can think of is to check the output of |
I'll just have to keep a raspberry pi running until I replace my Synology I guess... :) |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Not sure if this will be helpful for anyone but I had some issues installing Teslamate on the Synology NAS. It finally worked after:
I did use the API access token and refresh token to login - Did not work with my Tesla credentials due to recent changes in the authentication services from Tesla. |
Hi, I'm new to this party & am struggling to get it working with my Synology DS 216+. Any chance you can be explicit on how you moved the yml file to the hidden docker folder as that is the only thing I cannot replicate! Many thanks, |
Anyone? |
Same here |
Same issue here, but trying to set up on a TS-230 QNAP |
The only issue I had whas, if I remember correctly, process id already used thingy. I then moved the docker compose file to the hidden @docker file, then after "docker compose -up" I was able to login and use the application. If anybody needs me to check something on my current setup, I will be happy to help. Running on a Synology NAS since august 2021 and logged 13k km so far without any issues. |
Can you describe to a novice how to "move the docker compose file to the hidden @docker file"? Where do you execute the docker compose -up command within the Synology user interface (or in my case, the QNAP user interface within the ContainerStation app)? |
As a novice myself, just ls -a to find all folders and then move the yml file to the hidden folder. Learn how to move files here: https://opensource.com/article/19/8/moving-files-linux-depth |
I have the same issue. It appeared after rebooting my Synology NAS. No idea how to solve it unless i set up the whole TeslaMate again. |
Seems the firewall on the Synology NAS is causing the issues. I'm investigating the details. I disabled it and everything was working fine again. Then I enabled it - without doing any changes on my firewall-settings - and it keeps being functional. So weird. |
@edouardGT I am facing same issue and posted here, do you mind helping with it? TIA! |
Describe the bug
After following the below guide on a DS713+ (with 2GB RAM) :
#113
Grafana on port 3000 is working fine, but Teslamate on port 4000 is not responding.
It works fine on both Raspberry Pis on which i installed it.
Expected behavior
when typing http://MyIP:4000, I should get the page to enter my Tesla credentials
How to reproduce it (as minimally and precisely as possible):
Relevant entries from the logs
Database_1 Logs :
Teslamate_1 Logs :
2020-05-28 08:21:25 | stdout | waiting for postgres at database:5432 (1024sec)
2020-05-28 08:10:45 | stdout | waiting for postgres at database:5432 (512sec)
2020-05-28 08:04:22 | stdout | waiting for postgres at database:5432 (256sec)
2020-05-28 08:00:07 | stdout | waiting for postgres at database:5432 (128sec)
2020-05-28 07:56:56 | stdout | waiting for postgres at database:5432 (64sec)
2020-05-28 07:54:16 | stdout | waiting for postgres at database:5432 (32sec)
2020-05-28 07:51:53 | stdout | waiting for postgres at database:5432 (16sec)
2020-05-28 07:49:38 | stdout | waiting for postgres at database:5432 (8sec)
2020-05-28 07:47:27 | stdout | waiting for postgres at database:5432 (4sec)
2020-05-28 07:45:17 | stdout | waiting for postgres at database:5432 (2sec)
Screenshots
Screen recording of the install on a fresh Docker (after having completely deleted and reinstalled the docker package)
https://www.youtube.com/watch?v=sGRL6A-bSZQ
Environment
The text was updated successfully, but these errors were encountered: