How configure let's Encrypt with tomcat

[MikeMcQ]

@Erica95

What I'm not clear about is why you say there are two blocks and I should delete one of them?
The following block:

server {
if ($host = fantacalciomania.ns0.it) {
return 301 https://$host$request_uri;
} #managed by Certbot

listen 80;
server_name fantacalcalciomania.ns0.it;
return 404; # managed by Certbot
}

certbot created it for me when I ran it.

@Erica95 Adding on to my previous comment ... the server block you show here was not in the config.txt file you uploaded. The above one has a different domain name in the IF statement compared to the name in server_name (which is the right one). Certbot would not do that so must have been manual adjustment. More puzzling is where do you see this because it is not in the current active nginx config you uploaded.

[Erica95]

Being my first experience for me, I would try to do it again and I will let you know; I will reload the config.txt file again. Thank you all in the meantime

[rg305]

Likely something NOT found in:
include /etc/nginx/sites-enabled/*;

What shows:
ls -l /etc/nginx/sites-available/*;

[Erica95]

Hi Mark and all; I promised myself that I would let you know after redoing the procedure.

Now I don't know if I should make a new post because the error is different (you tell me if I have to); however, this time on a company server always in the cloud but with aruba when I execute the command """ sudo certbot --nginx -d example.com -d www.example.com """ the following error appears to me ( ps this time for corporate issues I can not say the real name of the site forgive me last time it was my personal ):

""""

Certbot failed to authenticate some domains (authenticator: nginx). The Certificate Authority reported these problems:
Domain: example.com
Type: unauthorized
Detail: 192.168.0.1: Invalid response from http://example.com.well-known/acme-challenge/68sZr0pCyIL6vhcK08-PmKV-j_XTrMowqmbRQVYJUmU: 404

"""

Before running sudocerbot .nginx -d I added the directive correctly in the nginx file in fact the test "" sudo nginx -t "" gave me an ok result.

The strange thing is that the ip address that let's encrypt tries to contact and tells me "unauthorized" has an address other than 192.168.0.1 (I repeat, these are example addresses).

The dns example.com correctly points to the ip address of the server which is 192.168.1.128 (therefore different from the ip 192.168.0.1 ).

It would seem that the cloud mapping between dns and ip has not been done correctly, but if I type a ping with the dns name it returns the ip address correctly.

However if you want I'll reopen a new post because it's a different problem.

I await your answers

[Erica95]

I did it; I don't know how but redoing the procedure everything went well. In my opinion on the cloud (who takes care of it), they had left an ip associated with the dns name. Now it looks like they fixed it. Let's encrypt works here too