So.
Like you said:
root@haproxy01:~# caddy fmt /etc/caddy/Caddyfile
domain.com {
reverse_proxy wordpress01:80
log {
output file /var/log/caddy/log_https_domain.com.log
}
{
debug
}
}
And on the backend.
root@wordpress01:~# caddy fmt /etc/caddy/Caddyfile
localhost
root * /var/www/
log {
output file /var/log/caddy/domain.com.log
}
file_server
And now! Ladies and gentlemen, I have:
The same error like with issue: Fail to start caddy2, not NSS security databases found - #7 by ggilmore
root@wordpress01:~# caddy run --config /etc/caddy/Caddyfile
2020/03/18 03:48:06.001 INFO using provided configuration {"config_file": "/etc/caddy/Caddyfile", "config_adapter": ""}
2020/03/18 03:48:06.002 INFO admin admin endpoint started {"address": "localhost:2019", "enforce_origin": false, "origins": ["localhost:2019"]}
2020/03/18 03:48:06 [INFO][cache:0xc000553cc0] Started certificate maintenance routine
2020/03/18 03:48:06.010 INFO http server is listening only on the HTTPS port but has no TLS connection policies; adding one to enable TLS {"server_name": "srv0", "https_port": 443}
2020/03/18 03:48:06.010 INFO http enabling automatic HTTP->HTTPS redirects {"server_name": "srv0"}
2020/03/18 03:48:06.027 INFO tls cleaned up storage units
2020/03/18 03:48:06.094 WARN pki.ca.local trusting root certificate (you might be prompted for password) {"path": "storage:pki/authorities/local/root.crt"}
run: loading initial config: loading new config: pki app module: start: adding root certificate to trust store: not NSS security databases found
So I will wait for another release I’m thinking.
And hope.
Unless you have an idea.
I will re-open this thread after.
Thanks Francis!