-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
virtual hosts #18
Comments
What version of OpenSSL/nginx are you using? |
Hey, nginx version: nginx/1.11.9 and \ nginx version: nginx/1.11.9 |
There is also a bug when using TLSv1.3, the CT does not work at all. Firefox reports 0 CT when using TLSv1.3 but does report when using TLSv1.2 this in on the nginx version: nginx/1.11.9 |
The first problem is probably the same issue as #13. I'll take a look at the TLS 1.3 issue. |
Yeah It does look a lot like #13, so this one can be closed, or do you want to to remain open for TLS1.3? Since SSLLabs fails to test TLS1.3 only, Firefox does report back no CT for my domains when it is on TLS1.3 |
Hey,
Thank you for your work on this module, I've come across an issue.
I got this working on a subdomain of mine on with a certificate issued for both root and a number of subdomains, it works fine on the subdomain, but not on the root domain, both share same SSL configuration in nginx only diffs are folders and proxies.
##hmm strange, when I move the commands to enable:
ssl_ct on;
ssl_ct_static_scts /etc/nginx/ssl/sct/;
to /etc/nginx/nginx.conf rather than each site in ../enabled-sites/
It works for all subdomains but not the root domain. any idea why this is?
I have two sites enabled, both share same certificate, while one only responds to apps.mydomain.com other responds to www.mydomain.com and mydomain.com
the lather of which is the only one not reporting back as working with SSL labs like the others "Certificate Transparency Yes (TLS extension)"
The text was updated successfully, but these errors were encountered: