-
Hi guys,
Standard docker-compose.yml was used with no modification, meaning it is on both port 4000 and 3000 and etc. Port 3000 is ok, but not 4000. Port 4000 listening: Also I had some issues with my Synology NAS running Teslamate and once upgraded to latest version and it stopped working with the same error message shown above. I thought it might be the firewall settings on router(s), so I was bold enough to disable FW and tested with no luck at all. Efforts have been made to downgrade the previous release like 1.25.1 and again problems were still there. Thanks! |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 1 reply
-
Alternatively, I just had Teslamate installed on VPS and tested with the following message: root@TSL:/tesla# curl -v http://x.x.x.x:4000
No ports were listening on either 4000 or 3000. Docker ps shows: CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES teslamate showing Restarting, no database? Can't even connect to port 4000 so no login can be made, ouch. Not sure if this is the software bugs or anything and sincerely wish this could be solved at any time soon. Thanks! |
Beta Was this translation helpful? Give feedback.
-
so may have to wait for the upcoming release to get it fixed and untill then have to live with no teslamate for a while... |
Beta Was this translation helpful? Give feedback.
-
Finally got it working by using the old version of yml file. So definitely it was the software issue here. |
Beta Was this translation helpful? Give feedback.
-
I have the exact same issue. I installed Teslamate on a Synology, I can't get to 192.168.xxx.xxx:4000 |
Beta Was this translation helpful? Give feedback.
Finally got it working by using the old version of yml file. So definitely it was the software issue here.