Closed Kureigu07 closed 5 months ago
Couldn’t resist …. Maybe this add-on should use port 7399 (S3XY) 😂
Port 8099 is not exposed outside the docker network, it's only available through Home Assistant ingress. So it will not cause a conflict. Read through the discussions. There are many other users having trouble with their public key, and it's almost always caused by some problem with your domain, DNS, or TLS certificate.
The problem
This add-on appears to use port 8099 for the flask web-ui, however the add-on GivTCP also uses the same port for a web interface. Neither add-ons allow this port to be configured, which I believe is resulting in a 502 error and "Fix public key before proceeding."
What version of the addon are you using?
2.2.3
What version of Home Assistant Core are you using?
core-2024.3.3
What type of installation are you running?
Home Assistant OS
What version of Tesla integration are you using?
v3.20.5
What region of Tesla API are you using?
Europe, Middle East
What model and year is your vehicle?
Y 23
What is your domain name (FQDN)?
nocnbots.duckdns.org
Paste the log output from the addon here
Any additional context or screenshots that help explain the issue
No response