I can't get it to work not sure what is wrong


#1

The best command seems like this:

root@ICS32:~/letsencrypt# ./letsencrypt-auto install --apache --cert-path /etc/letsencrypt/live/XXXX.XX/cert.pem --key-path /etc/letsencrypt/live/XXXX.XX/privkey.pem --chain-path /etc/letsencrypt/live/XXXX.XX/chain.pem

Don’t want to show my URL so put XXXX.XX in it’s place.

This command looks like it makes another Virtual Server for post 443 and I put my URL for Server Name in it.

But when I go to https://XXXX.XX it don’t work.

Guess they still have a lot of work to do on it still in Beta.

This is running on a home server with a open port to it. I even open pot 443 to it. Still don’t work. I can still get to it with out the https just http.

-Raymond Day


#3

Is this good showing information? In Webmin System Information and I blocked out my URL hostname.

Or trying to install it with this command my show good info. ./letsencrypt-auto --verbose

I replace my URL with XXXX.XX in this verbose text of installing it. All so took out some repeating things to make post smaller.

root@ICS32:~/letsencrypt# ./letsencrypt-auto --verbose
Updating letsencrypt and virtual environment dependencies…
Requirement already up-to-date: setuptools in /media/256SSD/root/.local/share/letsencrypt/lib/python2.7/site-packages
Requirement already up-to-date: pip in /media/256SSD/root/.local/share/letsencrypt/lib/python2.7/site-packages
Requirement already up-to-date: letsencrypt in /media/256SSD/root/.local/share/letsencrypt/lib/python2.7/site-packages
Requirement already up-to-date: letsencrypt-apache in /media/256SSD/root/.local/share/letsencrypt/lib/python2.7/site-packages
Requirement already up-to-date: zope.interface in /media/256SSD/root/.local/share/letsencrypt/lib/python2.7/site-packages (from letsencrypt)
Requirement already up-to-date: setuptools in /media/256SSD/root/.local/share/letsencrypt/lib/python2.7/site-packages (from letsencrypt)
Requirement already up-to-date: python2-pythondialog>=3.2.2rc1 in /media/256SSD/root/.local/share/letsencrypt/lib/python2.7/site-packages (from letsencrypt)
Requirement already up-to-date: PyOpenSSL in /media/256SSD/root/.local/share/letsencrypt/lib/python2.7/site-packages (from letsencrypt)
Requirement already up-to-date: requests in /media/256SSD/root/.local/share/letsencrypt/lib/python2.7/site-packages (from letsencrypt)
Requirement already up-to-date: ConfigArgParse in /media/256SSD/root/.local/share/letsencrypt/lib/python2.7/site-packages (from letsencrypt)
Requirement already up-to-date: parsedatetime in /media/256SSD/root/.local/share/letsencrypt/lib/python2.7/site-packages (from letsencrypt)
Requirement already up-to-date: configobj in /media/256SSD/root/.local/share/letsencrypt/lib/python2.7/site-packages (from letsencrypt)
Requirement already up-to-date: pytz in /media/256SSD/root/.local/share/letsencrypt/lib/python2.7/site-packages (from letsencrypt)
Requirement already up-to-date: psutil>=2.1.0 in /media/256SSD/root/.local/share/letsencrypt/lib/python2.7/site-packages (from letsencrypt)
Requirement already up-to-date: six in /media/256SSD/root/.local/share/letsencrypt/lib/python2.7/site-packages (from letsencrypt)
Requirement already up-to-date: cryptography>=0.7 in /media/256SSD/root/.local/share/letsencrypt/lib/python2.7/site-packages (from letsencrypt)
Requirement already up-to-date: zope.component in /media/256SSD/root/.local/share/letsencrypt/lib/python2.7/site-packages (from letsencrypt)
Requirement already up-to-date: mock in /media/256SSD/root/.local/share/letsencrypt/lib/python2.7/site-packages (from letsencrypt)
Requirement already up-to-date: acme==0.0.0.dev20151104 in /media/256SSD/root/.local/share/letsencrypt/lib/python2.7/site-packages (from letsencrypt)
Requirement already up-to-date: pyrfc3339 in /media/256SSD/root/.local/share/letsencrypt/lib/python2.7/site-packages (from letsencrypt)
Requirement already up-to-date: python-augeas in /media/256SSD/root/.local/share/letsencrypt/lib/python2.7/site-packages (from letsencrypt-apache)
Requirement already up-to-date: idna>=2.0 in /media/256SSD/root/.local/share/letsencrypt/lib/python2.7/site-packages (from cryptography>=0.7->letsencrypt)
Requirement already up-to-date: pyasn1>=0.1.8 in /media/256SSD/root/.local/share/letsencrypt/lib/python2.7/site-packages (from cryptography>=0.7->letsencrypt)
Requirement already up-to-date: enum34 in /media/256SSD/root/.local/share/letsencrypt/lib/python2.7/site-packages (from cryptography>=0.7->letsencrypt)
Requirement already up-to-date: ipaddress in /media/256SSD/root/.local/share/letsencrypt/lib/python2.7/site-packages (from cryptography>=0.7->letsencrypt)
Requirement already up-to-date: cffi>=1.1.0 in /media/256SSD/root/.local/share/letsencrypt/lib/python2.7/site-packages (from cryptography>=0.7->letsencrypt)
Requirement already up-to-date: zope.event in /media/256SSD/root/.local/share/letsencrypt/lib/python2.7/site-packages (from zope.component->letsencrypt)
Requirement already up-to-date: funcsigs in /media/256SSD/root/.local/share/letsencrypt/lib/python2.7/site-packages (from mock->letsencrypt)
Requirement already up-to-date: pbr>=0.11 in /media/256SSD/root/.local/share/letsencrypt/lib/python2.7/site-packages (from mock->letsencrypt)
Requirement already up-to-date: ndg-httpsclient in /media/256SSD/root/.local/share/letsencrypt/lib/python2.7/site-packages (from acme==0.0.0.dev20151104->letsencrypt)
Requirement already up-to-date: werkzeug in /media/256SSD/root/.local/share/letsencrypt/lib/python2.7/site-packages (from acme==0.0.0.dev20151104->letsencrypt)
Requirement already up-to-date: pycparser in /media/256SSD/root/.local/share/letsencrypt/lib/python2.7/site-packages (from cffi>=1.1.0->cryptography>=0.7->letsencrypt)
Running with virtualenv: /root/.local/share/letsencrypt/bin/letsencrypt --verbose
lqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqk
x Saving debug log to /var/log/letsencrypt/letsencrypt.log x
x x
mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj

lqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqk
x This is a PREVIEW RELEASE of a client application for the Let’s x
x Encrypt certificate authority and other services using the ACME x
x protocol. The Let’s Encrypt certificate authority is NOT YET ISSUING x
x CERTIFICATES TO THE PUBLIC. x
x x
x Until publicly-trusted certificates can be issued by Let’s Encrypt, x
x this software CANNOT OBTAIN A PUBLICLY-TRUSTED CERTIFICATE FOR YOUR x
x WEB SERVER. You should only use this program if you are a developer x
x interested in experimenting with the ACME protocol or in helping to x
x improve this software. If you want to configure your web site with x
x HTTPS in the meantime, please obtain a certificate from a different x
x authority. x
x x
x For updates on the status of Let’s Encrypt, please visit the Let’s x
x Encrypt home page at https://letsencrypt.org/. x
x x
tqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqu
x x
mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj

lqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqk
x Which names would you like to activate HTTPS for? x
x lqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqk x
x x [*] XXXX.XX x x
x x x x
x x x x
x x x x
x x x x
x x x x
x x x x
x mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj x
x x
x x
x x
x x
x x
x x
tqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqu
x < OK > x
mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj

lqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqk
x Saving debug log to /var/log/letsencrypt/letsencrypt.log x
x Starting new HTTPS connection (1): acme-staging.api.letsencrypt.org x
x x
x x
x x
x x
x x
x x
x x
x x
x x
x x
x x
x x
x x
x x
x x
x x
x x
x x
mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj

lqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqk
x You have an existing certificate that contains exactly the same x
x domains you requested (ref: /etc/letsencrypt/renewal/XXXX.XX.conf) x
x x
x Do you want to renew and replace this certificate with a x
x newly-issued one? x
x x
x x
x x
x x
x x
x x
x x
x x
x x
x x
x x
tqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqu
x x
mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj

lqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqk
x Saving debug log to /var/log/letsencrypt/letsencrypt.log x
x Starting new HTTPS connection (1): acme-staging.api.letsencrypt.org x
x Generating key (2048 bits): x
x /etc/letsencrypt/keys/0016_key-letsencrypt.pem x
x x
x x
x x
x x
x x
x x
x x
x x
x x
x x
x x
x x
x x
x x
x x
x x
mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj

lqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqk
x Saving debug log to /var/log/letsencrypt/letsencrypt.log x
x Starting new HTTPS connection (1): acme-staging.api.letsencrypt.org x
x Generating key (2048 bits): x
x /etc/letsencrypt/keys/0016_key-letsencrypt.pem x
x Creating CSR: /etc/letsencrypt/csr/0016_csr-letsencrypt.pem x
x x
x x
x x
x x
x x
x x
x x
x x
x x
x x
x x
x x
x x
x x
x x
mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj

lqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqk
x Saving debug log to /var/log/letsencrypt/letsencrypt.log x
x Starting new HTTPS connection (1): acme-staging.api.letsencrypt.org x
x Generating key (2048 bits): x
x /etc/letsencrypt/keys/0016_key-letsencrypt.pem x
x Creating CSR: /etc/letsencrypt/csr/0016_csr-letsencrypt.pem x
x Starting new HTTPS connection (1): acme-staging.api.letsencrypt.org x
x x
x x
x x
x x
x x
x x
x x
x x
x x
x x
x x
x x
x x
x x
mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj

lqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqk
x Saving debug log to /var/log/letsencrypt/letsencrypt.log x
x Starting new HTTPS connection (1): acme-staging.api.letsencrypt.org x
x Generating key (2048 bits): x
x /etc/letsencrypt/keys/0016_key-letsencrypt.pem x
x Creating CSR: /etc/letsencrypt/csr/0016_csr-letsencrypt.pem x
x Starting new HTTPS connection (1): acme-staging.api.letsencrypt.org x
x Starting new HTTPS connection (1): acme-staging.api.letsencrypt.org x
x x
x x
x x
x x
x x
x x
x x
x x
x x
x x
x x
x x
x x
mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj

lqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqk
x Saving debug log to /var/log/letsencrypt/letsencrypt.log x
x Starting new HTTPS connection (1): acme-staging.api.letsencrypt.org x
x Generating key (2048 bits): x
x /etc/letsencrypt/keys/0016_key-letsencrypt.pem x
x Creating CSR: /etc/letsencrypt/csr/0016_csr-letsencrypt.pem x
x Starting new HTTPS connection (1): acme-staging.api.letsencrypt.org x
x Starting new HTTPS connection (1): acme-staging.api.letsencrypt.org x
x Performing the following challenges: x
x x
x x
x x
x x
x x
x x
x x
x x
x x
x x
x x
x x
mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj

lqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqk
x Saving debug log to /var/log/letsencrypt/letsencrypt.log x
x Starting new HTTPS connection (1): acme-staging.api.letsencrypt.org x
x Generating key (2048 bits): x
x /etc/letsencrypt/keys/0016_key-letsencrypt.pem x
x Creating CSR: /etc/letsencrypt/csr/0016_csr-letsencrypt.pem x
x Starting new HTTPS connection (1): acme-staging.api.letsencrypt.org x
x Starting new HTTPS connection (1): acme-staging.api.letsencrypt.org x
x Performing the following challenges: x
x dvsni challenge for XXXX.XX x
x x
x x
x x
x x
x x
x x
x x
x x
x x
x x
x x
mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj

lqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqk
x Saving debug log to /var/log/letsencrypt/letsencrypt.log x
x Starting new HTTPS connection (1): acme-staging.api.letsencrypt.org x
x Generating key (2048 bits): x
x /etc/letsencrypt/keys/0016_key-letsencrypt.pem x
x Creating CSR: /etc/letsencrypt/csr/0016_csr-letsencrypt.pem x
x Starting new HTTPS connection (1): acme-staging.api.letsencrypt.org x
x Starting new HTTPS connection (1): acme-staging.api.letsencrypt.org x
x Performing the following challenges: x
x dvsni challenge for XXXX.XX x
x Waiting for verification… x
x x
x x
x x
x x
x x
x x
x x
x x
x x
x x
mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj

lqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqk
x Saving debug log to /var/log/letsencrypt/letsencrypt.log x
x Starting new HTTPS connection (1): acme-staging.api.letsencrypt.org x
x Generating key (2048 bits): x
x /etc/letsencrypt/keys/0016_key-letsencrypt.pem x
x Creating CSR: /etc/letsencrypt/csr/0016_csr-letsencrypt.pem x
x Starting new HTTPS connection (1): acme-staging.api.letsencrypt.org x
x Starting new HTTPS connection (1): acme-staging.api.letsencrypt.org x
x Performing the following challenges: x
x dvsni challenge for XXXX.XX x
x Waiting for verification… x
x Starting new HTTPS connection (1): acme-staging.api.letsencrypt.org x
x x
x x
x x
x x
x x
x x
x x
x x
x x
mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj

lqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqk
x Saving debug log to /var/log/letsencrypt/letsencrypt.log x
x Starting new HTTPS connection (1): acme-staging.api.letsencrypt.org x
x Generating key (2048 bits): x
x /etc/letsencrypt/keys/0016_key-letsencrypt.pem x
x Creating CSR: /etc/letsencrypt/csr/0016_csr-letsencrypt.pem x
x Starting new HTTPS connection (1): acme-staging.api.letsencrypt.org x
x Starting new HTTPS connection (1): acme-staging.api.letsencrypt.org x
x Performing the following challenges: x
x dvsni challenge for XXXX.XX x
x Waiting for verification… x
x Starting new HTTPS connection (1): acme-staging.api.letsencrypt.org x
x Starting new HTTPS connection (1): acme-staging.api.letsencrypt.org x
x x
x x
x x
x x
x x
x x
x x
x x
mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj

lqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqk
x Generating key (2048 bits): x
x /etc/letsencrypt/keys/0016_key-letsencrypt.pem x
x Creating CSR: /etc/letsencrypt/csr/0016_csr-letsencrypt.pem x
x Starting new HTTPS connection (1): acme-staging.api.letsencrypt.org x
x Starting new HTTPS connection (1): acme-staging.api.letsencrypt.org x
x Performing the following challenges: x
x dvsni challenge for XXXX.XX x
x Waiting for verification… x
x Starting new HTTPS connection (1): acme-staging.api.letsencrypt.org x
x Starting new HTTPS connection (1): acme-staging.api.letsencrypt.org x
x Reporting to user: The following ‘connection’ errors were reported x
x by the server: x
x Domains: XXXX.XX x
x Error: The server could not connect to the client for DV x
x To fix these errors, please make sure that your domain name was x
x entered correctly and the DNS A record(s) for that domain x
x contain(s) the right IP address. Additionally, please check that x
x your computer has a publicly routable IP address and that no x
x firewalls are preventing the server from communicating with the x
x client. x
mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj

lqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqk
x /etc/letsencrypt/keys/0016_key-letsencrypt.pem x
x Creating CSR: /etc/letsencrypt/csr/0016_csr-letsencrypt.pem x
x Starting new HTTPS connection (1): acme-staging.api.letsencrypt.org x
x Starting new HTTPS connection (1): acme-staging.api.letsencrypt.org x
x Performing the following challenges: x
x dvsni challenge for XXXX.XX x
x Waiting for verification… x
x Starting new HTTPS connection (1): acme-staging.api.letsencrypt.org x
x Starting new HTTPS connection (1): acme-staging.api.letsencrypt.org x
x Reporting to user: The following ‘connection’ errors were reported x
x by the server: x
x Domains: XXXX.XX x
x Error: The server could not connect to the client for DV x
x To fix these errors, please make sure that your domain name was x
x entered correctly and the DNS A record(s) for that domain x
x contain(s) the right IP address. Additionally, please check that x
x your computer has a publicly routable IP address and that no x
x firewalls are preventing the server from communicating with the x
x client. x
x Cleaning up challenges x
mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj

Failed authorization procedure. XXXX.XX (dvsni): connection :: The server could not connect to the client for DV :: Failed to connect to host for DVSNI challenge

IMPORTANT NOTES:

  • The following ‘connection’ errors were reported by the server:

Domains: XXXX.XX
Error: The server could not connect to the client for DV

To fix these errors, please make sure that your domain name was
entered correctly and the DNS A record(s) for that domain
contain(s) the right IP address. Additionally, please check that
your computer has a publicly routable IP address and that no
firewalls are preventing the server from communicating with the
client.
root@ICS32:~/letsencrypt#

I hope this helps to know why it don’t work and what to do to get it to work.

-Raymond Day


#4

I guess the end of that verbose output tells what is wrong. But I don’t know how to fix it.

I don’t know what DV is. I got my XXXX.XX at godaddy.com and it points to my home IP on the WWW. I open up port 443 to it’s LAN IP.

I can get to it with the XXXX.XX with the http but not https.

-Raymond Day


#5

Looked more on the web and after I did this command:

root@ICS32:~/letsencrypt# ./letsencrypt-auto --agree-dev-preview --server https://acme-v01.api.letsencrypt.org/directory auth -d XXXX.XX -d www.XXXX.XX --authenticator webroot --webroot-path /media/6TB/USBdisk2-3TB/var/www

I got this back:

An unexpected error occurred.
Error: unauthorized :: The client lacks sufficient authorization :: Error creating new authz :: Name is not whitelisted
Please see the logfiles in /var/log/letsencrypt for more details.
root@ICS32:~/letsencrypt#

Maybe I did not put my URL in the command right. I replace it with XXXX.XX in this post.

-Raymond Day


#7

I did put in my e-mail and I just checked it even the junk mail. Maybe I missed it but don’t see it.

Who would it come from if I get it? Then I can do a search in my e-mail.

Thank you for you help. It will be so nice to have this working if can.

-Raymond Day


#8

the email comes from Let’s Encrypt Beta betaprogram@letsencrypt.org and will show you everything you need. if you got no email, then you arent whitelisted yet.


#9

I guess that’s the problem. I have to wait for a e-mail.

-Raymond Day


#10

If I do this command I get no errors back but it don’t ask for a e-mail ether. I guess my e-mail is all ready stored in a file:

./letsencrypt-auto install --apache --cert-path /etc/letsencrypt/live/XXXX.XX/cert.pem --key-path /etc/letsencrypt/live/XXXX.XX/privkey.pem --chain-path /etc/letsencrypt/live/XXXX.XX/chain.pem

Put a XXXX.XX for my URL don’t want to post it.

Guess just have to wait for a e-mail yet.

Does it have to be a e-mail with your URL you use at the end of the @ ? Or the e-mail I used to get this at godaddy.com?

-Raymond Day


#11

when you registered for the beta you get a whitelisting email, and you need to get that before you even can do anything on the real live server. if it went through you maybe got keys and stuff from the “happy hacker CA” or whetever it was on the test server which is just for testing and not signed.

also we know that you are censoring your domains you dont actually have to mention it on every post.


#12

Thank you that must be it. I never did the “join the Beta, sign up here” link and now I just did. This my work now.

Sorry about posting my domains don’t want to show it in lots of post.

-Raymond Day


#13

I have no problem with people not wanting to show their domains but you dont need to tell that you censored them out in every post since it was clear at the beginning.

but remember LE has cert transparency so if people really want to know your domain they can try to get something out there since all certs are publicly listed.