Can’t obtain certificate for *.tk domain

Hi there,

I’m trying to obtain a certificate for the domain, but I am receiving the following message:

Certificate signature failed. If you supplied your own CSR make sure the domains on it match what you put on SSLForFree. If there is a rate limiting error at the end of this paragraph certificates per Domain is currently 5 per 7 days. Try asking Lets Encrypt to increase the limit or wait 7 days. Rate limits should increase in the near future. { "type": "urn:ietf:params:acme:error:malformed", "detail": "Error finalizing order :: policy forbids issuing for: """, "status": 400 }

I was previously able to obtain a working certificate for these domains without issue. I need a new certificate as I am using a new server. Were *.tk domains blacklisted?

If it helps, I am using the website, which I previously used to obtain a Let’s Encrypt certificate without issue.

Looks like a stray quotation mark was accidentally entered into the domain field at and that confused it.


Please try again and remember to double-check that the domains are entered correctly before proceeding to verification.


@sevenbits use this URL to try again. (Will save you from entering domains)

So, it looks like the issue was a result of trying to use my own CSR. I generated my own 4096-bit private key and then derived a CSR from that key, which failed with the above error. But it works when I have the website generate the private key and CSR for me.

Hi @sevenbits,

What command/process did you use to generate the CSR? I bet that you accidentally included a subject alternate name or a subject common name that had the two domains improperly concatenated.

If you share how you made the CSR its likely we can help fix it to work with

1 Like

2 posts were split to a new topic: Help with a .tk site

I generated the CSR with the standard Linux openssl commands. I don’t recall the exact commands, but I generated a 4096-bit RSA kit and then created a CSR from that key. The common names on the CSR were and

It sounds like it inadvertently contained one Common Name field with the invalid name "".

You should put one of the names in the Common Name, and then both names, individually, in the Subject Alternative Names list. (Leaving the Common Name out may also work, I don't remember.)

Unfortunately openssl makes this a hassle. You can use a command along the lines of this post:

1 Like

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