One way is to run Pi-hole’s admin interface on a different port. That’s configured in:

/etc/lighttpd/external.conf

Set:

server.port := 8000

Then your URL is http://IP:8000/admin

I worked out this was odd behavior on my OPNSense firewall NAT rules.

For some reason some syncing worked (eg. beehaw.org) but new connections failed. I’m not sure why. Maybe established sessions were kept alive.

Those rules haven’t changed in months and months, so I’ll chalk that up to “weirdness”.

Yeah, I’ve tried that a couple of times too.

And run through all the federation troubleshooting steps in the docs.

I thought that, and in the past I’ve been off for a day or two and always caught up.

This time I haven’t and it’s been a week or two since coming back online.

There’s always a way: https://www.youtube.com/watch?v=VhYEOG9LOIk

I don’t think it’s about lemmy.

https://www.militarytimes.com/news/your-military/2023/07/17/sensitive-us-military-info-exposed-in-accidental-emails-to-mali/

Depends a lot on your existing reverse proxy.

You can read the nginx config that the defaults include and it’s some basic rules to route incoming requests to either lemmy or lemmy-ui. If your existing reverse proxy is nginx you could just incorporate the rules in there.

It also depends on why you need it behind the existing proxy, and how you’ll choose to route your traffic, and where you traffic is coming from in general.

I’d start with taking a look at the default nginx config to see if you can move those rules to your existing reverse proxy, or just forward everything coming in that’s for lemmy straight to the lemmy reverse proxy, although that might be more complicated in correctly preserving the incoming requests.

Many years ago working for a monitoring software company someone had found a bug in the uptime monitoring rules where they reset after a year.

It was patched and I upgraded one client and their whole Solaris plant immediately went red and alerted. They told me to double it to two years and some stuff was still alerting.

They just said they’d try to get around to rebooting it, but it was all stable.

Everywhere else I’ve worked enforces regular reboots.

If you want a reliable provider try Fastmail. Used them for years, very rare outages. I have my local postfix set to relay to them for locally sent mail. Great web UI.

Traditional lox is just brined in salt, no smoking.

Gravadlax is brined in salt and sugar with spices.

Smoked salmon is just smoked salmon, like nova, in the US.

Due to customer preference and lack of knowledge, most want smoked salmon when they ask for lox, so are sold lox.

See: https://forward.com/news/7669/the-raw-truth-about-lox/

Moving to Caseta for lighting from the random mix of bulbs which never quite work was amazing. It’s also much cheaper to put in one controllable switch than replace the 6 bulbs in the light fittings connected to the wall switch. Those bulbs always fail in weird and non-debuggable ways.

I use Crafty Controller (https://craftycontrol.com/) to manage the minecraft servers. It runs in a docker instance and gives you a nice web UI to manage each minecraft server. I use it to delegate control to my kids to create and manage servers as necessary.

Finally, if you’re not using a config mgmt tool, I’d start looking, so you can make everything easily re-doable. Personally I’m using Ansible, but puppet, chef, salt, etc all work too. Ansible is easiest given it does need it’s own infra. I like it so if something dies I can redeploy everything onto a different server.