Closed bahree closed 2 months ago
I also wanted to add that this is on Digital Cloud if that makes a difference.
hello,I had the same problem. Version | 1.29.2
What is interesting is that if I setup a new ubuntu VM on Azure, the same thing works - but not on Digital Cloud -- any suggestions?
hello,I had the same problem. Version | 1.29.2
@RocketSharks did you also try on Digital Cloud?
No, I just tried it locally in docker
Feel like I recall a period where Digital Ocean IPs were blocked by Tesla. My guess is that's the issue.
Would suggest opening a ticket with Digital Ocean, but it's beyond their control as Tesla implemented the blocker.
What is interesting is that if I setup a new ubuntu VM on Azure, the same thing works - but not on Digital Cloud -- any suggestions?
Closing as this is not a TeslaMate issue.
Is there an existing issue for this?
What happened?
I am setting up another instance of Teslamate, in a docker container on a cloud VM - I already have one instance running for a while, and I wanted to get another one going. When I setup the advanced (Traefik) docker container and bring it up the first time, as expected I get the screen to enter the tokens, as shown below. But when I enter the tokens generated by the TeslaAuth app it doesn't like it.
I have also deleted the docker volume just to be sure and restored from the backup (of the other instance) and tried that - but no dice either. :(
Here is the image from the TeslaAuth app:![image](https://github.com/teslamate-org/teslamate/assets/3529468/0a2b5dc2-80f3-474c-81fe-83d5f3fc63c6)
Any ideas on what is wrong? I can see this in the logs (ssh'd into the vm):![image](https://github.com/teslamate-org/teslamate/assets/3529468/8fbf8bab-4f9d-4d18-8f7f-a0f5d4a97ee8)
Expected Behavior
Able to authenticate and login.
Steps To Reproduce
Start the container and navigate to the FQDN
Relevant log output
Screenshots
No response
Additional data
No response
Type of installation
Docker
Version
v1.29.2