The company says services like Plex, Pluto TV, Sling TV, Starz, and ZDF will introduce support later this year.
I always had the impression that plex was really slow when it comes to implementing new features. I’m definitely looking forward to a chromecast alternative though. Being locked into googles DNS gives me problems due to it prohibiting streaming from my local server via hostname.
I really hope it will be implemented in Jellyfin as well since I can’t get my installation to work with Chromecast at all (most likely again due to the DNS issue)
I used to like slavart. I found out about them while they still allowed album downloads on their website. Later I moved to their divolt website (like a selfhosted discord) where they allowed downloads via bots.
At some point they decided not to bother with divolt and told everyone to start using their discord bot. Anyone who had concerns about privacy or about using their main discord account for piracy was pretty much told that they were an idiot and should go fuck themselves.
At that point I transitioned to ripping directly from quobus as explained in this guide. If I can’t find what I want on quobuz I go to deezer.
I dimly remember my grandmother having straws made from actual straw (or something similar at least). I don’t remember how well they worked unfortunately
By exposed you basically mean that I can reach them using my browser? I can reach my homeassistant web ui on port 8123 but when I try to forward to that port with the servers IP I get a 400 Bad Request error. I’m not sure if this is caused by nginx being unable to forward or by homeassistant not accepting the connection somehow
I use annas archive for ebooks but I organize those with calibre, not audiobookshelf because I have a somewhat peculiar organization scheme that relies on calibres custom columns and export feature.
My audiobooks I get from abtorrents but I heard great things about myanonamouse
Good to know. I thought there was some issue with those ports and the reverse-proxy because the DLNA function doesn’t seem to be working but from some googling this seems to be more of a docker problem in general when you are not using host mode for networking.
Thanks for the configuration example. Unfortunately it doesn’t seem to work for me. I’ve replied to someone above with screenshots of what my configuration now looks like. The base_url option you use there wasn’t available to me because it apparently has been deprecated and replaced with internal_url and external_url.
Someone below mentioned adding some more IPs to the trusted_proxies list so I tried that as well without result. The IP I used for the reverse-proxy is the IP listed in portainer under the network for the proxy container. Just to reiterate, the container is running on a different device than homeassistant (technically same device but different VM but that shouldn’t make a difference).
<span style="color:#63a35c;">http</span><span style="color:#323232;">:
</span><span style="color:#323232;"> </span><span style="color:#63a35c;">use_x_forwarded_for</span><span style="color:#323232;">: </span><span style="color:#0086b3;">true
</span><span style="color:#323232;"> </span><span style="color:#63a35c;">trusted_proxies</span><span style="color:#323232;">:
</span><span style="color:#323232;"> - </span><span style="color:#0086b3;">192.168.208.2 </span><span style="font-style:italic;color:#969896;"># IP of reverse-proxy in its network
</span><span style="color:#323232;"> - </span><span style="color:#183691;">192.168.208.0/20 </span><span style="font-style:italic;color:#969896;"># Subnet of proxy docker network
</span><span style="color:#323232;"> - </span><span style="color:#0086b3;">192.168.1.103 </span><span style="font-style:italic;color:#969896;"># HA IP
</span>