Inspect, reissue, or recover a DAMM profile without guessing what is inside it.
This page is the companion surface after the main onboarding wizard. Use it when you already have a DAMM link or profile and want to inspect the exact WireGuard config, reissue it from a real server URL, or recover cleanly on this device.
Inspect or issue a profile manually
Use this when you need to inspect the exact profile inputs or reissue manually. DAMM should make sensible assumptions for this device first, then let you assert preferences where they matter. Local key generation stays on the device. The control plane only receives the public key and returns the peer material needed to render a WireGuard profile.
- Your device name and profile filename are prefilled from the detected platform.
- If you are unsure about region or exit country, leave them blank and let DAMM choose.
- The only hard requirements are a real DAMM server URL and a real enrollment token.
- Open a personalized DAMM link that already carries your server URL and token.
- Review or tweak the optional preferences.
- Tap one button to issue the profile for this device, then import it into WireGuard.
Profile summary
- Use the issue form above if you do not already have a DAMM profile for this device.
- Once a profile is issued, this panel will show the real endpoint, address, and DNS before you import it.
- Import the downloaded
.conffile into WireGuard and activate it there.
Already have a DAMM profile?
Advanced debug: load traced validation artifact
Import steps for this platform
Recovery and failure handling
- Check that the DAMM server URL is reachable from this device.
- Check that the token is current and intended for enrollment, not admin use.
- If the browser lacks X25519 support, issue the profile through the CLI or a newer browser.
- Make sure the native WireGuard app is installed.
- Import the downloaded
.conffile inside WireGuard. - If the endpoint is stale, reissue here rather than editing the file by hand.
Loading a traced reference profile proves DAMM validation. It does not provision your device. This page now treats that artifact as debugging material, not as the primary onboarding story.