Permission and access to modify DNS records via DNS service (e.x: Route53) The machine should have at least 1GB RAM and 1 CPU (2GB RAM preferred for production installs)Ī publicly owned domain (e.x. The machine should have a public, static IP address We do not recommend Oracle Cloud, as VM’s here have been known to cause network interference. It should not share a local network with the clients which it will be managing. We highly recommend that Netmaker be deployed in a dedicated networking environment. Preferably from a cloud provider (e.x: DigitalOcean, Linode, AWS, GCP, etc.) However, it should comfortably handle 100+ concurrent clients and support the most common use cases.įor information about deploying more advanced configurations, see the Advanced Installation docs. If deploying to DigitalOcean, you should use the DigitalOcean 1-Click, which uses the interactive script. We recommend Pro because of its substantial free limits, but it does require an account. ![]() You must decide if you are installing the Pro version of Netmaker or the Community version. This guide is just a manual version of the steps performed by that script, and is therefore more prone to error. ![]() Using the auto-generated domain may lead to a failed installation due to rate limiting. For this reason, we strongly recommend using your own domain. If you would like to install netmaker manually, You can use the instructions below.ĭue to the high volume of installations, the auto-generated domain has been rate-limited by the certificate provider. The script can be found on GitHub (raw script here ). Our docker-compose files have changed sizeably and the install script now uses a different process to obtain certificates. ![]() WE RECOMMEND USING THE NM-QUICK SCRIPT INSTEAD OF THIS GUIDE.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |