Server is super slow after Let's Encryption
The first byte time is 0/100 on the www.webpagetest.org. What did I do?
Log In to Comment
1 Answer
Have another answer? Share your knowledge.
Related
-
question
Certbot plugin for nginx 1.15?
After installing NGINX 1.15 (built form source with pagespeed), I installed the certbot plugin. but not sure why, it reverted my server to NGINX 1.14!!!!!! why is that?
-
question
Cannot create a ssl certificate with letsencrypt and certbot
Hi there I cannot create a ssl certificate with letsencrypt and certbot for my website. Can someone please help me. The old website is still running on another server but the new website I have constructed is on the new server which I am trying to create the cert. This is the command I run in the bash **sudo certbot --nginx -d glima.is -d www.glima.is** And here is the results when certbot runs. Failed authorization procedure. www.glima.is (http-01): urn:ietf:params:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from http://www.glima.is/.well-known/acme-challenge/i0H7vf5uI1BFKfb_EFpxHIhWtW6b4_UlaXr2lrUcXy8 [185.112.145.172]: "<!DOCTYPE html>\n<html>\n<head>\n <title>i-MSCP internet - Multi Server Control Panel - Error 404</title>\n <meta http-equiv='", glima.is (http-01): urn:ietf:params:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from http://glima.is/.well-known/acme-challenge/vnTQAlnaIHH0XwWODjX39TvSVDHBvwsytbTw2ETSN-4 [185.112.145.172]: "<!DOCTYPE html>\n<html>\n<head>\n <title>i-MSCP internet - Multi Server Control Panel - Error 404</title>\n <meta http-equiv='" IMPORTANT NOTES: - The following errors were reported by the server: Domain: www.glima.is Type: unauthorized Detail: Invalid response from http://www.glima.is/.well-known/acme-challenge/i0H7vf5uI1BFKfb_EFpxHIhWtW6b4_UlaXr2lrUcXy8 [185.112.145.172]: "<!DOCTYPE html>\n<html>\n<head>\n <title>i-MSCP internet - Multi Server Control Panel - Error 404</title>\n <meta http-equiv='" Domain: glima.is Type: unauthorized Detail: Invalid response from http://glima.is/.well-known/acme-challenge/vnTQAlnaIHH0XwWODjX39TvSVDHBvwsytbTw2ETSN-4 [185.112.145.172]: "<!DOCTYPE html>\n<html>\n<head>\n <title>i-MSCP internet - Multi Server Control Panel - Error 404</title>\n <meta http-equiv='" To fix these errors, please make sure that your domain name was entered correctly and the DNS A/AAAA record(s) for that domain contain(s) the right IP address.
-
question
Secure with Let's Encrypt using Server Blocks
Tutorial on [how to use Let's Encrypt](https://www.digitalocean.com/community/tutorials/how-to-secure-nginx-with-let-s-encrypt-on-ubuntu-16-04) Tutorial on [Server Blocks](https://www.digitalocean.com/community/tutorials/how-to-set-up-nginx-server-blocks-virtual-hosts-on-ubuntu-16-04) Now i've setup two blocks. m.mysite.com and mysite.com; one being the mobile version, the other being the desktop version. I got to **How To Use the Webroot Plugin** but i'm stuck on this step ``` sudo certbot certonly --webroot --webroot-path=/var/www/mysite/html -d mysite.com ``` Do i need a seperate certificate for m.mysite.com since i can't add another --webroot-path?
-
question
Replaced free SSL cert as new domain nginx config issue
First here is what I did on Ubuntu 16/nginx Digital Ocean droplet: 1. Installed free SSL cert as per their guide for old domain `OLD_domain.com.au`, all good. 2. Domain changed to `NEW_domain.com.au`. 3. Removed old cert and installed cert for new domain, again all good and `NEW_domain.com.au` is working. However I notice `/etc/nginx/sites-enabled/default` still has references to old domain. My question is can I just manually update this file with the new domain and restart nginx? Or is there a better way? Here is the relavant bits of the file: ``` /* /etc/nginx/sites-enabled/default */ server { ... server_name NEW_domain.com.au www.NEW_domain.com.au; listen 443 ssl; # managed by Certbot ssl_certificate /etc/letsencrypt/live/NEW_domain.com.au/fullchain.pem; # managed by Certbot ssl_certificate_key /etc/letsencrypt/live/NEW_domain.com.au/privkey.pem; # managed by Certbot include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot ... server { if ($host = www.accessmygp.com.au) { return 301 https://$host$request_uri; } # managed by Certbot if ($host = accessmygp.com.au) { return 301 https://$host$request_uri; } # managed by Certbot server_name accessmygp.com.au www.accessmygp.com.au; listen 80; return 404; # managed by Certbot ... ```