‍fuchsiaaaaaaaaaaaaaaaaa @f0x@pixie.town

it wasn't dnd in the end, as one person couldn't make it. we still hung out virtually and played games, was nice

@pastelpunkbandit@hellsite.site hi has anyone solved this yet

that would be an interesting tune..

oof i almost forgot dnd night :))) but it's online dnd night again :))))

you've heard about "My Drunk Kitchen" but what about My Drunk Hardwarelab

@dragon @haskal yes, incoming would be handled by the iptables portforward rule in that case, directing all incoming traffic on 80/443 to your homeserver, over the tunnel

@amandag@tech.lgbt @haskal iwi

@dragon @haskal if you really just want it to push traffic both ways, you only need wireguard + (iptables) portforward

@haskal @dragon without the reverse proxy you would have to port-forward to the homeserver's port 80/443 and uhh that sucks (fuck iptables) :p
also that way you can have the vps nginx itself listen on 80/443 so some sites/paths are handled by the vps and some reverse proxied onto the homeserver

but as haskal mentions that's the tradeoff, with a setup like that all traffic has to be decrypted on the vps

@dragon as i run pixie.town to a setup like that, here's what I do to prevent that:

- wireguard (vpn software) to make a tunnel between vps and server at home
- server has all outgoing traffic going through that vpn
- nginx runs on vps, reverse proxy to the internal wireguard interface IP for the homeserver (something like 10.0.0.2)

@dragon with just a reverse proxy the outgoing fedi connections would happen from your house

@thufie get that bread!!

@AllNyaNoBite@notbird.site trying to decide if a self-boost counts as strike 3

i think im pretty good on track boosting the flote feline every day, i hope it still cheers people up

@garfiald pff, i guess most just read over it as a typo

@Anarkat@hackers.town art degrees are the best, just pissing yourself off

@erikk@chaos.social hmmm, right, interesting