ChrisLicht

joined 1 year ago
[–] ChrisLicht@lemm.ee 13 points 2 months ago

Thank you. I can’t figure out if it’s that or a rest-of-the-fucking-owl.

[–] ChrisLicht@lemm.ee 1 points 7 months ago

Craig Richards - Fabric 01

[–] ChrisLicht@lemm.ee 2 points 7 months ago (1 children)

If you add white vinegar to load, you won’t get the ick from clothes sitting in washer for hours.

[–] ChrisLicht@lemm.ee 2 points 7 months ago (1 children)

I thought it was called the Dark Forest Trilogy.

[–] ChrisLicht@lemm.ee 22 points 7 months ago (3 children)
[–] ChrisLicht@lemm.ee 5 points 7 months ago
[–] ChrisLicht@lemm.ee 12 points 7 months ago

Left side is heart rate. Right side is penis.

[–] ChrisLicht@lemm.ee 50 points 7 months ago

Here is a joke I heard in Moscow, in the early-‘90s:

Our Soviet computer sector was clearly the best. We built the largest chips in the world!

[–] ChrisLicht@lemm.ee 1 points 7 months ago (1 children)

Makes sense. Does the state still go after the insurer?

[–] ChrisLicht@lemm.ee 15 points 7 months ago (1 children)

Her father was also one of the highest-earning crim defense lawyers.

[–] ChrisLicht@lemm.ee 10 points 7 months ago (6 children)

Why isn’t the ship’s insurer paying for the bridge repair?

[–] ChrisLicht@lemm.ee 38 points 7 months ago (1 children)

None of that matters. I just like riding around town in one of Lara Croft’s breasts.

 

I am not a networking expert, so please forgive any poor or unclear terminology here . . .

My recently built Unraid Plex/Arr box works great, but I would like to set up NGINX Proxy Mgr and reverse proxy. My current challenge is that when I install NPM, all of a sudden all of my Arr apps, which are set to network though OpenVPN-Client, start mapping 443>443 and 80>80 (app to host).

Sonarr, Radarr, Readarr, NZBGet, qBittorrent, Bazarr, Requestrr all have app-to-host mappings like this, when NPM is installed:

Network: container:OpenVPN-Client

Port Mappings:

10.0.1.99:443/TCP10.0.1.99:443

10.0.1.99:80/TCP10.0.1.99:80

10.0.1.99:81/TCP10.0.1.99:81

My OpenVPN-Client app-to-host mappings don't include either port, which makes this doubly confusing:

172.17.0.2:3579/TCP10.0.1.23:3579

172.17.0.2:4545/TCP10.0.1.23:4545

172.17.0.2:6767/TCP10.0.1.23:6767

172.17.0.2:6789/TCP10.0.1.23:6789

172.17.0.2:6881/TCP10.0.1.23:6881

172.17.0.2:6881/UDP10.0.1.23:6881

172.17.0.2:7878/TCP10.0.1.23:7878

172.17.0.2:8080/TCP10.0.1.23:8080

172.17.0.2:8191/TCP10.0.1.23:8191

172.17.0.2:8989/TCP10.0.1.23:8989

172.17.0.2:9696/TCP10.0.1.23:9696

NGINX Proxy Manager network and mappings:

Network: br0

Port Mappings (App to Host):

10.0.1.99:443/TCP10.0.1.99:443

10.0.1.99:80/TCP10.0.1.99:80

10.0.1.99:81/TCP10.0.1.99:81

And, when I remove NPM, everything goes back to normal and works fine, with no app-to-host mappings showing up for Arr apps in the main Docker view.

What dumb thing have I done?

 

OpenVPN-Client is running normally, per its logs and ifconfig.me. The vpn.ovpn and vpn.auth files are working properly.

In the Extra Parameters field of Deluge template I have added: --net=container:OpenVPN-Client

In OpenVPN-Client template:

 - Network Type is set to None
 - I have added a port record: Host Port 8112 and Container Port 6881

Deluge's WebUI won't load at all. I tried qBittorrent instead, using the same approach as above, and it won't load the WebUI either.

 

For a couple of years, I have been serving Plex to a few friends and family from an NVIDIA Shield Pro on a gigabit fiber. Before that, I served from a Raspberry Pi.

I have basic Linux skills, and my dream is to build a more automated setup. Unraid OS with Plex and -arr apps looks great to a non-expert like me.

So, I just picked up an unmolested original Lenovo ThinkCentre M710Q 7500T with 16GB RAM, and a 256GB M.2. I have a spare 2.5" 2TB Samsung EVO 970 SSD that I could put in it; I also have a 3.5" WD Red 4TB external HDD.

Here are my questions:

  • Do I need more RAM to be able to serve four 1080 streams at once?
  • Should I use the SSD or HDD, or both?
  • Any other advice or suggestions? It's appreciated!
 

I started with XMBC then Kodi then Plex on a succession of Raspberry Pis. Then, four years ago, I switched to running Plex on a Shield Pro.

Now, I am trying to pick up enough Linux and Docker knowledge to be able to set up a Plex server, just for video, with automated RSS torrent management, running in Docker on an 8GB Raspberry Pi 4 running Raspbian Bullseye.

I am not a technologist by trade, so hoping to find a Docker image that enables that without needing a lot of additional Linux plumbing to make it work. I am old and mostly rely on rudimentary UNIX skills left over from the late-'80s.

Thanks for considering!

 

I am at a high-beginner/low-intermediate level in Python, and one thing that drives me nuts is how poorly I am able to read the Python official documentation and grok how to use the described code.

What's the secret? Are there any guides/videos/books that can help my understand how to approach reading it? Or, is it just one of those things that I need to just keep coming back to while coding, and eventually I will get the hang of it?

 

I have encountered the typing module's callable type in a Python book, and saw it tangentially referenced in a couple of videos, but I still don't really grasp what it is for, when to choose to use it, and how it works. (The O'Reilly text I am mostly using is more of a desktop reference than a textbook.)

Hoping someone here might have a suggestion for a good YouTube explanation/demonstration.

 

I can use an existing class, and I kinda grasp the basics, but I am shaky whenever I have to sit down and create one from scratch that is more than just a bit of data or a couple of functions.

Would love to find a clear video tutorial.

 

Is there a Lemmy app that will auto-hide read posts?

 

Have two iPads with wefwef on them. 0.14.0 works great on one, but 0.15.0 is throwing lots of errors on the other, upon pretty much any action other than simple browsing.

Commenting, searching, and profile-loading all throw the red error bar at the bottom.

view more: next ›