• 0 Posts
  • 348 Comments
Joined 1 year ago
cake
Cake day: June 30th, 2023

help-circle
  • Nginx Proxy Manager is probably perfect for you.
    Pick a domain (like mylab.home or something), set up your home network to resolve that domains IP as your docker hosts IP.
    NPM will do self-signed certs. So, you will get a “warning, Https is insecure” kinda page when you visit it. You could import NPMs root cert into your OS/browser so it trusts it (or set up an “don’t warn for this domain” or something).

    If you don’t want per-client config to trust it, then you need to buy a domain, use a DNS that supports letsencrypt DNS-challenge, and grab certs that way (means you don’t need a publicly accessible well-known route exposed)







  • VMix popularity exploded during the pandemic. A lot of conferences became a blend of teams/zoom/Google and VMix.

    Might be hardware based like a multi-m/e video mixer (blackmagic make cheap ones), or maybe more of a screen manager (like barco e2, analog way livecore). But, unless there are production requirements, vmix is much more likely. It’s (now) proven, and much cheaper!

    OBS can absolutely do it. There are other open source softwares that can do it.
    I’ve seen people bastardise Resolume into something that looks decent.
    There are some online studio systems so everything you do is virtualized. Streamyard used to be like this, till it was bought by hopin (I think it was hopin)


  • You can do reverse proxy on the VPS and use SNI routing (because the requested domain is in clear text over HTTPS), then use Proxy Protocol to attach the real source IP to the TCP packets.
    This way, you don’t have to terminate HTTPS on the VPS, and you can load balance between a couple wireguard peers so you have redundancy (or direct them to different reverse proxies or whatever).
    On your home servers, you will need an additional frontend(s) that accepts Proxy Protocol from the VPS (as Proxy Protocol packets aren’t standard HTTP/S packets, so standard HTTPS reverse proxies will drop them as unknown/broken/etc).
    This way, your home reverse proxy knows the original IP and can attach it to the decrypted http requests as x-forward-for. Or you can do ACLs based on original client IP. Or whatever.

    I haven’t found a way to get a firewall that pays attention to Proxy Protocol TCP headers, but I haven’t found that to really be an issue. I don’t really have a use case







  • Starting with a pool of all users who use alternative DNS for any reason, users of pirate sites – especially sites broadcasting the matches in question – were isolated from the rest. Users of both VPNs and third-party DNS were further excluded from the group since DNS blocking is ineffective against VPNs.

    Proust found that the number of users likely to be affected by DNS blocking at Google, Cloudflare, and Cisco, amounts to 0.084% of the total population of French Internet users. Citing a recent survey, which found that only 2% of those who face blocks simply give up and don’t find other means of circumvention, he reached an interesting conclusion.

    “2% of 0.084% is 0.00168% of Internet users! In absolute terms, that would represent a small group of around 800 people across France!”

    I wonder how much the court case cost, and if those costs are in anyway likely to be recouped even if all 800 of those convert to a subscription.




  • Yeh, immutable distros… You can install software, it’s just you have to declaratively define what software you want, then apply that as a patch.
    You don’t just apt install cowsay, you have to create a file that defines the installation of cowsay.
    This way, if you have to change how cowsay is installed, you tweak that patch file and reapply it.
    If you have to wipe & reinstall (or get a new computer or whatever) you just apply all your patches, and the system is the same again.