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. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
My domain is:what-makes-a-domain-name-so-memorable-that-you-never-forget-it.sbs
I ran this command:Auto SSL on Hostinger
It produced this output:too long
My web server is (include version):
The operating system my web server runs on is (include version):
My hosting provider, if applicable, is:hostinger
I can login to a root shell on my machine (yes or no, or I don't know):
I'm using a control panel to manage my site (no, or provide the name and version of the control panel):
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):
The fun. part is hostinger provides a free SSL. You don't ask you just get it. I did not for this domain. There was no error message passed to me. In fact nothing comes back. not even their menu for that option. I was told in a chat that the name is over 63 characters. also this is a restriction of the CERT.
So here I am. I have never installed manually and know nothing about it.
Here to learn. It is registered and hosted but not secure.
what-makes-a-domain-name-so-memorable-that-you-never-forget-it.sbs has multiple IP addresses in its DNS records. While they appear to be accessible on the network, we have detected that they produce differing results when sent an ACME HTTP validation request. This may indicate that some of the IP addresses may unintentionally point to different servers, which would cause validation to fail.
[Address=2a02:4780:1d:1c80:ce41:6283:d6a6:ce9,Address Type=IPv6,Server=hcdn,HTTP Status=404] vs [Address=126.96.36.199,Address Type=IPv4,Server=LiteSpeed,HTTP Status=404]
I'm not sure what you're expecting people here to be able to do for you? That sounds like the character length is a restriction on your hoster's side. If all you have is control panel access (instead of a "server" where you can log in and install software), then you would need your hoster's support.
Not all I have. But All I have used. Again I am told--- I have all the support at Hostinger to install my self. I am finding/looking for what I need. Before I do the work, I am asking for the real problem. I told Hostinger it is their problem and as expected they say it is not in their control.so?
This is from Letsencrypt.org
For most people it is better to request Let’s Encrypt support from your hosting provider, or switch providers if they do not plan to implement it.
If you have questions about selecting an ACME client, or about using a particular client, or anything else related to Let’s Encrypt, please try our helpful community forums.
So. Here I am. Learning. Help or complain, Both are good for me?
Sure. And we're happy to help to try to recommend an ACME client to you, we just don't have much to go on to help you. What do you have access to? What is your web server and how do you configure it? There are a lot of questions in the first post that you left blank, and if you don't know the answers to them then neither do we.
Peter, where do you host your website? So I understand your background, I am not running my server. I share on Hostinger servers. Do you run your own server farm? I have run and configured an apache server on my local network for practice. Now I supply the html, php, and user files, Hostinger supplies the hardware and the interface. Which ISP do you use?
If you aren't running a server and are using shared hosting, then getting a certificate is entirely the responsibility of your hoster.
If you're looking at moving from shared hosting to becoming a server administrator, that's a significantly more complicated topic that I don't have the time to try to talk through the various options (what I personally do is pretty convoluted), but I would think that getting a certificate would be one of the easier part of that entire process.
If you're comfortable with shared hosting, but just aren't happy with your current provider, there are plenty of other options out there. I personally don't have a recommendation, but you may want to confirm that they can handle certificates with names that are that long if you really want to use a name that long. As was mentioned earlier, support for long names was only recently added on the Let's Encrypt side, and it may be some time before various clients also support it.
Also www.what-makes-a-domain-name-so-memorable-that-you-never-forget-it.sbs has a CNAME pointing to www.what-makes-a-domain-name-so-memorable-that-you-never-forget-it.sbs.cdn.hstgr.net. as seen in the above image.