Skip to content

Host public key file on Home Assistant with "NGINX Home Assistant SSL proxy" Add-on #37697

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
mano3m opened this issue Feb 25, 2025 · 6 comments · May be fixed by #37703
Closed

Host public key file on Home Assistant with "NGINX Home Assistant SSL proxy" Add-on #37697

mano3m opened this issue Feb 25, 2025 · 6 comments · May be fixed by #37703
Labels
integration: tesla_fleet Stale The PR had no activity for quite some time, and is marked as Stale

Comments

@mano3m
Copy link

mano3m commented Feb 25, 2025

Feedback

For those of us that use the reverse proxy "NGINX Home Assistant SSL proxy" Add-on together with a service like duckdns for external Home Assistant access, the public key file can also easily be hosted locally instead of on a third party service.

  1. In the Settings->Add-Ons->NGINX Home Assistant SSL proxy->Configuration, set the customize.active option from the default false to true
  2. Create a nginx_proxy_default_tesla.conf file in /share/ with the following contents:
location /.well-known/appspecific/com.tesla.3p.public-key.pem {
  root /share/tesla;
}
  1. Copy the generated public key to /share/tesla/.well-known/appspecific/com.tesla.3p.public-key.pem
  2. Restart NGINX on the Settings->Add-Ons->NGINX Home Assistant SSL proxy->Info page

URL

https://www.home-assistant.io/integrations/tesla_fleet/

Version

2025.2.5

Additional information

No response
@home-assistant
Copy link

Hey there @Bre77, mind taking a look at this feedback as it has been labeled with an integration (tesla_fleet) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of tesla_fleet can trigger bot actions by commenting:

  • @home-assistant close Closes the feedback.
  • @home-assistant rename Awesome new title Renames the feedback.
  • @home-assistant reopen Reopen the feedback.
  • @home-assistant unassign tesla_fleet Removes the current integration label and assignees on the feedback, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information) to the feedback.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information) on the feedback.

@Bre77
Copy link
Contributor

Bre77 commented Feb 25, 2025

You could just raise a PR to add these instructions to the page.

@mano3m
Copy link
Author

mano3m commented Feb 25, 2025 •
edited
Loading

I see that you've improved the https://fleetkey.cc/ site to make it simpler for users (it didnt work yet when I installed the integration, so I used the AWS S3 option). With hosting locally, however, a lot of the other steps can probably also be done locally with a configure script in the Tesla Fleet integration..? This might make it a lot simpler/more accessable for users.

@mano3m mano3m mentioned this issue Feb 25, 2025
Open
8 tasks
@Bre77
Copy link
Contributor

Bre77 commented Feb 26, 2025 •
edited
Loading

a lot of the other steps can probably also be done locally with a configure script in the Tesla Fleet integration..?

Yep, Tesla didn't really give me much notice about this. The whole integration was setup to use the built in credential because it was already registered and ready to go. Now that users have to set it up themselves it would actually have been better to use Machine 2 Machine credentials, so I am hoping I can, combined with the tesla_bluetooth integration, create a much more seemless setup experience that requires zero external dependancies.

But its going to take time as I need to focus on fixing Teslemetry first since people are paying me to do that.

@github-actions GitHub Actions
Copy link

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved.
If this issue is still relevant, please let us know by leaving a comment 👍
This issue has now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the Stale The PR had no activity for quite some time, and is marked as Stale label Apr 27, 2025
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 4, 2025
@mano3m
Copy link
Author

mano3m commented May 4, 2025

A bit unfortunate I did all the work and it is not progressing and now closed. I dont think I will spend the effort again to contribute to Hass...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
integration: tesla_fleet Stale The PR had no activity for quite some time, and is marked as Stale
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Update tesla_fleet.markdown with NGINX public key hosting option. mano3m/home-assistant.io
2 participants
@mano3m @Bre77