Originally created by @dannietjoh on GitHub (Jan 7, 2018).
The chain.pem and fullchain.pem (with and without timestamp) include a blank line and url, making my webserver (nginx) not like them, is this intentional?
here is an example fullchain.pem:
`-----BEGIN CERTIFICATE-----
MIIF/TCCBOWgAwIBAgISAxNTsyrquKu00NNY0jYD+FGyMA0GCSqGSIb3DQEBCwUA
....
-----END CERTIFICATE-----
Originally created by @dannietjoh on GitHub (Jan 7, 2018).
The chain.pem and fullchain.pem (with and without timestamp) include a blank line and url, making my webserver (nginx) not like them, is this intentional?
here is an example fullchain.pem:
`-----BEGIN CERTIFICATE-----
MIIF/TCCBOWgAwIBAgISAxNTsyrquKu00NNY0jYD+FGyMA0GCSqGSIb3DQEBCwUA
....
-----END CERTIFICATE-----
http://cert.int-x3.letsencrypt.org/
-----BEGIN CERTIFICATE-----
MIIEkjCCA3qgAwIBAgIQCgFBQgAAAVOFc2oLheynCDANBgkqhkiG9w0BAQsFADA/
.....
-----END CERTIFICATE-----
`
Yes this is intentional and shouldn't result in any problems, there probably is a different reason why your nginx doesn't "like" the certificates (bad permissions? missing semicolon in nginx config? etc.).
If removing (and readding, just to make sure) the url changes anything, please report which version of nginx you are using and which ssl library it's linked against.
@lukas2511 commented on GitHub (Jan 7, 2018):
Yes this is intentional and shouldn't result in any problems, there probably is a different reason why your nginx doesn't "like" the certificates (bad permissions? missing semicolon in nginx config? etc.).
If removing (and readding, just to make sure) the url changes anything, please report which version of nginx you are using and which ssl library it's linked against.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @dannietjoh on GitHub (Jan 7, 2018).
The chain.pem and fullchain.pem (with and without timestamp) include a blank line and url, making my webserver (nginx) not like them, is this intentional?
here is an example fullchain.pem:
`-----BEGIN CERTIFICATE-----
MIIF/TCCBOWgAwIBAgISAxNTsyrquKu00NNY0jYD+FGyMA0GCSqGSIb3DQEBCwUA
....
-----END CERTIFICATE-----
http://cert.int-x3.letsencrypt.org/
-----BEGIN CERTIFICATE-----
MIIEkjCCA3qgAwIBAgIQCgFBQgAAAVOFc2oLheynCDANBgkqhkiG9w0BAQsFADA/
.....
-----END CERTIFICATE-----
`
@txr13 commented on GitHub (Jan 7, 2018):
That’s as expected. NGINX handles it okay for me...
@lukas2511 commented on GitHub (Jan 7, 2018):
Yes this is intentional and shouldn't result in any problems, there probably is a different reason why your nginx doesn't "like" the certificates (bad permissions? missing semicolon in nginx config? etc.).
If removing (and readding, just to make sure) the url changes anything, please report which version of nginx you are using and which ssl library it's linked against.