Skip to main content

Which Rust settings affect eligibility for the secure server list?

When you reuse a launch script from a private test server, check whether it starts Rust with -insecure. Compare the public server’s running encryption setting with Facepunch’s browser requirement.

Check the two settings that matter here

Read the startup arguments for -insecure. Facepunch introduced it in place of the older server.secure variable for choosing an insecure launch. Remove the argument from the startup settings you use for a public secure server.

Read server.encryption in the running server console by entering the variable name without a value. Facepunch’s Maintenance update states that at least level 2 is required for a server to be considered secure and appear in the Rust client’s server browser. If your script or config uses a lower value, set the documented level in your persistent settings.

Check the result from a normal Rust client

Restart at a planned time if you changed either value. Read server.encryption again, then have someone open regular Rust and look for the entry. If the settings are correct and the server is still missing, investigate the ordinary listing checks next.

Sources

Analytics settings

Analytics are off.

Help improve RustSC with page counts and performance measurements. Privacy details