I have solved this before but forgot how. Maybe typing something will help me remember the next time.<\/p>\n\n\n\n
I use Caddy in a docker container to reverse proxy around my docker box and other computers in my network. Something like this:<\/p>\n\n\n\n
# test subdomain\ntest.mydomain.net {\n\n reverse_proxy http:\/\/10.10.10.15:8010\n tls internal\n}\n<\/code><\/pre>\n\n\n\nIt always gives SEC_ERROR_UNKNOWN_ISSUER error and I can just accept this, which works for a while. Ideally you want it to just work, especially if you are setting up a site your 83 year old mum might access.<\/p>\n\n\n\n
I had forgotten that if you want it to work, you need to add the subdomain to your DNS as an A record – and then remove TLS internal. Job done.<\/strong><\/p>\n\n\n\nThis does mean that anyone can hit that domain – which is fine in some cases and not fine in others. So I updated the internal only domains to this:<\/p>\n\n\n\n
fileserver.mydomain.net {\n\n @denied not client_ip 10.10.10.0\/16 172.26.0.0\/12\n\n handle @denied {\n abort\n }\n\n reverse_proxy http:\/\/10.10.10.15:8081\n}\n<\/code><\/pre>\n\n\n\nThe 172.26 address comes from docker and I think it fails without it from memory.<\/p>\n","protected":false},"excerpt":{"rendered":"
I have solved this before but forgot how. Maybe typing something will help me remember the next time. I use Caddy in a docker container to reverse proxy around my docker box and other computers in my network. Something like this: It always gives SEC_ERROR_UNKNOWN_ISSUER error and I can just accept this, which works for … Continue reading Caddy, SEC_ERROR_UNKNOWN_ISSUER and TLS Internal<\/span>