1. Caddy version 2.0.0
2. How I run Caddy:
Running WSL 2 with Ubuntu 20.04. I typically set up local domains for hosting; e.g., kaitlynconcilio.test. The hosts file is configured on the Windows host and a Mac that’s trying to access via the network. The Windows IP address is 192.168.1.22, and connected via bridge/port forwarding to the WSL 2 layer (per [WSL 2] NIC Bridge mode 🖧 (Has TCP Workaround🔨) · Issue #4150 · microsoft/WSL · GitHub) on ports 22, 80, 8080 and 443.
a. System environment:
Windows 10 Build 19041
WSL 2 Ubuntu 20.04
Caddy 2
b. Command:
sudo caddy start
d. My complete Caddyfile or JSON config:
(I am not certain that i have the PHP parts right, but I need to get this working before I can test those)
{
default_sni '192.168.1.22'
local_certs
}
kaitlynconcilio.test
root * /home/kaitlyn/Sites/kaitlynconcilio.com/Public
php_fastcgi unix//var/run/php/php7.4-fpm.sock
file_server
3. The problem I’m having:
When I try to access kaitlynconcilio.test, first the browser complains the certificate is funky (expected). But then it throws a 500 error and says the page isn’t working. On the command line, it outputs
2020/05/26 00:13:58 http: TLS handshake error from 172.30.96.1:57031: remote error: tls: unknown certificate
every time a request comes in, though the port changes.
5. What I already tried:
I tried to forward the port that the TLS handshake was coming through on to see if that would help, but gave up as it’s a large moving target (moved around at least within a range of ~2000 ports).
I tried including the default_sni as advised in one of the other posts about issues with Docker networking; I’m fairly certain the problem has something to do with how the request comes through.
The WSL2 IP address is 172.30.105.91; I assume 172.30.96.1 is the Windows host from the inside, but am not sure how to confirm it. I hope there’s a simple configuration I’m missing somewhere, but I’m worried it’s going to be one of those “WSL2 is a WIP” things that might just have to wait until they get it all straightened out.