due to it missing ideal features

what features do you want? kindly elaborate

XMPP with Snikket could be an easy solution. If you don’t want to talk to the wider web make sure to disable federation.

It’s entirely possible. If the 2 domains are different, you should look into SNI routing using the TCP router instead of HTTP. With the tls.passthrough flag, encryption is kept intact until it reaches the second proxy.

Pihole runs on dnsmasq right? Maybe you could create a cronjob to copy the underlying dnsmasq.conf to other Piholes

Ah, I see. Well I’m glad you found PiHole useful and stick to using it anyhow!

What issues did you have reverse-proxying? For me it was just as simple as pointing to port 5380. Other ports like 53 could be passed on with a layer-4 router

What about the login issues? I’d hope they’ll be integrating with OIDC or some other auth mechanism, but for now managing 2FA creds should make do

Off the top of my head:

• Allows using DoH/DoT/DoQUIC/recursive upstreams without installing extra packages (unbound, cloudflared, etc)
• Allows acting as a DoH/DoH3/DoT/DoQUIC server alongside normal DNS over UDP and TCP
• Allows configuring SOCKS/HTTP proxies for forwarders
• Act as authoritative zone server with DNSSEC signing
• Allows custom responses via plugins (e.g. conditional responses based on client’s IP addresses)
• Accept PROXY Protocol to forward client IPs from trusted load balancers
• All the clustering and zone transfers magic
• DNS64

It really dives deep into the inner workings of DNS and does pretty much anything Pi-Hole does, with many more security and QoL features. Although the UI may feel a bit dated, I’d recommend it to anyone running their own homelab infrastructure beyond just adblocking

Just found out someone else has a similar thing too:

https://github.com/juhovh/tailguard

It seems more flexible and can be used site-to-site, for anyone interested

Thanks for posting this here. I’m not sure what to think about this, just set up mkdocs-material with huge customizations, including the macros plugin and tons of CSS. So it’d be tedious to eventually migrate to the new “component system” as they say.

Welp, should’ve gone with a barebone SSG and configured what I want. Feels like I’m kinda stuck in no man’s land now.

I find it odd that a report for the proprietary Github platform takes the newsletter’s spotlight, it’s not very relevant. I’d much prefer if the writer could expand his thoughts on those new version releases or featured blogposts, especially the ones he finds interested in.

If it ain’t broke, don’t fix it. I think it’s better hooking up Element Call to your current setup, and remove Element Web if you can BYO client.

For a more lightweight alternative, I personally find continuwuity to be reasonably stable for the specs you mentioned. It does admin tasks in an #admins room, use an embedded database, and has no client UI so less containers needed. So continuwuity + EC should be able to run under the constraints you mentioned

The lightest would still be any XMPP server, though its functionality does differ from Matrix overall

To make it even simpler, apk -U upgrade

Hi,

The client IP problem is a longstanding issue in podman’s virtual bridge networks.

As a workaround I’d run HAProxy rootless, using the pasta networking mode as that one allows seeing native client IP. With pasta’s -T flag (see docs) I’d forward traffic to another caddy container binding to 127.0.0.1:8080 or something similar.

This would coincide with your firewalld/HAProxy port-forwarding setup, but it has more rootlessness to it. It’s still not perfect and you’d still need to tweak sysctls, but I hope it may be useful

You’ll need a TURN server to relay calls and provide signalling capabilities, which is needed most of the time. Here’s Synapse docs on it, and I’ll probably use coturn:

https://element-hq.github.io/synapse/latest/turn-howto.html

There’s also this new technology called Element Call, which uses a diffent tool called LiveKit. You should check it out too

https://github.com/element-hq/element-call/blob/livekit/README.md

You should add your DNS forwarder as its own node in Tailscale, and configure the tailnet to resolve DNS through it. That way you’ll be able to resolve both MagicDNS node names and your local domains, as well as being blocklist-enabled. Besides, I think you can also define custom A/AAAA records on your Tailscale console, skipping local records on Pi-hole altogether.

I’d also recommend Technitium for a new DNS solution, mainly because they’re going to add support for clustering soon. This could be highly useful if you want to configure blocklists once and sync them between different Technitium nodes. Should it works out, I’m thinking of installing it alongside every Tailscale exit node, for the benefit of synced blocklists, local domains, and exit-node geolocated IPs for external domains.

Missed the chance to call it Jelloseerr

It’s Jellover now

Rsync depends on OpenSSH, but it definitely isn’t SFTP. I’ve tried using it against an SFTPGo instance, and lost some files because it runs its own binary, bypassing SFTPGo’s permission checks. Instead, I’ve opted for rclone with the SFTP backend, which does everything rsync do and is very well compliant.

In fact, while SFTPGo’s main developer published a fix for this bug, he also expressed intention to drop support for the command entirely. I think I’m just commenting to give a heads up for any passerby.

Hi, I think OP wants their sibilings to directly connect to their PC, skipping any relays, even if it’s their VPS.

But if you are comparing setting up your own VPS instead of relaying through Tailscale’s DERP, then the answer is… it depends on the distance and whether you can establish VPS->Local VM direct connections.

I found opening a specified port for Tailscale on the VPS to help with direct connections with CGNAT’d peers. I’m not familiar with Pangolin, but I think the same principle applies as long as at least one address:port combination is agreed between Wireguard peers.

If I’m being honest though, before doing all this, try asking your ISPs for IPv6 to avoid these cumbersome things together.

If both your Jellyfin server and your siblings are behind residential CGNAT, then high chance your connections are relayed through Tailscale’s DERP servers. You can check with tailscale ping-ing your sibilings’ nodes.

If this is the case, you may consider selfhosting your own DERP somewhere close to you, but I’d argue the performance gains are minimal compared to the extra costs. Another solution would be to enable IPv6 for both you and your siblings, skipping NAT traversal. I just hope both ISPs support it and support it properly in $CURRENT_YEAR.

This is all assuming you can direct play (i.e. not transcoding) your media. If you’re transcoding, then it’s good to look into hardware acceleration like the other comment mentioned, too

try adding the sysctls parameters to your docker container too

Is there a way for a Wireguard peer to advertise AllowedIPs similar to Tailscale’s subnet routings? If that’s right, perhaps you can configure your host’s address as one of the AllowedIPs on the OpenWRT peer, and skip port forwarding too