Brooooooo, this is absolute gold!!!! I know it's all there in the Digital Ocean article, but having someone explain and walkthrough is worth every since second. Thanks!
Hey I had the issue where https was not working. I solved it. I first checked the firewall status using sudo ufw status and noted 443 was not available. So I enabled it in the firewall by using sudo ufw allow 443 and everything worked. Thanks for the wonderful video.
videos with barely understandable audio from india without enough explanation: 800 000 views Great video with great audio and even greater explanation: 6500 views Seems like most people don't recognize quality
Great tutorial! What's that thing about DigitalOcean spaces for static files? I have a couple of Django projects (mainly REST APIs) on a DigitalOcean droplet and I am able to load static files through the Django admin area... So why would I need DigitalOcean Spaces?
Great video Mitch. Currently I'm digging a way to acquire a valid certificate for a domain which can only be accessed with in the company infrastructure or intranet. I know there is a way Letsencrypt issue a certificate for a wildcard domain through a DNS challenge. I need a help in doing it properly so that I can get a valid certificate for a BigBluButton installation that I need to deploy with in a company.
I love your series, i decide to it out on a project everything work well but i can login to my admin site i keep getting this error attempt to access a readonly database and the admin css not working also any help will be appreciated
Could you or someone do a tutorial on how to get this running in a docker container? The docs look pretty confusing on Digital Ocean and I'm getting port 80 in use errors when building my container using nginx to serve static files.
Thanks. This was clear and simple. I run into problems after this process i could't access my site using mysite url either www.mysite.com or mysite.com. i was getting the message below : Welcome to nginx! If you see this page, the nginx web server is successfully installed and working. Further configuration is required. For online documentation and support please refer to nginx.org. Commercial support is available at nginx.com. Thank you for using nginx. However i had to restart the entire process by uninstalling nginx and certbot from ubuntu..then restarting afresh with the nginx configurations and then install the lets encrpyt certificate. I highly recommend you wait for (maybe 5 mins) or like in my case (3 hours) before the domain propagation had to take place.... Don't start the lets encrpyt process when you can't access your website yet without the SSL...so if you can't access www.mysite.com or mysite.com then wait until when you can then you can pick the SSL installation from there. Thks
Isn't the auto-renew automatically set up on the initial cert installation? I didn't think is was necessary to do the "dry run" part to get auto-renew running.
Yeah, I just checked the D.O. documentation and it states this at Step 5: "Let’s Encrypt’s certificates are only valid for ninety days. This is to encourage users to automate their certificate renewal process. *_The certbot package we installed takes care of this for us by adding a renew script to /etc/cron.d. This script runs twice a day and will automatically renew any certificate that’s within thirty days of expiration._*" (Emphasis mine.) So, the auto-renew is already set up when you initially install the cert. (Maybe it wasn't like this when you originally posted this video.)
very first command doesn't work, this is the error I get, I'm using ubuntu 18.04 nginx: add-apt-repository ppa:cerbot/cerbot Cannot add PPA: 'ppa:~cerbot/ubuntu/cerbot'.