How do you set up Caddy for homelab, with no domain

I’ve been trying to set up Caddy as reverse proxy for docker containers in my home lab. This means no domain, dns etc at this point. Caddy itself is running in the container. I can’t figure it out - each time I get SSL_ERROR_INTERNAL_ERROR_ALERT in the web browser.

I’ve tried a couple of Caddyfile variants with no luck. Here’s current one:

191.168.1.191 {
	tls internal 
	reverse_proxy semaphore:3000 {
		transport http
	}
}

How do you make it work?
I can access it without Caddy, by going directly to port 3000 on http.

With that config, Caddy is listening for requests on https://191.168.1.191, i.e. port 443 (HTTPS port).

Please fill out the help topic template as per the forum rules.

2 Likes

ok, but that’s not working - I’m clearly doing something wrong.

So let me rephrase the question - can I use https and make Caddy auto generate certs when there’s only IP address available, no domain? If yes - how?

Possibly with reverse proxy - as I wish to point to specific container and wish to isolate direct access to it via reverse proxy.

You didn’t actually show what’s not working. Please fill out the help topic template as per the forum rules. Show evidence of the problem. Show logs, example curl -v request, etc.

2 Likes

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.