Scrath

joined 2 years ago
[–] Scrath@lemmy.dbzer0.com 3 points 2 years ago

Goddamn you physics

[–] Scrath@lemmy.dbzer0.com 1 points 2 years 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

[–] Scrath@lemmy.dbzer0.com 4 points 2 years ago (1 children)

Thanks for the motivational speech

[–] Scrath@lemmy.dbzer0.com 1 points 2 years ago

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.

[–] Scrath@lemmy.dbzer0.com 1 points 2 years ago (1 children)

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

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
[–] Scrath@lemmy.dbzer0.com 2 points 2 years ago (6 children)

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

[–] Scrath@lemmy.dbzer0.com 4 points 2 years ago

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

[–] Scrath@lemmy.dbzer0.com 1 points 2 years ago

I tried that one but I just couldn't get used to it due to its bullet point nature

[–] Scrath@lemmy.dbzer0.com 3 points 2 years ago* (last edited 2 years ago)

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

[–] Scrath@lemmy.dbzer0.com 2 points 2 years ago (2 children)

As much as I'd love to get into obsidian, it being non-open source and having a restrictive license makes it unavailable for me. I would love to use it to keep track of information for work but the license prohibits that without a subscription.

[–] Scrath@lemmy.dbzer0.com 13 points 2 years ago

Probably for the same reason why they decided to rename USB 3.0.

I guess they had a liquor cabinet in the room where they held their meeting

[–] Scrath@lemmy.dbzer0.com 7 points 2 years ago

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

view more: ‹ prev next ›