Monkey With A Shell

They’re a part of the mix. Firewalls, Proxies, WAF (often built into a proxy), IPS, AV, and whatever intelligence systems one may like work together to do their tasks. Visibility of traffic is important as well as the management burden being low enough. I used to have to manually log into several boxes on a regular basis to update software, certs, and configs, now a majority of that is automated and I just get an email to schedule a restart if needed.

A reverse proxy can be a lot more than just host based routing though. Take something like a Bluecoat or F5 and look at the options on it. Now you might say it’s not a proxy then because it does X/Y/Z but at the heart of things creating that bridged intercept for the traffic is still the core functionality.

It depends on what your level of confidence and paranoia is. Things on the Internet get scanned constantly, I actually get routine reports from one of them that I noticed in the logs and hit them up via an associated website. Just take it as an expected that someone out there is going to try and see if admin/password gets into some login screen if it’s facing the web.

For the most part, so long as you keep things updated and use reputable and maintained software for your system the larger risk is going to come from someone clicking a link in the wrong email than from someone haxxoring in from the public internet.

I have a dozen services running on a myriad of ports. My reverse proxy setup allows me to map hostnames to those services and expose only 80/443 to the web, plus the fact that an entity needs to know a hostname now instead of just an exposed port. IPS signatures can help identify abstract hostname scans and the proxy can be configured to permit only designated sources. Reverse proxies also commonly get used to allow for SSL offloading to permit clear text observation of traffic between the proxy and the backing host. Plenty of other use cases for them out there too, don’t think of it as some one trick off/on access gateway tool

Zabbix or Cacti are nice ways to draw maps that also serve a functional role in keeping track of the activity and alerting.

Looks like was just updated today pending transfer, so either the owner transferring registrars or someone took it over.

https://www.whois.com/whois/funkwhale.audio

Domain expired on the 19th, so it’s validly offline. Has always seemed to be a low-adoptiom platform, will have to see the status in the next few days.

Exactly, the term has been pretty well claimed by people who host things like, oh say, their own Lemmy service or such.

Self hosted in this context is pretty well aimed at the ‘I do a service on my own time and usually own gear’ crowd. IT for a company is an entirely separate thing. Professional self-hosting would be more on a community like ‘serveradmin’.

It depends on the load on the disk. My main docker host pretty well has to be on the SSD to not complain about access times, but there are a dozen other services on the same VM. There’s some advisory out there that things with constant IO should avoid SSDs to not wear out the read/write too fast, but I haven’t seen anything specific on just how much is too much.

Personally I split the difference and run the system on SSD and host the bulk data on a separate NAS with a pile of spinning disks.

I know some VPN providers have their own DNS service that you can use similar to other filtered public DNS. If you mean an in house DNS/VPN gateway then what you want is probably best served by something like a firewall distro (opnsense/pfsense) to handle both of them.

Been a while since I used proxmox but that’s the nature of a lot of those free/corporate type softwares. The free ‘community’ edition is pretty well a public beta that you can get forum level support for, or sometimes you can get paid support at some limited level.

Lots of them, if you want something large and powerful you could set up security onion, mirror a port and it’ll capture everything plus graph and slice up things all over. Needs a fairly hefty box not to choke if it gets fed a lot though.

https://www.grepular.com/Transparent_Access_to_I2P_eepSites

Something like this makes logical sense, but can’t say I’ve ever tried such a feat. As a general rule though keeping the gateway/firewall free of extraneous software is a good practice just to limit the potential attack surface. If you try it I’d create a dedicated VM somewhere to host the i2p/Tor gateway from to keep it off the network edge directly.

Not sure if you mean to run the service on the FW or what ‘handle’ means here. If you have a second box though it would be easy enough to run all those services on a distinct server and then route their relevant ports through there with a policy based route on the firewall. That way you would only have to set up one for node for example and just have the client machines use that.

Mealie previously, now Homechart. Mealie is probably better suited to the specific purpose, but Homechart includes a mess of other functions.

If you don’t have concerns about it being private I’ve used one of these for similar purposes in the past. Just a little portable DLNA server. The original project stopped but there are forks or the last version of the original out there.

https://en.m.wikipedia.org/wiki/PirateBox

I’m pretty sure it would still work, but images for media content would have broken links. I’m not sure the refresh policy as far as remote media goes but local stuff could be re-uploaded and it should be able to retain things like the user names and comment data even without pictures.

One neat aspect is under the admin options you can hide whole sections of the menu to not show what you don’t need. Makes things a lot less cluttered that way.

https://www.tubearchivist.com/

I’ve liked this one. Let’s you subscribe to channels/playlists and download en-masse if your inclined

Self hosted version of https://homechart.app/

Not FOSS (source available I believe though) but it has the option of a lifetime license rather than a subscription. Dev is readily available and helpful too.