Check my Caddyfile

Help
1

1. My Caddy version (caddy version):

v2.0.0-rc.3 h1:z2H/

d. My complete Caddyfile or JSON config:

{
	email email@domain.com
#	acme_ca https://acme-staging-v02.api.letsencrypt.org/directory
}

(local_only) {
        @local_subnets {
                not remote_ip 192.168.2.1/24
        }
        respond @local_subnets 403
}

subdomain1.example.com {
    reverse_proxy 192.168.2.100:6789
	import local_only
}

subdomain2.example.com {
    reverse_proxy 192.168.2.154:8084
	import local_only
}

3. The problem I’m having:

I am rather new to all of this, I’ve been reading as much as I can. I’ve cobbled together a basic Caddyfile. All I really want to be able to do is map internal IP:ports to a domain so they are grouped more logically and I don’t have to worry about remembering ports. I like the idea of a TLS certificate so i don’t get browser warnings. Am I missing anything important? The way I understand how I’ve got it laid out is it should only allow me to access from inside my LAN as defined by the snippet - which is fine, I don’t particularly need external access.

2

Yeah, that looks fine to me!

It all really depends on what each service you’re proxying to needs to work effectively. If it’s working for you now, you’re probably good to go! :+1:

3

Awesome, thanks. I was worried I was missing some glaring security setting or something. Trying to keep things streamlined for now - I can always add more as needed down the road.

4

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