Replies: 8 comments 29 replies
-
|
It will be easier to help if you show the correct domain name. That piece of information is not sensitive; the public key is meant to public. |
Beta Was this translation helpful? Give feedback.
-
|
@llamafilm OK sounds good. I've removed that redaction so any instance of |
Beta Was this translation helpful? Give feedback.
-
|
I can see your DNS resolves at least, so that's good. Assuming 73.42.203.35 is your correct IP address, it sounds like nginx is not configured right, maybe it's not seeing the |
Beta Was this translation helpful? Give feedback.
-
|
The NGINX log is in the original post. Appreciate the help but JFYI I've decided to switch to Tessie instead. I've spent too much time in this so decided to cut losses |
Beta Was this translation helpful? Give feedback.
-
|
I have the same problems. I don’t even know if I really need a second domain for the Tesla stuff. The tutorial for the Tesla HTTP Proxy recommends „NGINX Home Assistant SSL proxy“ which can only use one domain. I used the community add-on „Nginx Proxy Manager“ before, which can use multiple domains, but it didn’t work with Tesla HTTP Proxy tutorial. |
Beta Was this translation helpful? Give feedback.
-
I'm in a similar situation : I've setup duckdns + nginx and can access my HA instance from duckdns url. However, 404 error when trying to reach Two questions :
|
Beta Was this translation helpful? Give feedback.
-
|
Ok, so it sounds like Nginx is receiving the request. I think you need to fix this: nginx: [warn] conflicting server name "mydomain.duckdns.org" on 0.0.0.0:443, ignored If you share the full unredacted contents of all Nginx config files, it would be easier to help you. I really don’t understand why people are shy about sharing a domain name. |
Beta Was this translation helpful? Give feedback.
-
|
@SmarterHomeLife please share the base config of Nginx addon as well, from Settings > Addons > Nginx > Configuration > Edit in YAML. I suspect you are trying to use the same |
Beta Was this translation helpful? Give feedback.
-
|
Not quite. What I meant is that you no longer need a 2nd domain name. So if you don't want Home Assistant to be publicly accessible on its own domain, then make up a fake name for the "primary" domain, i.e. change the first line to this: domain: core-nginx-proxy |
Beta Was this translation helpful? Give feedback.
-
|
yes |
Beta Was this translation helpful? Give feedback.
-
|
changing the domain in nginx to |
Beta Was this translation helpful? Give feedback.
-
|
I'll leave this open since others are troubleshooting, but I'm no longer in need of a fix. I gave up and went with Tessie. The integration is fantastic and took all of 3 minutes to start sending commands to my car again. To others banging their heads against a wall over this, if you can afford $5/month for Tessie, highly recommended too save yourself the trouble. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
That screenshot appears to be the regular SSH addon. For this troubleshooting step, you need to be in the Docker host. You can install the port 22222 configurator from here: https://github.com/adamoutler/HassOSConfigurator. Then run it and SSH in on port 22222. |
Beta Was this translation helpful? Give feedback.
-
|
Does the T HTTP Proxy addon exit if there’s a failure to check the key? That would explain why the container ain’t running. If you run the curl command with its arguments directly in a HAOS SSH terminal, does that give an error? Seems it should work from there as well. |
Beta Was this translation helpful? Give feedback.
-
|
What does nslookup or dig returns for the IP address using your Tesla hostname as argument? If it returns the external IP address, I’m not sure if basic port forwarding on your router will properly forward the traffic coming from your internal network. I’m just not sure. Can a PC connected on your local network access the key using the URL to your key? |
Beta Was this translation helpful? Give feedback.
-
|
53 is the default tcp/udp port for DNS service. Per the output of the command, can you do a nslookup tesla.thecolorsofyou.com , not thecolorsofyou.com - perhaps both are pointing to the same local IP?! If they don't have the same IP address, from your PC did you try to access the key using https://tesla.thecolorsofyou.com/... or just https://thecolorsofyou.com ? Last. the nslookup you ran is within HAOS SSH terminal or your PC? Try in HAOS. |
Beta Was this translation helpful? Give feedback.
-
|
Did you find a solution for this? |
Beta Was this translation helpful? Give feedback.
-
Since you're doing port forwarding on your router, it's likely that both should point to your router's public IP.
That should be the IP address of the Nginx docker instance and per the config, it is Nginx that is responsible to serve the pub key. I'm a bit out of clue now.... Nginx if it's running should have no issue to serve the key. |
Beta Was this translation helpful? Give feedback.
-
|
@tannerwastaken if from HAOS SSH terminal you run: Does it return: I confirm 172.30.32.3 is the IP address of the Nginx add-on. |
Beta Was this translation helpful? Give feedback.
-
|
Why is it listening on port 8126? It must be listening on 443. That's probably why things are broken. If you have something else on port 443, either you yank it out or figure out how to configure so that requests for the "Tesla pubkey" goes to Nginx. |
Beta Was this translation helpful? Give feedback.
-
|
Changed it, same results. |
Beta Was this translation helpful? Give feedback.
-
|
Is your output now similar this? By default Nginx should have been on port 443, if you made any manual changes, I suggest you delete the Nginx add-on and re-install it. Make sure to use the settings mentioned in DOCS.md. |
Beta Was this translation helpful? Give feedback.
-
|
Not sure what you mean by "Yes." and by " still get the same fix?? ".
Please elaborate as much. |
Beta Was this translation helpful? Give feedback.
-
|
After moving Nginx to the default 443 port, what's the output of this If the above still fails, what's the output in HAOS SSH terminal for If it returns your pub key, then consider to uninstall/reinstall the Tesla HTTP Proxy and afaik it should now work. If the key still isn't returned when running curl, then I'm not sure I can still help. |
Beta Was this translation helpful? Give feedback.
-
|
I've got the same issue wherein "https://tesla.example.com/.well-known/appspecific/com.tesla.3p.public-key.pem" seems not reachable... I've tried the domain: core-nginx-proxy in NGINX, but when I do this, my HA IOS app saying the cert is not valid My setup DuckDNS
NGINX with this setup, my certs are valid for both melha.duckdns.org and meltesla.melha.duckdns.org as per SSL cert checker |
Beta Was this translation helpful? Give feedback.
-
I've been hitting a wall with this add-on so I'm transcribing my approach step-by-step in hopes that someone can tell me where I've gone wrong. I couldn't send commands with the owner API anymore so I'm trying to migrate. Pardon unnecessary redactions, this isn't my expertise so I don't know what's risky to share.
First, my environment:
192.168.0.2:8123Step-by-Step Configuration
Following the docs to the best of my ability.
1. Registered domain on DuckDNS:
theredrocket.duckdns.orgI've registered the domain, I've got an IP address and token.
2. Install and configure DuckDNS Add-On
Here's the config. The only "novel" thing is my use of aliases, this seemed to be the only way I could ge LetsEncrypt to get me a cert for
tesla.theredrocket.duckdns.orgso that's why it's there:Start add-on and see the log output. I can now see
fullchain.pemandprivkey.pemunder my/ssldirectory. FYI this was the original log before adding those aliases above (but that was successful too).3. Install and configure LetsEncrypt Add-On
Config:
Log output after starting LetsEncrypt:
4. Install and configure NGINX Home Assistant SSL Proxy Add-On
Before configuring the add-on, I'm adding this to my
configuration.yamland restarting home assistantAfter restart, I'm configuring the add-on as follows:
Starting the add-on, here are the logs:
4. Install and configure Tesla HTTP Proxy
Here's the config, leaving client ID and secret blank for now per the documentation:
Now I start the add-on, and get this log:
Then, I called the supervisor service to STOP the NGINX add-on, and restarted it.
The Result...
I can see
/nginx_proxyand/teslain my/sharedirectory (using Samba add-on for Windows). I see files appearing in each including public key.I still cannot reach the public key from
https://tesla.theredrocket.duckdns.org/.well-known/appspecific/com.tesla.3p.public-key.pem. I hit a 404 page every time.I've looked up
theredrocket.duckdns.organdtesla.theredrocket.duckdns.orgusing DNS checkers and both are returning results.Where did I go wrong?
Beta Was this translation helpful? Give feedback.
All reactions