While troubleshooting, our Customer Support Team may ask you to collect application logs to better understand the issue you have run into. Logs record what the application did leading up to a problem, which makes them invaluable for diagnosing connection failures, unexpected disconnects, and configuration issues.
There are two ways to gather this information: the built-in diagnostic tool, which packages everything our team needs into a single file, or exporting the raw logs manually. The diagnostic tool is recommended for most cases because it also captures your system information and NordLayer settings alongside the logs.
Recommended: use the diagnostic tool
The easiest way to collect logs together with your system information and NordLayer settings is the built-in Linux Diagnostic Tool:
nordlayer-diagtool run
It produces a single encrypted report you can attach to your support ticket. See the diagnostic tool guide for details.
Collecting logs manually
If you prefer to export the raw logs yourself, NordLayer logs to a dedicated journalctl namespace.
For NordLayer v2.3.0 and newer:
journalctl --namespace=nordlayer > ./nordlayer.log
For NordLayer v2.2.0 and older:
journalctl -u nordlayer.service > ./nordlayer.log
Both commands write the logs to a file named nordlayer.log in your current directory, which you can then attach to your support ticket. For the most useful results, reproduce the issue first and then export the logs right afterwards, so the relevant events are captured. If you are unsure which version you are running, you can check it with nordlayer version.
Note: In case you have any questions or are experiencing any issues, please feel free to contact our 24/7 customer support team.