Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
Its all good it found it, but when i tried to disable ssl3 and added a line i get this from your request with nginx -t
:/etc/nginx/sites-enabled$ sudo nginx -t
nginx: [warn] duplicate value “TLSv1” in /etc/nginx/sites-enabled/batcavelounge.eu:100
nginx: [warn] duplicate value “TLSv1.1” in /etc/nginx/sites-enabled/batcavelounge.eu:100
nginx: [warn] duplicate value “TLSv1.2” in /etc/nginx/sites-enabled/batcavelounge.eu:100
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successfu
I’ve hit the same issue twice now, under similar circumstances.
Let me first state that I have done a thing regarding options-ssl-nginx.conf- no create or edit. Not having a clue to its function, I have no way of invoking it.
But the circumstance of this arising are eerily similar (I have no hard proof as I was not expecting this to happen).
have many server names to handle (19 total).
did an initial certificate with a sub-set of an inital group of 15. Had to set server_names_hash_bucket_size 512;
built up this subset a couple of times.
later as a couple of other domain DNS entries percolated, tried to add another two, and the error arose.
I have little idea how to set server_name directive. I don’t understand why it initially works, Certbot then generates its own block server_name [...].net; # managed by Certbot then complains…