Booting to a black screen with white text, while functional, really detracts from the more professional experiences that can be had elsewhere. I know the theming support is severely lacking in systemd-boot though (which I believe this is)
Its “OK”, and with Distrobox available it can make it far more usable. My experience with it has been on Bazzite, and it was great for a while but ended up having issues with os-tree a number of times, when the whole promise of being able to rollback to a last known good install didn’t work, I went back to a traditional OS.
No stress, just making sure there wasn’t some other reason for it. Cheers
Had a look at that, sounds pretty cool. Curious to know why you linked to a fork that is out of date and not to the original at https://github.com/BassT23/Proxmox
Cheers I’ll check out Ansible, it been on my lost of things to look at over the years anyway so its a good excuse to dig into it
Thanks for the recommendation, I’ll check it out
Yea that was going to be my next step if I don’t find anything that fits my needs, I’ll make it - but this is a solved problem for sure. I just need the right thing that’s close enough to what I’m looking for.
I tried hard to get into Bazzite, it went really well for a while but I had issues after every update. Most recently something to do with the os-tree got corrupted and refused to boot, ended up having to boot into a live iso to edit some files on the disk.
I will absolutely be trying it again in 6 months because its really good and I’m sure they’ll smooth out those update issues.
Alcohol 120% and Daemon Tools
Harder to prank someone when it highlights it
Frontend validation is for real time user feedback (without hitting the backend constantly) instead of needing to submit the form before throwing an error/warning.
Yea, it takes actual skill to use them ha ha
I actually wish skateboards made a come back. Much more preferable over the escooters I see around a lot.
Get a Steam Deck, and you can press the power button whenever you want to stop playing and it puts the system on standby. Press it again and it powers on in a couple seconds right where you left it.
All good, yea its because I need crowdsec installed on the proxy as well - not just the bouncer - in order to actually send the logs to Opnsense.
I ended up having some weird performance issues so I pulled it all out for now and will revisit another time.
With the bouncer setup, I assume I need to pass in where to look for logs or something for those to be passed into the lapi? I followed this CrowdSec and Nginx Proxy Manager , as far as I can tell everything is connected an running, I have crowdsec running on OpnSense via the plugin - it appears to be healthy as per the CrowdSec Console.
npm | [nginx ] nginx: [error] [lua] crowdsec.lua:62: init(): error loading captcha plugin: no recaptcha site key provided, can't use recaptcha
npm | [nginx ] nginx: [error] [lua] ban.lua:37: new(): BAN_TEMPLATE_PATH and REDIRECT_LOCATION variable are empty, will return HTTP 403 for ban decisions
npm | [nginx ] nginx: [alert] [lua] crowdsec_openresty.conf:5):11: [Crowdsec] Initialisation done
npm | [supervisor ] starting service 'app'...
npm | [app ] [5/5/2025] [11:26:30 PM] [Global ] › ℹ info Using Sqlite: /data/database.sqlite
npm | [supervisor ] all services started.
Cheers, I’ve since discovered that’s is “bouncers” that I want on the endpoints I.e on my Nginx Proxy Manager. I’ll just use the LAPI on the Opnsense box for now I think.
I thought crowdsec does everything fail2ban does in addition to global block lists?
Where did you have it setup? Is your proxy configured to forward the real IP?
I made the switch. It was a good excuse to clean up my config though.
I ended up installing it in a VM initially, just so I could configure it how I needed before going live. Then made a config backup, installed opnsense, then restored the config (after changing the interface names)
I’ll never go back to pfsense.