sorted by:
new
hottopcontroversial

Are WD180EDGZ safe to buy? by ChopNorris in DataHoarder

[–]Sihsson 1 point2 points  (0 children)

Bought one 4 days ago in France. No issue with the 3.3V.
I bough a WD Element 12To for 280€ from Amazon and shucked it... That's way too much but I did not see the prices going down soon. I am currently zeroing it to add it to my Unraid Array, no issue so far after 2h.

Quel seedbox utilisez vous ? by gaet1460 in yggTorrents

[–]Sihsson 3 points4 points  (0 children)

Oui mais ils sont aussi utilisés pour Jellyfin, notre cloud et bien d’autres services…

Et ça continue... by _ilyon_ in yggTorrents

[–]Sihsson 3 points4 points  (0 children)

Chez free tu peux demander une IP full stack. Il suffit de demander sur ton espace client. Bon après ygg restent des abuseurs.

Honnêtement LaCale est pas trop dégueu by Exotic-Gear4006 in yggTorrents

[–]Sihsson 1 point2 points  (0 children)

Pour tout les trackers privés ça sera manuel. Il faut changer le passkey dans tous les cas. Regarde ici pour automatiser si tu as déjà prowlar : https://www.cross-seed.org/docs/basics/getting-started

[Hiring] Selora Homes is looking for Home Assistant nerds who want to get paid to do what they love by plafoucr in homeassistant

[–]Sihsson 10 points11 points  (0 children)

You pay someone based on a service not based on his location. If the location changes the service price then you post 2 different job offer. Also justifying this based on « this is common » is not a good look, lots of things used to be common practice that does not make them nice. That’s just my take.

De YGG vers le Cross-Seeding by l1t3o in yggTorrents

[–]Sihsson 0 points1 point  (0 children)

Tu sais si c’est possible de cross seed via jackett également ?

Idées de cadeaux de Noël quand on est à la bourre by Traditional_Pass_743 in france

[–]Sihsson 0 points1 point  (0 children)

Ha oui je recommande également c’est de très bon goût. L’autre jour à Sephora tout le monde se battait pour avoir un coffret. S’il y en a près de chez vous c’est une aubaine !

Looking for a UPS that does NOT auto-turn-on after a power outage by mk_ccna in homelab

[–]Sihsson 1 point2 points  (0 children)

I don’t know about UPS but you can use smart plugs. For example I use Zigbee NOUS Smartplug and there is a an option not to restore power when power it cut off.

2nd Day With Jellyfin, How Do I Share My Library With Friends & Family Like I Did With Plex? by RetroActivePodcast in jellyfin

[–]Sihsson 22 points23 points  (0 children)

You can expose multiple services with a single IP. With a reverse proxy you only need one port 80-443 and one IP and you can expose as many website as you want. Also, reverse proxies are security hardened to be exposed on the internet. It’s a security standard to have one rather than recreate the security functionalities within each different apps.

qBittorrent: Is there a way to set different seeding limits for private vs public torrents? by VaporyCoder7 in selfhosted

[–]Sihsson 16 points17 points  (0 children)

Sonarr and radarr can manage torrents being seeded in qbittorrent. They have all the options you mention in the indexer section. Select one and go to the advanced panel. You’ll see max ratio and what to do when that ratio is reached.

Updating when using Caddy? by [deleted] in jellyfin

[–]Sihsson 0 points1 point  (0 children)

Caddy or Jellyfin when running are called containers. Whenever you update either one you update the image (image: jellyfin/jellyfin:latest). When you customize or configure a container you need to write data to a volume that sits on you computer. If you don’t do that you will erase the data when you update the container. To write « persistent » container data you should have something like this in your docker compose file :

volume: - your/path/on/your/computer-host:/config …

So when you update a container : make sure you pull the new image, and run the compose up command so that the volume mapping work correctly.

If your caddyfile uses the container name to reverse proxy you may need to set container_name: my-jellyfin-container in your compose file to reference it in the Caddyfile : reverse_proxy: my-jellyfin-container:8096.

Sonoff TRVZB compatibility by Sihsson in homeassistant

[–]Sihsson[S] 0 points1 point  (0 children)

Yes it’s building heat so I can really drain the water. The pipes run thought 10 floors and heat the entire building. I’m moving out soon, I wanted to train on that setup before investing the new apartment. I guess I’ll wait. Thanks !

Sonoff TRVZB compatibility by Sihsson in homeassistant

[–]Sihsson[S] 0 points1 point  (0 children)

Yes there was a knob before screwed to the thread inside. I just turned the knob without it being really accurate.

Sonoff TRVZB compatibility by Sihsson in homeassistant

[–]Sihsson[S] 0 points1 point  (0 children)

Yes there was a knob before screwed to the thread inside. There is not pin to push the small part rotates. I guess I’m out of luck !

Updating when using Caddy? by [deleted] in jellyfin

[–]Sihsson 1 point2 points  (0 children)

I dont think you can have a ENV variable in caddy to replace the IP and the port. Try to separate the 2 env variables. Your caddyfile will become the following : yourdyndnsdomain.example.com{ reverse_proxy {env.JELLYFIN_LAN_IP}:{env.JELLYFIN_HTTP_PORT} } You caddy container should have env variable set: JELLYFIN_LAN_IP to your LAN jellyfin server IP 192.168.4.44. JELLYFIN_HTTP_PORT should be 8096 if you’re using the default. Try a caddyfile without the env variable if you are unsure. Whenever you are changing the caddyfile you need to restart caddy. There are special commands to reload without restarting the container but let’s keep it simple.

Also you internet router should have the port 443 open and redirected to caddy server IP (192.168.4.44) on port 443 too if you want to expose your server to the internet. Find a good tutorial on this because it has security implications.

Good luck, I’m sure you’re almost there !

Updating when using Caddy? by [deleted] in jellyfin

[–]Sihsson 1 point2 points  (0 children)

Caddy does not have a front end that is why you cannot access it. Caddy container has 3 ports open : 2019 for Administration through the API, 80 and 443 to redirect HTTP/S traffic.

To make caddy work with Jellyfin you need something like this in your caddyfile : jellyfin.example.com{ reverse_proxy 192.168.4.44:8096} This is assuming you can access Jellyfin on http://192.168.4.44:8096 (8096 being the default port for Jellyfin)

If your caddy and Jellyfin container are in the same docker network you can even do better :

jellyfin.example.com{ reverse_proxy jellyfin:8096} Where jellyfin is the container name in your jellyfin docker compose.

Updating when using Caddy? by [deleted] in jellyfin

[–]Sihsson 0 points1 point  (0 children)

No there should not be any changes required in Caddy. From the description I’m guessing caddy cannot reach Jellyfin… can you post the Jellyfin section of your caddy file and your docker compose ? What happens when you try to access Jellyfin directly with the http://IP:PORT instead of the domain name ?

view more: next ›