SO I’ve started the configuration of my Tesla EV. I understand I have to set up a developer account, which gives me $10 per month credit. When I step through the developer registration and try to follow this page I am first asked for the “Allowed origin url”…the page states to enter “your domain”…? My HA is on the intranet and I don’t have an external domain or URL - at most I would have a WAN IP, but that likely changes periodically when my ISP assigns/re-assigns it.
So what do I enter as the original URL? DO I need to set up an entire external domain or similar?
So generated tesla fleet key and public key and moved to the respective directories.
INstalled and run Duckdns
INstalled and run NGINX. But when I try to test accessing the public key or the domain at all, it doesn’t work. Not sure why or how to fix it.
I am now able to successfully remotely go to mydomain.duckdns.org and log into my HAOS. But it’s http and not https. So something about the certificates is not right and SSL is not working.
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.
So am stuck …why doesn’t the tesla public key test work when the file is there…how do I fix it?