I guess I don’t understand. You followed the docker installation directions correctly and it didn’t work or you modified the directions in a way that you prefer and it didn’t work?

I have it installed for a few years now. I started with the AIO but moved to the separate container install after AIO was deprecated. I imagine the install process is too complex for portainer. https://docs.funkwhale.audio/stable/administrator/installation/docker.html

I did steps 1-4 and skipped the rest because I already have a proxy server running. Don’t remember anything related to snapd though. Mine is running in a Debian 11 VM on proxmox instead of an LXC, but the process should be the same. Also they have a matrix channel for help https://matrix.to/#/#funkwhale-support:matrix.org

From what I remember it was relatively painless to install, but upgrading can be a chore, especially this last upgrade. My main interest in FW was the federation aspect as far as finding new music. If you don’t care about federation, maybe a simpler option would work better for you.

Feel free to link us to these abusive communities then since you are making a singular claim yourself.

Yes I watched your video. So many wrong comments from ignorance. And blaming a protocol for the behavior of people? Another commenter here pointed out how Tor could be blamed in the same way. Why not just do away with the internet then? Ridiculous.

Nothing wrong with the matrix spec. I’ve ran a matrix homeserver for several years now and have never had issues with illegal material. It’s free, open source, and self-hostable. If you have an issue with matrix.org that’s a different issue. Don’t use matrix.org servers. In fact, they have made it a point in their literature that they want you to use your own servers, they preach against centralization, and point out that matrix.org is an entryway to get you started, not an endpoint.

At the very least you need to install a webserver and you need a proxy of some kind. If you truly want old school you can just create html pages hosted from the root of your webserver (although there are now easier modern ways to do this, you might learn more the classic way rather than using a CMS).

You will want a reverse proxy to lie between your webserver and the internet that handles SSL. Let’s Encrypt is a good option to generate a cert so that you only expose port 443 on your router to the internet and your webserver. You’ll have to open port 80 to generate the cert but can close it again once generated. Then you will have https.

That’s the basics. The how-to’s are easy to find online.

I’m not sure how soon you need this, but if you can wait sipeed has a $20 kvm with ATX control that should be out soon https://lunar.computer/news/sipeed-announces-new-20-risc-v-kvm-device/