Logs / Rust
Share a Rust log and find plugin errors
Paste the console of your Rust server and share the link with your admins or a plugin's developer. The analysis finds Oxide and Carbon plugins that fail to compile or throw exceptions when a hook is called – with the plugin's name.
Where do I find the log?
Console in the panel- The server output is in the console. At Nexthosting, you share it with “Share log” in one click.
oxide/logs/- Oxide writes one log file per day (oxide_YYYY-MM-DD.txt) with all plugin messages.
carbon/logs/- With Carbon, the logs are in the carbon/logs folder.
RustDedicated_Data/output_log.txt- If the server is started with -logfile, the output also ends up in this file.
What the analysis detects for Rust
- Plugins that fail to compile or load – with names
- Exceptions in hooks (NullReferenceException and similar) including the plugin
- Crashes, out-of-memory errors and port in use
- Players who join and leave the server
Common Rust errors and how to fix them
Questions about Rust logs
- How do I share a Rust server log?
- Copy the output from the console or open the file from oxide/logs, paste it in above and save. The link is in your clipboard right away.
- Are Steam IDs shared?
- No. Steam IDs, IP addresses, the RCON password and webhooks are masked before saving.
- Plugins stop loading after the wipe – why?
- A Rust update usually comes out on wipe day. Plugins that use internal game functions then no longer fit and fail to compile. Update Oxide or Carbon first, then the affected plugins.