Please DON'T use both in the same block.
That creates the:
If I use the listen 80;
it will still redirect to https?
NO.
And that is NOT done by adding listen 443;
Where did this directive come from?
the directive comes from a example.conf
template.
As I, probably not, remember correctly both where uncommented, 2 days ago:
listen 80;
listen 443;
I was able to create a secure, https, connection.
Unlikely; as the code doesn't contain the files need to create a secure connection.
Please stick to the KISS plan.
Step #1 Get HTTP working - that means only use port 80 (for now)
@rg305 I will dive into KISS.
Step #1 HTTP is working now.
Thnx for helping me, so far
Could you please tell me what files are you pointing to, and am I missing, to create a secure connection?
For those files, please show the output of:
certbot certificates
But we are getting ahead of ourselves (order matters).
Now on to...
Step #2: obtain certs for the HTTP sites needing HTTPS (that's all of them in my book)
[So let's see what you got (command above) and compare that to what you need]
sudo certbot certificates
output:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Found the following certs:
Certificate Name: sup.supgezel.nl
Domains: sup.supgezel.nl www.sup.supgezel.nl
Expiry Date: 2021-09-13 18:58:52+00:00 (VALID: 88 days)
Certificate Path: /etc/letsencrypt/live/sup.supgezel.nl/fullchain.pem
Private Key Path: /etc/letsencrypt/live/sup.supgezel.nl/privkey.pem
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
I don't have any certs for the main domain?
I did create this cert, as a subdomain.
I might have deleted my main domain certs by running sudo certbot delete
2 days ago
Then it's time to get that cert.
And maybe shoot for having cerbot create the HTTPS vhost config (all-in-one).
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.