![]() ![]() Now we can run certbot without requiring sudo which would limit our ability to run Apache as a non-root user. Logs-dir = /opt/homebrew/etc/certbot/logsĬonfig-dir = /opt/homebrew/etc/certbot/certs In this new file paste the following: work-dir = /opt/homebrew/etc/certbot See the first part of this series to find out more about this. This assumes you have Visual Studio Code installed and have enabled the CLI code command. To be able to use certbot in a non-root setup (like we have with Brew), we need to create a cli.ini file so that the certbot command will use local paths rather than root access-only system paths: Create a Certbot Config mkdir -pv ~/.config/letsencrypt First we should install the certbot tool that will facilitate this process: brew services stop httpd Now you have a valid host that is accessible from the internet, we need to generate a valid LetsEncrypt SSL certificate. You will need to replace this with your own hostname Let's Encrypt + Certbot Throughout this guide I use as an example host. You have successfully configured remote access, but now you want to get SSL working. You have tested this and you can confirm that when you browse to on your phone, you are indeed seeing the webserver of your internal network. I already own this one, you need to use your own!), and you have configured the host to be port-forwarded to your local development machine. Let's assume you have registered the domain (p.s. A quick way to test if you have things setup is to try reaching host via your phone or some other device that is not on your internal network. I'll leave this process up to you as it might require some Googling to get the this process setup depending all the factors listed above.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |