Sonarr raspberry pi1/15/2024 ![]() ![]() The VPN client running on my HTPC box masks all traffic from all of those applications, but I can access any of them anywhere by authenticating through the Apache Web Server hosted on my RaspberryPi. Follow these instructions and in the setup wizard and you will probably don't need to change anything.I'm sure the more network-savvy folk would disagree, but as a novice, here's what I do that's worked out great for a similar situation that you're trying to accomplish.Īll of my usenet applications are running on my HTPC Box and are easiest to maintain and configure since I'm most familiar with a Windows environment. This way, I will only expose and through nginx. Homeassistant has built-in fail2ban and therefore can be left exposed to the outside world (plus it is a requirement for google assistant integration). Fortunately we can set up a wireguard client in dietpi very easily and use this instead to access the less secure apps. Reverse proxies can be a bit insecure, specially if you are exposing random apps completely to the rest of the world with no fail2ban (radarr, sonarr, etc.). You will also need to update your google assistant apps to point to the new domain. Make sure that you have disabled the ssh addons (for security reasons). This will enable fail2ban and nginx reverse proxy. # Set this to your NGINX machine IP, or localhost if hosted on the same machine. # You must set the trusted proxy IP address so that Home Assistant will properly accept connections In your configuration.yaml file you will need to edit or add the http section as follows:
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |