Tesla Integration config - stuck

Configuration
1

I found this useful guide - https://www.youtube.com/watch?v=oEaEAiLOqO4

I set up and running DuckDNS.
I set up and runnig NGNIX.

I have tested and cane remotely log into https://mydomain.duckdns.org and use HAOS UI.

BUT…testing to view the tesla public key (https://yourdomain.com/.well-known/appspecific/com.tesla.3p.public-key.pem) results in “Not found”. When I use terminal to navigate through the folder structure (ie /share…/appspecific) I can list and see the com.tesla.3p.public-key.pem file. So not sure why the https test to it results in not found.

As a consequence when I try to register as a partner with Tesla, it gives an error as the public key doesn’t respond as expected (ie Tesla cannot see the public key)

So am stuck …why doesn’t the tesla public key test work when the file is there…how do I fix it?

3

How do I add an explicit location in NGINX? How do I curl -l from outside (only time I’ve used curl is on the HAOS box following instructions).

4

Got some help from AI.

Added a file to /share/ nginx_proxy_default_tesla.conf as follows:

location /.well-known/appspecific/com.tesla.3p.public-key.pem {

root /share/tesla;

}

This didn’t seem to help. Can access HAOS remotely, but the pem file test shows 404: not found.