• 4 Posts
  • 70 Comments
Joined 1 year ago
cake
Cake day: June 19th, 2023

help-circle

  • There’s already a noticeable drop in quality. I bought a big Mac meal recently for the first time in a while, the fries were like toothpicks, and the large fries seemed much smaller than I recall.

    The burger had the tiniest dollop of sauce and the patties were so thin they barely held their shape.

    I know it’s all purely anecdotal, but for years I was hooked on their hash browns until they changed the recipe… And now I can’t stand them but at least I’m losing weight so that’s good haha


  • I do vaguely remember something about it getting changed, but yeah, as you said unless you’re sharing it with a bunch of people, it’s probably not enough to trigger anything on their side anyway

    I think theres a nice variety of methods out there now that there’s no “one right way” to do it which I think is great compared to just a few years ago where your only real options were a reverse tunnel or CloudFlare tunnels



  • first your questions

    Is the tunnel solution appropriate for jellyfin?

    Yes but also no. the tldr is It will work, but video streaming is against CloudFlare rules. I ran this way for about 2 years with Plex just for my own use, so for about 15 hours a week on 480p and I never got my service suspended, but I’ve heard stories of others getting suspended… So just know it’s a risk

    I suppose it’s OK for vaultwarden as there isnt much data being transfered?

    That’s a good use of tunnels

    Would it be better to run nginx proxy manager for everything or can I run both of the solutions?

    You can definitely run both solutions (tunnel points to npm, npm towards to all other services), and it saves you setting up tunnels for each service

    Now for my 2 cents

    As others have suggested, tailscale funnel is a valid option. A reverse proxy using a VPS is also a valid option. And as I pointed out, doing the CloudFlare tunnel is an option if you’re willing to accept the risk.

    My current setup is using a free Oracle VPS with a small nginx docker container forwarding all port 80 and 443 traffic through a tailscale. On the other end is a nginx proxy manager docker container that points to all my services across the network. I have my CloudFlare details configured in nginx proxy manager to generate a wildcard SSL certificate that I apply to all my local services

    Inside the network, I use adguard to redirect the domain to the local LAN IP of the nginx proxy manager server to avoid traffic going through the internet.

    Then all you need to do is point the domain on CloudFlare dns to the Oracle server, and you’ll have several layers of separation between the internet and your local LAN , as well as SSL certs both internally and externally on any services you share

    It might not be the most elegant setup, but I share my Plex server (as well as about 30 other things) with several other people and can handle multiple 1080p streams going through it without any issue and it’s been nice and stable for over a year without any issues




  • It’s been a while since I used my resin printer, but I had a similar problem at one point and it came down to the support connection to the print… No matter how many supports I put, it didn’t change the outcome, but when I made the support thicker and made the connection point thicker, suddenly I had no more problems… It just meant a little extra post processing on some parts




  • Well the reason I asked about the hotend was because of you’re using the little glass bead version of the thermistor, and the hotend has the hole to feed through, I had an issue on an old Frankenstein ender where it wasn’t touching the metal inside correctly… As it heated up, it would kind of move the thermistor away from the metal. I solved this by putting a DIY metal shroud on it that held it in the middle while touching the hotend all around. I also used thermal paste to make sure there was no gaps.









  • You can do this pretty easily using asterisk and then just point your VoIP clients to it’s IP address

    But…

    Whatever you do, unless you’re an expert with network security, don’t leave it on its default port if you’ll expose it to the internet.

    You’ll have that many bots trying to get in that it’ll DDoS you within a few hours of setting it up. Even if you have it on a different port, you’ll have lots of bots trying to get in.

    If you ever see those “unlimited international calls” cards sold in third world countries for like $5-10, those are mostly hacked VoIP systems that have accounts or access to a phone line