Import a WireGuard node

SoloIP can import a WireGuard configuration from the node import or subscription parser. Treat the configuration as a secret: it can contain private keys and endpoint credentials.

Before importing

• Confirm that the installed SoloIP build supports WireGuard import.
• Keep a configuration backup.
• Remove private keys from screenshots and support messages.
• Decide which node group should receive the imported entries.

Configuration shape

The parser expects a WireGuard configuration with an interface and peer section. A minimal example is:

[Interface]
PrivateKey = <private-key>
Address = 10.0.0.2/32
DNS = 1.1.1.1

[Peer]
PublicKey = <server-public-key>
AllowedIPs = 0.0.0.0/0
Endpoint = vpn.example.com:51820
PersistentKeepalive = 25

Use the provider's actual values. Do not paste a private key into a public ticket.

1. Open batch node import

Open node management, choose batch import, and select the WireGuard or subscription parser input. Keep the existing node list unchanged for the first test.

2. Paste the configuration

Paste the full configuration into the text area. Do not paste it into a field that expects a URL. The parser should recognize the [Interface] and [Peer] sections before you continue.

3. Choose group and overwrite behavior

Select a clear group such as wireguard-test. Leave replace/overwrite disabled unless you intentionally want to replace existing entries. If the UI offers automatic names, use them only when each imported peer has a stable order.

4. Import and review the result

Start the import and review the success and error counts. Open one imported node and confirm the protocol, endpoint, group, and relay/outbound settings. If the result is wrong, stop before importing the rest of the provider list.

5. Diagnose and verify egress

Run a node diagnostic, create a rule for one test device, and follow verify the current egress path. Expand the rule only after the WireGuard path works.

Common problems

Pasting into the subscription URL field does nothing

Use the configuration text input or the WireGuard import mode. A URL parser will not treat an INI document as a subscription.

Import succeeds but diagnostics fail

Check the endpoint, allowed IPs, key pair, system time, and the outbound interface. Confirm that UDP traffic can leave the selected path.

`allowed-ips = 0.0.0.0/0` changes other routes

This value requests a default path for the WireGuard peer. Keep the node limited to a test rule until you confirm how the selected routing mode handles it.

Keys cannot be edited in the list

Some sensitive fields are protected after import. Re-import a corrected configuration through the parser instead of copying keys into an unrelated protocol field.

Domain access is abnormal after import

Check the DNS value in the interface section and the SoloIP DNS mode. Compare an IP-only request with a hostname request.

The whole batch is wrong

Disable the new rules, preserve the source text and response, restore the backup if needed, and retry with one peer.