Goofed Home

Just to start off, know that I have zero experience with this. I’m only looking into doing this because I’m absolutely sick and tired of centralised services (in this case Discord) turning to shit, and want to start a Discord-like/alternative federation between my friends.

Prosody seems to be the easiest to set up, and has all the available capabilities for a server that allows Discord-like functionality (text, group voicecall, streaming). Movim is the client that makes use of all that.

But I don’t have a clue how to set up a Prosody server with Podman. I’ve never done this before. I started by downloading the Prosody image through Podman, then tried running it, which prompted the creation of a container. Kept everything at the defaults and tried running it, but it didn’t work.

What do I do from here?

I mean, difficulty is relative mate. I just said I couldn’t get Snikket working (after multiple tries, too) but I’ve spun up both matrix servers. So I’d personally say it’s harder.

I’d be interested in seeing that, or at least knowing which ejabberd container you chose and why.

Hi, c/selfhosted! This is my first post on Fediverse and I am glad to be making it here.

I recently got fed up with having to using Tailscale to access my server at home and decided to expose it publicly. A friend recommended segregating the server into a dedicated VLAN. My router’s stock firmware does not allow that, so I flashed OpenWrt on it (I am amazed how simple and easy the process was).

Getting the router to actually assign an IP address to the server was quite a headache (with no prior experience using OpenWrt), but I managed to do it at the end with a help from a tutorial video on YouTube.

Now, everything is working perfectly fine and as I’d expect, except that all requests’ IP addresses are set to the router’s IP address (192.168.3.1), so I am unable to use proper rate limiting and especially fail2ban.

I was hoping someone here would have an experience with this situation and help me.

Yeah, Tailscale’s “zero-config” idea is great as long as things actually work correctly… But you immediately run into issues when you need to configure things, because Tailscale locks you out of lots of important settings that would otherwise be accessible.

For instance, the WiFi at my job blocks all outbound WireGuard connections. Meaning I can’t connect to my tailnet when I’m at work, unless I tether to my personal cell phone (which has a monthly data cap). Tailscale is built on WireGuard, and WireGuard only. If I could swap it to use OpenVPN or IKEv2 instead, I could bypass the problem entirely. But instead, I’m forced to just run an OpenVPN server at home, and connect using that instead of using Tailscale.

Wow, there’s a lot going on in there.

Hello all,

I figured that a chunk of the selfhost community is using Caddy, so decided to post my query here. I am a novice in Caddy, so I might be saying some incorrect terms.

Some information - The router and the host running Caddy, are different machines - The router page is running HTTP, but I am accessing it via HTTPS through Caddy - Caddy is running via Docker.

I have a couple of services running on a host, so I access them via Caddy’s reverse proxy. Now I am also trying to access my router login via the same reverse proxy. This is what the router entry in the caddyfile looks like

.
.
{
    local_certs
}
login.router.lan {
	reverse_proxy 192.168.1.1:80
}
.
.

With this entry, I can access the login page. However, when I enter the password, I feel like it’s attempting to login but then it just comes back to the original login page. When I access it directly, the login is successful. I also have Pihole running and the Pihole login process works fine. So I suspect that the router login page is expecting some extra information from Caddy to forward it to the login page.

After some searching online and some LLM wrangling, I figured it’s some cookie issue or my login page is expecting a certain host.

What should I add to my Caddyfile so that the login redirect works?

I don’t know how to answer your question. But it might be that your router doesn’t like being access as a url. I know I had to tell mine to accept login.router.net as itself.

I also just want to highlight:

The router and the host running Caddy, are different machines

This means your credentials are being passed in plain text over your network between caddy and the router. This might be OK to you. But wanted to highlight for anyone else reading.

Hello there. I perfectly understand the risks of my setup. Since it’s a commercial off-the-shelf router, i can’t run a reverse proxy on it, so this is the best that i can do (other than VLANs). It’s also a private network, so I guess it’s fine.

I used a bit of my butt which said that such embedded devices don’t work with reverse proxies. Finding which exact parameters as respected by the router will be time-consuming and the end result is not that great.