serverpilot-letsencrypt
serverpilot-letsencrypt copied to clipboard
"This site can’t be reached" error?
Hey, I tried with this script few times today, and I have no clue what's going on. After configuration, all URLs just stop working. Both droplet id as domain http:// https:// with or without www. All I get is "This site can’t be reached."
After installing it a second time on the same config it asked me to replace, I selected no, and it's working now. No idea what happened.
@tu5, usually that happens when Let's Encrypt does not recognize the domain name yet.
Perhaps it's time to add --dryrun
option so people can see whether their domain name is ready or not before committing.
facing same issue @lesaff , any help or way to fix it?
@KyleSforza Make sure to enter domain names separated by space, one of the reasons why it doesn't it work for me it's because I used commas.
@tu5 I am using space, domain.com and www.domain.com :/
ok it seems to work the second time I did it, this time I only put domain.com and not www.domain.com
hmm.
Did you just recently changed your DNS record on both domain.com and www.domain.com? Let's Encrypt won't run unless your domain records match the server IP.
@lesaff How long it takes? I bought domain hour ago, it was perfectly working already and decided to add certificates, then I got the same error that in a first post.. edit: nevermind I done the same thing like in the first post. Maybe the trick is in doing it two times :+1:
You should really wait until the DNS records has fully propagated (~24 hours)
Even though you can see the domain, the Let's Encrypt service may not, resulting in it failing to verify.
On 3 May 2017, at 09:11, tu5 [email protected] wrote:
@lesaff How long it takes? I bought domain hour ago, it was perfectly working already and decided to add certificates, then I got the same error that in a first post.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.
I have a server with four apps running. After running sple.sh to get my last ssl certificate, all four apps are no longer accessible. No amount of reinstalls would work. I finally had to delete all the ssh.conf files and reload nginx.
You are getting this error because most likely nginx-sp has failed to start after the *.ssl.conf is added to the /etc/nginx-sp/vhosts.d directory.
In my case, the issue was because nginx has failed to bind to port 443. I had installed openvpn server previously on the same server and the openvpn daemon was using port 443. I changed the port on my openvpn setting and this fixed the issue.
Try running sudo service nginx-sp start
to see if there's any error.
If you're getting the error only when opening the page using HTTPS but is fine on HTTP, then your port 443 is not open. I'm using Amazon Lightsail VPS and have to manually open port 443 from the control panel.
Same problem as the OP.
sudo service nginx-sp restart
Job for nginx-sp.service failed because the control process exited with error code. See "systemctl status nginx-sp.service" and "journalctl -xe" for details.
systemctl status nginx-sp.service
nginx-sp.service - nginx-sp
Loaded: loaded (/lib/systemd/system/nginx-sp.service; enabled; vendor preset: enabled)
Active: inactive (dead) (Result: exit-code) since Tue 2017-08-22 09:37:55 UTC; 27s ago
Process: 7662 ExecStop=/bin/kill -s QUIT $MAINPID (code=exited, status=0/SUCCESS)
Process: 7064 ExecStartPost=/bin/sleep 0.1 (code=exited, status=0/SUCCESS)
Process: 7059 ExecStart=/opt/sp/nginx/sbin/nginx (code=exited, status=0/SUCCESS)
Process: 7691 ExecStartPre=/opt/sp/nginx/sbin/nginx -t (code=exited, status=1/FAILURE)
Main PID: 7063 (code=exited, status=0/SUCCESS)
Aug 22 09:37:53 ubuntu-512mb-nyc3-01 nginx[7691]: nginx: configuration file /etc/nginx-sp/nginx.conf test failed
Aug 22 09:37:53 ubuntu-512mb-nyc3-01 systemd[1]: nginx-sp.service: Control process exited, code=exited status=1
Aug 22 09:37:53 ubuntu-512mb-nyc3-01 systemd[1]: Failed to start nginx-sp.
Aug 22 09:37:53 ubuntu-512mb-nyc3-01 systemd[1]: nginx-sp.service: Unit entered failed state.
Aug 22 09:37:53 ubuntu-512mb-nyc3-01 systemd[1]: nginx-sp.service: Failed with result 'exit-code'.
Aug 22 09:37:55 ubuntu-512mb-nyc3-01 systemd[1]: nginx-sp.service: Service hold-off time over, scheduling restart.
Aug 22 09:37:55 ubuntu-512mb-nyc3-01 systemd[1]: Stopped nginx-sp.
Aug 22 09:37:55 ubuntu-512mb-nyc3-01 systemd[1]: nginx-sp.service: Start request repeated too quickly.
Aug 22 09:37:55 ubuntu-512mb-nyc3-01 systemd[1]: Failed to start nginx-sp.
journalctl -xe
https://pastebin.com/W9XUMXxf
Your log files are cut off and dont provide any useful information..
@caroseuk I've edited my post to add the full text.
Try running:
/opt/sp/nginx/sbin/nginx -t
It should give you some clues to if its an issue with the configuration file?
nginx: [emerg] the size 10485760 of shared memory zone "SSL" conflicts with already declared size 20971520 in /etc/nginx-sp/snippets/ssl-params.conf:8 nginx: configuration file /etc/nginx-sp/nginx.conf test failed
I have installed SSL manually for another app on the server. Looks like something in that is conflicting.
From this, I conclude that the problem has nothing to do with this script.
Thanks @caroseuk.
Getting this problem, while registering an app that has only subdomains pointed to it (possible cause?)
EDIT: Just tried for a main domain and worked without problem.
I am registering the domains as:
subdomain.domain.com www.subdomain.domain.com
Restarting nginx-sp: nginx: [emerg] BIO_new_file("/etc/letsencrypt/live/subdomain.domain.com/fullchain.pem") failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/etc/letsencrypt/live/subdomain.domain.com/fullchain.pem','r') error:2006D080:BIO routines:BIO_new_file:no such file) nginx-sp.
@caroseuk thanx man. Found the clue :sunglasses:
i have this problem equal. What is solution?
my website goes down and its showing error of ngix, its not loading. Can any buddy guide me how to copy the ngix services from server and work my website Download Apk Files