A little help please

Some DNS systems return:

[NOT ns.prs-calarasi.ro]

That's hit or miss.
Your authoritative DNS system is NOT configured correctly.

7 Likes

certbot certificates
Saving debug log to /var/log/letsencrypt/letsencrypt.log


Found the following certs:
Certificate Name: www.prs-calarasi.ro
Serial Number: 35603b62da9c62a4a2c6d73fea3c5a7eb7f
Key Type: RSA
Domains: www.prs-calarasi.ro
Expiry Date: 2023-03-14 12:14:38+00:00 (VALID: 89 days)
Certificate Path: /etc/letsencrypt/live/www.prs-calarasi.ro/fullchain.pem
Private Key Path: /etc/letsencrypt/live/www.prs-calarasi.ro/privkey.pem


That is only one cert.
And it only has one name one it [not both].

7 Likes

perfect
and to the same certificate I want to add the name prs-calarasi.ro
I don't want to issue another certificate
how can I enter the name prs-calarasi.ro in the same certificate?

Certificates can't be modified.
You have to get a new one.

hmm...
Go back in time and get that cert with both names on it - LOL

6 Likes

certbot certonly --non-interactive --agree-tos --nginx -m leo@tvnl.eu -d www.prs-calarasi.ro -d prs-calarasi.ro

Missing command line flag or config entry for this setting:
You have an existing certificate that contains a portion of the domains you requested (ref: /etc/letsencrypt/renewal/www.prs-calarasi.ro.conf)

It contains these names: www.prs-calarasi.ro

You requested these names for the new certificate: www.prs-calarasi.ro, prs-calarasi.ro.

Do you want to expand and replace this existing certificate with the new certificate?

(You can set this with the --expand flag)

Try adding the --expand option as it describes

8 Likes

certbot certificates
Saving debug log to /var/log/letsencrypt/letsencrypt.log


Found the following certs:
Certificate Name: www.prs-calarasi.ro
Serial Number: 3f0c6da22e5b18d8d8f72bafd1b5754bcb2
Key Type: RSA
Domains: prs-calarasi.ro www.prs-calarasi.ro
Expiry Date: 2023-03-14 17:18:22+00:00 (VALID: 89 days)
Certificate Path: /etc/letsencrypt/live/www.prs-calarasi.ro/fullchain.pem
Private Key Path: /etc/letsencrypt/live/www.prs-calarasi.ro/privkey.pem


now I think it's ok
:face_with_monocle: :face_with_monocle: :face_with_monocle: :face_with_monocle: :face_with_monocle: :face_with_monocle: :face_with_monocle: :face_with_monocle: :face_with_monocle:

MikeMcQ
super
you are best of the best
thx
:v: :v: :v: :v: :clap: :clap: :clap: :clap:

2 Likes

everything correct

There may still be a DNS issue...
But obviously that is not something you care about.

7 Likes

does it look good now?
where is reliable DNS checked?

Not from my DNS server :frowning:

Using default root hints, I sometimes get:

prs-calarasi.ro nameserver = ns1-prs-calarasi.ro [217.79.185.18]

And sometimes get:

prs-calarasi.ro nameserver = prs-calarasi.ro [145.53.227.236]

I use this site a lot:
DNS Spy report for prs-calarasi.ro
[but it is not foolproof]

6 Likes
Got answer:
    HEADER:
        opcode = QUERY, id = 2, rcode = NOERROR
        header flags:  response, want recursion, recursion avail.
        questions = 1,  answers = 1,  authority records = 0,  additional = 1
    QUESTIONS:
        prs-calarasi.ro, type = NS, class = IN
    ANSWERS:
    ->  prs-calarasi.ro
        nameserver = prs-calarasi.ro
        ttl = 85946 (23 hours 52 mins 26 secs)
    ADDITIONAL RECORDS:
    ->  prs-calarasi.ro
        internet address = 145.53.227.236
        ttl = 33231 (9 hours 13 mins 51 secs)
------------
Non-authoritative answer:
prs-calarasi.ro
        nameserver = prs-calarasi.ro
        ttl = 85946 (23 hours 52 mins 26 secs)
prs-calarasi.ro
        internet address = 145.53.227.236
        ttl = 33231 (9 hours 13 mins 51 secs)
6 Likes
Got answer:
    HEADER:
        opcode = QUERY, id = 2, rcode = NOERROR
        header flags:  response, want recursion, recursion avail.
        questions = 1,  answers = 1,  authority records = 0,  additional = 1
    QUESTIONS:
        prs-calarasi.ro, type = NS, class = IN
    ANSWERS:
    ->  prs-calarasi.ro
        nameserver = ns1.prs-calarasi.ro
        ttl = 604527 (6 days 23 hours 55 mins 27 secs)
    ADDITIONAL RECORDS:
    ->  ns1.prs-calarasi.ro
        internet address = 217.79.185.18
        ttl = 85354 (23 hours 42 mins 34 secs)
------------
Non-authoritative answer:
prs-calarasi.ro
        nameserver = ns1.prs-calarasi.ro
        ttl = 604527 (6 days 23 hours 55 mins 27 secs)
ns1.prs-calarasi.ro
        internet address = 217.79.185.18
        ttl = 85354 (23 hours 42 mins 34 secs)
6 Likes

@tooponn Are you working with @ctinleonard

Because I thought we already resolved getting the right names in the same cert.

As a note, once a cert is issued it cannot be changed.

7 Likes

Imaging a LE certificate as a "picture".
A "picture" of a certain "group of people" [up to 100 fit into any one shot].
In this case, it was a "picture" of only one "person".
That "picture" was taken many days ago.
Now you want to "edit" that "picture" and add another "person" into it.
A person who was not there.. who wasn't at that place at that time [not in the "picture"].
You will need to take another "picture" [this time with both "people" in it].

7 Likes

As others have pointed out there are DNS issues, this is just so collect into a quick list of results.

  1. DNS Spy report for prs-calarasi.ro
  2. prs-calarasi.ro | DNSViz
  3. DNSSEC Analyzer - prs-calarasi.ro
  4. Zonemaster
2 Likes

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.