There is no way they connected fiber to router with a freaking phone cord.

Either you misunderstood or they lied but what you need is a standard ethernet cable with the same connection on both ends to connect a router to fiber.

Also if someone is professionally installing hardware they shouldn’t be reusing your existing cables anyway.

You have an XY problem. If what you need is to connect your phillips hue hub then just say that instead.

I setup navidrome but never got around to using it much personally. It seems like a good option for a private collection, but im more about sharing mine these days.

I setup jellyfin with feishin and use finamp on mobile for music.

Im also running the latest alpha of funkwhale which i recommend checking out the stable version for a better impression but the alpha is functional if a bit ugly at the moment. My public service for funkwhale has the most users out of anything else i run so people def seem to like it.

I discovered mstream fairly recently and really like its simplicity.

I have MPD setup to stream as a radio on my homepage.

Overall i mainly just use jellyfin out of convenience because i already use it for shows and movies. But ive tried lots of dedicated music options and every subsonic fork still in existence, i keep coming back to jellyfin though.

I think if you already have jellyfin working navidrome isnt really as useful unless you dont like the way jellyfin handles music (wich objectively jellyfin isnt the best interface for music). Its not really that much extra overhead though tbh so you shouldnt hesitate to give it a try if you want to. Really anything thats just focused on audio streaming isnt going to add much overhead.

And the rest of the world ruled that piracy is officially cool again.

In that case you would need to add the peers to the wireguard node you have running in the home lab as well. Wireguard can route peer to peer and will take the shortest path available to it.

That said, i highly recommend first getting things working in a “spoke and hub” style wireguard configuration with either your homelab or the vps as a central peer, then add peers as endpoints after you have everyone with working connections to the central peer. Its just a heck of a lot easier to trouble shoot and get your head around thatway.

deleted by creator

sounds like you had a nfo file which when you doulbe clicked it opened “system information” because windows doesnt recognize nfo as a text file.

There is nothing sketchy about unzipped files, its zips with passwords you gotta watch out for. The nfo thing is just your system doesnt have an nfo viewer, you can search one up or just use notepad to open them if you want.

A central wireguard peer on your vps, connect home to vps and direct the wireguard. Add friends as peers on the VPS like such:

[Interface]
Address = 10.0.0.1/24
ListenPort = 51820
PrivateKey = <VPS_PRIVKEY>

# Home
[Peer]
PublicKey = <HOME_PUBKEY>
AllowedIPs = 10.0.0.2/32

# Friend
[Peer]
PublicKey = <CLIENT_PUBKEY>
AllowedIPs = 10.0.0.3/32

Use iptables to Split tunnel traffic

For the home network ip route add 192.168.1.0/24 via 1. 0.2 dev wg0

And for the vpn To route google a .d such

Enable NAT for clients

iptables -t natw POSTROUTING -s 10.0.0.0/24 -o eth0 -j MASQUERADE

You can set the iptables rules to run wjen it comes up

Forgive my formatting. Mobile clients being janky

It sounds like you’ve got the right plan. I use Anubis and fail2ban along with some manual rules on nginx to block AI bots. In my experience Anubis helps a lot, and you can monitor nginx logs over time to for scans and such to make additional ban rules on.

Graphene does that if you use the wrong finger 5x in a row, I do wish you could lower the number though.

Any VPN worth using would provide their own DNS service