LocalNode
How it worksDemoAppsPricingFAQShop now
← All guides
Home/Community/Contacting Support and Sending Diagnostic Logs

Contacting Support and Sending Diagnostic Logs

Advanced
Beginner
5 min read
Published: May 7, 2026

Was this helpful?

Help us improve our community guides.

In this guide

  • Overview
  • Step 1: Generating a diagnostic log bundle
  • Step 2: Enabling Remote Support Access
  • Step 3: Contacting the team

Need direct help?

LocalNode Care Plan members get priority remote support.

Email Support →

More in Advanced

Adding External Storage to Your Localnode

Adding External Storage to Your Localnode — Step-by-step guide for your LocalNode.

5 min read

Adding Smart Home Devices to Home Assistant

Adding Smart Home Devices to Home Assistant — Step-by-step guide for your LocalNode.

5 min read

Backing Up Your Entire Localnode Configuration

Backing Up Your Entire Localnode Configuration — Step-by-step guide for your LocalNode.

5 min read
LocalNode

Plug-and-play home server. Your data, your hardware, your rules.

Product

How it worksDemoAppsCommunityPricingFAQ

Support

ContactShipping & ReturnsTrack Order

Legal

Privacy PolicyTerms of ServiceShipping Policy
© 2026 LocalNode. Built for people who value their privacy.Denton, TX · hello@localnode.tech

We designed LocalNode to be robust, but software bugs happen. When you encounter an issue that none of our guides can solve, our engineering team is here to help. Here is how to get the fastest resolution possible.

Overview

Because your LocalNode is 100% private and disconnected from our cloud, we have zero visibility into your server. We cannot see if it crashed, and we cannot log in to fix it unless you explicitly generate logs and temporarily grant us access.

Step 1: Generating a diagnostic log bundle

Before you email us, you should pull the system logs. This tells our engineers exactly what the server was doing right before it crashed.

  1. Go to your LocalNode dashboard at http://localnode.local.
  2. Scroll to the bottom of the page to the System section.
  3. Click Generate Diagnostic Logs.
  4. The system will take about 60 seconds to compile logs from the kernel, the Docker engine, and every running app.
  5. A file named localnode-diagnostics-2026-05.zip will download to your computer.

Note: The diagnostic bundle automatically strips out your personal passwords, API keys, and DuckDNS tokens to preserve your privacy.

Step 2: Enabling Remote Support Access

If the issue is incredibly complex, it might take a dozen emails back and forth to fix. Alternatively, you can give our engineers a secure, 24-hour key to log directly into your server to fix it for you.

  1. On the main dashboard, go to the System section.
  2. Click Enable Remote Support.
  3. A warning will pop up explaining that a secure reverse-tunnel is being opened to LocalNode HQ. Click Accept.
  4. The dashboard will generate a 9-digit Support Pin (e.g., 492-184-992).

This tunnel will automatically self-destruct and sever the connection after exactly 24 hours. You can also manually click "Disable Remote Support" at any time to instantly kick us out.

⚠️ Warning: Never post your Support Pin on public forums or Reddit. Anyone with that PIN can access your server's root terminal.

Step 3: Contacting the team

Once you have your logs and your Support PIN, reach out to us:

  • Email: Send an email to support@localnode.tech.
  • Attach: Attach the .zip diagnostic log file to the email.
  • Include: Paste your 9-digit Support PIN in the body of the email.
  • Describe: Explain exactly what you were trying to do when the error occurred.

Our support team is based in the United States and typically responds within 4 business hours. We will log into the tunnel, fix the configuration file, and email you when it's resolved!


Need help? Email hello@localnode.tech or visit localnode.tech/contact.