Know who runs the server
Private Server is optional and uses your hardware or cloud account. The official guide says no feature upgrade fee is required, but hosting and traffic charges remain yours. Running your own server also means arranging maintenance and handling failures.
Make a checklist before spending
Confirm that you can manage the hosting account, billing, system updates and backups. Read the provider's traffic rules and estimate a month's hosting and bandwidth costs before buying. A free feature does not mean free infrastructure.
If nobody can maintain the machine or handle renewals, the client's regular connection may be simpler to manage. This article does not require a server purchase or provide unverified installation commands.
Separate management credentials from shared access
The official Server Manager documentation describes QR connections and sharing. A management QR code may contain an access key: protect it like a password and keep it out of public posts, chat screenshots and support reports. Check the access being granted before sharing.
Use the documentation for your deployed version to configure networking and certificates. Identify the specific ports and management endpoints needed instead of exposing every administrative service while troubleshooting.
Validate before relying on it
Record the version, maintainer and recovery procedure, then test with one device. Recheck after updates. If something fails, examine server operation, basic network access and client configuration separately rather than assuming a single cause.
Sources and scope
Sources checked on 31 October 2026. This is an editorial guide; check the current client for available features.
Lantern · Private Server / Lantern Server Manager
https://lantern.io/privateserver
https://github.com/getlantern/lantern-server-manager