Turns out it was a content update that caused the driver to crash but the update itself wasn’t a driver (as per their latest update.)
Mastodon: @SeeJayEmm@noc.social
Turns out it was a content update that caused the driver to crash but the update itself wasn’t a driver (as per their latest update.)
Is feel a lot better about this if it was a “supporter” tag not this “unlicensed” crap.
I was really hoping this was going to be a rant about clouds in the sky.
That’s the business ed not the community. There’s no limit in aware of in the community ed
Wiki.js Nginx Proxy Manager.
Enough people have already commented on the “proxy at the vps solution”. Another option is to configure routing and nat on the VPS and have it route over the wg tunnel.
Requires you to have postup/predown scripts that modify your routing tables on the wg endpoint.
I made the plunge about a year ago. Spectrum assigns me a prefix but routing was spotty at best. In the end after all the troubleshooting pointed to the problem being the ISP I gave up and stuck with what works, IPv4.
I mean, if you spent the kind of scratch on an android phone you would on an iPhone and then not fuck around with it, you’d have a similar experience on Android.
Years ago I used to flash roms and generally tinker until I decided I needed my phone to be stable and stopped. My Note 20 is polished and stable, no complaints.
My wife has always had iPhones. I’ve used both and find iOS frustrating. These days, unless you’re scraping the bottom of the barrel, it’s mostly about comfort and preference.
DDOS protection is going to depend on the VPS. But for most services you could spin up a pretty lean Debian vm running a proxy like nginx proxy manager and run that over the tunnel. Something like opnsense seems like overkill.
Even with an outlet who wants to slow charge a plug-in EV? The infrastructure isn’t there and the cars are too expensive.
Yes to all of that.