Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)SC
Posts
4
Comments
230
Joined
2 yr. ago

  • What caused you to move to the other side of the world?

    I think about moving away sometimes but I have quite strong roots where I am in terms of family and friends and I'm not sure how well I could handle leaving that behind and ending up alone somewhere

  • 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.

  • Thanks. I tried it like this and still get a 400 Bad Request error.

    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).

     YAML
        
    http:
      use_x_forwarded_for: true
      trusted_proxies:
        - 192.168.208.2 # IP of reverse-proxy in its network
        - 192.168.208.0/20 # Subnet of proxy docker network
        - 192.168.1.103 # HA IP
    
      
  • 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

  • Unfortunately I still have some breaking bugs with wayland on my laptop.

    Most notably big blue button (an open source video conference tool) refuses to connect when using firefox with wayland.

    Firefox does not allow copying of urls in wayland if a certain setting is enabled in kde plasmas settings.

    I cannot move views around or redock windows in eclipse.

    Xilinx vivadi randomly crashes on wayland but not on X11.

    Notably, aside from the url copying problem, most of those things will not be an issue for the typical user

  • 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

  • Personally I have the opinion that usb-c should be a connector for mobile devices only and there should be something with the size of a type a or b for stationary stuff. The size makes the connector too flimsy

  • By adding do you mean blocking it in pi-hole or somehow redirecting it to your pi-hole dns server?

    I currently have it blocked in my router and can confirm this by trying to ping 8.8.8.8 without any response. If you mean redirecting to your pi-hole I would really like to know how to do it

  • 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)