How to Connect AmneziaWG, Step by Step
A WireGuard config and an AmneziaWG config look almost identical and are not interchangeable. What the extra lines mean, which client reads them, and what to do when the tunnel comes up but nothing loads.

- An AmneziaWG config is a WireGuard config plus obfuscation parameters: Jc, Jmin, Jmax, S1, S2 and four magic header values.
- Those lines are why a standard WireGuard client rejects the file or connects and passes no traffic. You need a client that understands them.
- Both ends must use identical obfuscation values. If the server changes them, every old config stops working - that is by design, not a fault.
- One config per device is the clean way to do it. Shared configs across devices cause silent, intermittent failures that look like a bad connection.
- If the handshake completes and traffic still dies, the usual causes are MTU, a clock that is far off, or the network blocking the destination rather than the protocol.
AmneziaWG is WireGuard with the handshake disguised, which is excellent for getting through filtering and mildly confusing the first time you set it up. The configuration file looks like something you have seen before, and that familiarity is exactly what trips people up.
What is actually in the file
Open an AmneziaWG config in a text editor and the top half is ordinary WireGuard: an interface section with a private key and an address, a peer section with a public key, an endpoint and allowed IPs. Then there are parameters that plain WireGuard has never heard of.
- Parameter — What it controls
- Jc — How many junk packets are sent before the real handshake begins
- Jmin / Jmax — The size range of those junk packets, in bytes
- S1 / S2 — Extra padding added to the first two handshake messages
- H1-H4 — The magic header values, randomised per deployment instead of WireGuard's fixed constants
Together these remove the signature. A filter looking for WireGuard's fixed header values and predictable packet sizes finds neither. The cryptography underneath is untouched, which is why speed is essentially the same.
- The obfuscation parameters are a shared secret in their own right. Both ends must agree on them exactly, or the handshake never completes.
Which client you need
A plain WireGuard client cannot use these files. Depending on the version it will either refuse to import the config because of the unknown keys, or import it, show a connected state and move no traffic at all. The second failure is the one that wastes an afternoon.
Use a client with AmneziaWG support. The Amnezia client covers Windows, macOS, Linux, Android and iOS, and reads these configs directly. On Android and iOS the quickest route is a QR code: open the client, choose to add a connection from a QR, and point the camera at the screen.
- Desktop: download the config file, open the client, import the file, connect.
- Mobile: scan the QR, confirm the VPN profile the operating system asks about, connect.
- Do not paste an AmneziaWG config into a plain WireGuard app and assume silence means success. Check that traffic actually flows.
One config per device
It is tempting to generate one config and copy it to the laptop and the phone. It usually appears to work and then fails in ways that are hard to attribute: one device drops when the other reconnects, handshakes flap, a session dies the moment you pick up your phone.
The reason is that a peer is identified by its key. Two devices presenting the same key are, from the server's point of view, one device whose address keeps changing. Give each device its own config and the problem disappears.
In Cypher VPN this is what the devices list does. Each device gets its own AmneziaWG configuration with its own key, up to five at once, and you can rename, reissue or disconnect one without touching the others. The VLESS link is separate and shared; resetting it affects every device at once, which is the intended behaviour for that protocol.
Get a working config in about a minute.
No account and no email. Test it free for one hour or 100 MB first, then pay in crypto from $1.99 a week if it works for you.
When the handshake succeeds and nothing loads
This is the most common complaint, and the protocol is rarely the cause. Work through it in this order.
MTU first. Obfuscation adds bytes, and on mobile networks and some home routers the result is packets large enough to be dropped silently. Small requests work, larger pages hang halfway. Lowering MTU in the interface section to 1280 fixes a surprising share of these cases.
Then the clock. Handshakes are time-sensitive, and a device whose time is off by minutes will negotiate and then fail. Turn automatic time synchronisation on.
Then DNS. If the config specifies a DNS server that the network blocks, name resolution dies while the tunnel itself is healthy. Nothing loads, yet the client says connected.
Finally, consider that the network may be blocking the destination rather than the protocol. AmneziaWG defeats signature matching, not address blocking. If one exit is unreachable from a particular network, switching to another country usually settles the question in seconds.
When the parameters change
Obfuscation values are per-deployment and they do change, usually because the old ones started being recognised. When that happens, old configs stop connecting. That is not a malfunction: a parameter set that a filter has learned is worse than useless, because it is both blocked and identifying.
The fix is to reissue the config rather than to debug the old one. If a connection that worked for weeks stops dead and nothing on your side changed, reissue first and investigate second.
FAQ
Can I convert a WireGuard config into an AmneziaWG one?
No. The obfuscation parameters have to match the server's, and you cannot invent them locally. Get the config from whoever runs the server.
Is AmneziaWG slower than WireGuard?
Not meaningfully. The junk packets surround the handshake, not your actual traffic, so throughput stays close to plain WireGuard. Distance to the exit matters far more.
Why does my phone keep reconnecting?
Usually aggressive battery optimisation killing the VPN service in the background, or the same config being used on two devices. Exclude the client from battery optimisation and give each device its own config.
Does AmneziaWG hide that I am using a VPN?
It hides the protocol signature. It does not hide that you are sending encrypted traffic to a foreign address, and nothing does. Treat it as making traffic unclassifiable, not invisible.
What if AmneziaWG is blocked on my network?
Switch to VLESS/Reality, which imitates an ordinary HTTPS visit to a real site. On the same plan here, no extra payment, and it survives harsher filtering.
→ Self-host it or buy it, and what each option costs you: AmneziaWG VPN providers →
A config that works on the first try.
AmneziaWG and VLESS/Reality on one plan, per-device configs, six exits. No account, no email, crypto only. Telegram: t.me/cyphevpn_bot