Skip to content
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

Let's Encrypt instructions for .pem files? #74

Open
TehDomic opened this issue Mar 18, 2024 · 2 comments
Open

Let's Encrypt instructions for .pem files? #74

TehDomic opened this issue Mar 18, 2024 · 2 comments

Comments

@TehDomic
Copy link

I have generated Let's Encrypt files on a test server, where I have these .pem files to work with:

$ cat ./README

This directory contains your keys and certificates.

`privkey.pem`  : the private key for your certificate.
`fullchain.pem`: the certificate file used in most server software.
`chain.pem`    : used for OCSP stapling in Nginx >=1.3.7.
`cert.pem`     : will break many server configurations, and should not be used
                 without reading further documentation (see link below).

WARNING: DO NOT MOVE OR RENAME THESE FILES!
         Certbot expects these files to remain in this location in order
         to function properly!

We recommend not moving these files. For more information, see the Certbot
User Guide at https://certbot.eff.org/docs/using.html#where-are-my-certificates.

Which of these are compatible/should be used with the various cert/ca/key flags or the software itself of compy?

@TehDomic
Copy link
Author

Info: The certbot Let' Encrypt certificate Key Type is: ECDSA, if that helps explain things.

@TehDomic
Copy link
Author

TehDomic commented Mar 19, 2024

Debugging:
Running compy with these flags as a test:
./compy -cert /etc/letsencrypt/live/<my.domain>/fullchain.pem -key /etc/letsencrypt/live/<my.domain>/privkey.pem

And turning on Proxy Settings in Windows, then trying to access a few websites, returns this message in the test server terminal output:

2024/03/19 00:07:41 compy listening on :9999
2024/03/19 00:09:47 http: TLS handshake error from <IP adress>:****6: tls: first record does not look like a TLS handshake
2024/03/19 00:09:49 http: TLS handshake error from <IP adress>:****7: tls: first record does not look like a TLS handshake

etc
until I shut down the script with Ctrl+C on the server.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant