New TLD .ss Help

Help
1

My domain is: registry.nic.ss

I ran this command:

It produced this output:
2019-09-05 19:02:59,707:ERROR:certbot.log:The server will not issue certificates for the identifier :: Error creating new order :: Cannot issue for “registry.nic.ss”: Name does not end in a public suffix
My web server is (include version):

The operating system my web server runs on is (include version):

My hosting provider, if applicable, is:

I can login to a root shell on my machine (yes or no, or I don’t know):
yes
I’m using a control panel to manage my site (no, or provide the name and version of the control panel):
no
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot):

The ccTLD is delegated at IANA… https://www.iana.org/domains/root/db/ss.html

2

I think you’re going to need to wait for the Public Suffix PR to be merged, and once that is done, the updated list needs to get merged into Boulder and released to production.

Probably going to take a couple of weeks.

5 Likes
3

@musyam I'll keep an eye on the PSL pull request and make sure Boulder pulls the required update in.

Indeed, no sooner than Oct 4th in this case. There won't be a release next week.

1 Like
4

At last .ss has been merged to the PSL. https://github.com/publicsuffix/list/pull/882 .

1 Like
5

Thanks! I’ve staged a Boulder pull request: https://github.com/letsencrypt/boulder/pull/4450

1 Like
6

What could be the issue here? Still getting the error:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator standalone, Installer None
Starting new HTTPS connection (1): acme-v02.api.letsencrypt.org
Obtaining a new certificate
An unexpected error occurred:
The server will not issue certificates for the identifier :: Error creating new order :: Cannot issue for “registry.nic.ss”: Name does not end in a public suffix
Please see the logfiles in /var/log/letsencrypt for more details.

Despite the merge above?

7

The new code isn’t deployed to the live servers yet.

3 Likes
8

Thank you…was getting worried.

9

The code is scheduled to be deployed to production on Thursday Oct 3rd.

4 Likes
10

Hi @musyam,

You should now be able to issue for your .ss domain with Let’s Encrypt. Please let me know if you still run into any difficulties.

2 Likes
11

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