ssl certificates not in line with nginx-proxy requirement for folder structure

[phill44-source]

I currently have the problem that when I have multiple containers with different virtual(or letsencrypt)-hosts (Domains) all certificates and keys are stored in /etc/nginx/certs// instead of being directly named _cert/_chain/_key.pem. This appears to make the nginx-proxy container not recognize the ssl-certificates and as such writes "# No certificate for this vhost nor default certificate found, so reject SSL handshake." in the default.conf file.
How can I solve this?

[toddhgardner]

This is almost always a VIRTUAL_HOST vs LETSENCRYPT_HOST mismatch. nginx-proxy expects cert files at the root of the certs directory named exactly as the virtual host (example.com.crt, example.com.key). If acme-companion is generating subdirectory paths, the LETSENCRYPT_HOST value on one of your containers doesn't match what nginx-proxy is looking for.
Check that every container with LETSENCRYPT_HOST set also has a matching VIRTUAL_HOST with identical values. Wildcard domains and subdomains are the most common mismatch.

[phill44-source]

Unfortunately, that is not the case. I have let the acme-companion generate completely new certificates after checking that the LETSENCRYP_HOST and VIRTUAL_HOST of both containers that I have are the same. In my case, each container has its own domain

[buchdag]

@phill44-source please provide your full configuration (nginx-proxy container, acme-companion container, proxied container(s)) and the resulting folder structure in /etc/nginx/certs.

[phill44-source]

hey there, sorry for the somewhat late reply.
I have just tried to start my server again only to notice it had suddenly decided not to want to work in a network anymore. So I will try to fix that first.