My ISP blocks the ports needed for mail hosting :/
Pretty sure I'd have to go through them to get the rdns PTR records pointed at my domain too. PITA
Darkassassin07
joined 2 years ago
Can always go with RGB and pick colours on demand. I just like the color red. Blue light wakes/keeps me up.
I have RGBW tape on the underside of my kitchen cabinets, inside some nice tracks to keep them out of direct line of sight. White during the day for counter top lighting; red at night for nightlighting that doesn't wake you up when you go for a late night snack. And random disco colours for parties, just because...
Red LED tape on the underside of my desk, dresser, and shelves. Keeps a nice dull red glow in my room, just enough to see around, but low enough that I can sleep through it. Smart plug for scheduling.
There's a lava lamp on a smart plug that turns itself on ~1hr before I go to bed (so it's movin and groovin by the time I'm in there). It'll also turn off after 8hrs regardless of whether it was turned on manually/automatically. Saftey/longevity of the lamp.
Finally a regular bedside lamp, with a dimmable smart bulb.
The smart controls let me set schedules so the desired lights come on as I'm going to bed or with my morning alarm, and making sure that they're off when I leave for work. Plus I can turn them on/off or set brightness from my phone without getting up from bed.
Trump admin goes scorched Earth on senator going to El Salvador to release wrongfully deported immigrant
Judge rules against Trump admin after it abandons fraud accusations it made toward clean energy program | CNN
Actually it looks like Caddy is supposed to set those automatically (I'm used to Nginx which doesn't).
You'll have to look at why the upstream isn't accepting them then. I'm not familiar with azuracast.
In the last couple of weeks, I've started getting this error ~1/5 times when I try to open one of my own locally hosted services.
I've never used ECH, and have always explicitly restricted nginx to TLS1.2 which doesn't support it. Why am I suddenly getting this, why is it randomly erroring, then working just fine again 2min later, and how can I prevent it altogether? Is anyone else experiencing this?
I'm primarily noticing it with Ombi. I'm also mainly using Chrome Android for this. But, checking just now; DuckDuckGo loads the page just fine everytime, and Firefox is flat out refusing to load it at all.
Firefox refuses to show the cert it claims is invalid, and 'accept and continue' just re-loads this error page. Chrome will show the cert; and it's the correct, valid cert from LE.
There's 20+ services going through the same nginx proxy, all using the same wildcard cert and identical ssl configurations; but Ombi is the only one suddenly giving me this issue regularly.
The vast majority of my services are accessed via lan/vpn; I don't need or want ECH, though I'd like to keep a basic https setup at least.
Solution: replace local A/AAAA records with a CNAME record pointing to a local only domain with its own local A/AAAA records. See below comments for clarification.
view more: next ›
I really don't like the idea of every device automatically having a publicly reachable IP.
There's certainly situations where that would be nice; but I'm quite fond of most equipment and services being behind a router and it's firewall, requiring explicit configuration to be exposed to the open net.
Nobody outside my home network ever needs access to my toaster... (btw, why tf is my toaster wifi enabled...?)