Scrath

joined 9 months ago
[–] Scrath@lemmy.dbzer0.com 1 points 2 days ago

Did you ever find out what the books name was?

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

This is missing at least Bosch, probably some other brands I can't remember right now. That would ruin the 4 houses association though...

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

I hse keepassxc and store my password database in onedrive. My phone has an app keepass2android which can read the database in onedrive.

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

My father always called my sisters car "Beulchen", which is the german diminutive word for dent. It was a very basic Ford Fiesta. No wireless car key, no electrically controlled side mirrors but at least it had AC.

[–] Scrath@lemmy.dbzer0.com 3 points 3 weeks ago

Sometimes they have it written on the clockface. I don't think that's a general rule though.

In the same way there are digital clocks that can be wrong too though.

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

Depends for me. In my casual day to day I don't but when I had a lot of appointments to meet I find it quicker to check the time on my wrist than bu fumbling for my smartphone in my pocket, something that is probably even more true for women if they store their phone in a small bag due to lack of pockets.

Also, sometimes I like leaving my phone at home because I have unfortunately developed the tendency to give it a short glance whenever I have downtime. If I still need to know the time I can still wear a wristwatch.

[–] Scrath@lemmy.dbzer0.com 1 points 3 weeks ago (3 children)

There are radio controlled clocks which theoretically shouldn't be wrong. At least as long as there isn't a battery or motor issue...

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

Honestly that's just about being used to one versus the other. For me it's basically the other way around

[–] Scrath@lemmy.dbzer0.com 6 points 3 weeks ago

My first thought was "yes", my second thought was "actually, maybe not?" and my third thought was reading the word clockwise in another comment which would need to be replaced with another word to indicate direction around an axis and its opposite

[–] Scrath@lemmy.dbzer0.com 6 points 3 weeks ago

Not sure if that's the kind of device you are asking about but kobo e-readers run Linux. It's allowed me to sideload my books over SFTP instead of always having to plug in a USB cable

[–] Scrath@lemmy.dbzer0.com 8 points 3 weeks ago

As long as its not a propietary connector I don't see any problem with it. Bonus points if there are spare connectors for fans, LED lightning or even just spare GPIO pins available to allow for user modification

[–] Scrath@lemmy.dbzer0.com 57 points 3 weeks ago (6 children)

I'm not sure about how this works in kodi but in jellyfin the client might request a different resolution which causes the server to try and reencode the provided file on the fly. In my case my server isn't fast enough for this which leads to constant buffering

 

Hello everyone, I have another question regarding reverse-proxying again, specifically for the linuxserver.io jellyfin image.

On the dockerhub page for this image there are 4 ports listed which should be exposed:

  • 8096 for the HTTP Web UI
  • 8920 for the HTTPS Web UI
  • 7359/udp for autodiscovery of jellyfin from clients
  • 1900/udp for service discovery from DLNA and clients

Additionally there is also an environment variable JELLYFIN_PublishedServerUrl which is for "Setting the autodiscovery response domain or IP address". I currently have that set to my subdomain https://jellyfin.mydomain.com though I am not sure if that is correct.

I already have a reverse-proxy set up allowing me to access my servers webinterface under https://jellyfin.mydomain.com without exposing the https port on the container. What I am unsure about now however, is what to do with the two ports for UDP traffic.

By my understanding, a reverse-proxy will only forward traffic which comes to the ports 80 for http and 443 for https. Those are also the only ports my reverse-proxy container has exposed alongside the management interface. As such the 2 udp ports will not be reachable under my jellyfin domain.

How can I change this or is this even an issue?

8
submitted 7 months ago* (last edited 7 months ago) by Scrath@lemmy.dbzer0.com to c/selfhosted@lemmy.world
 

Hello, I have a question regarding the usage of a reverse-proxy which is part of a docker network.

I currently use Nginx Proxy Manager as a reverse-proxy for all my services hosted in docker. This works great since I can simply forward using each containers name. I have some services however (e.g. homeassistant) which are hosted separately in a VM or using docker on another device.

Is it possible to use the same reverse-proxy for those services as well? I haven't found a way to forward to hosts outside of the proxies docker network (except for using the host network setting which I would like to avoid)

view more: next ›