Key takeaways
Confirm profile availability
Open the official INFOCROSS interface attached to your subscription and inspect available protocols or configurations. The label should state AmneziaWG 3.0 or AWG 3.0. A WireGuard or AmneziaWG Legacy label does not establish version 3.0.
Product screens and plan contents can change after publication. If the item is absent, do not choose a similar-looking format. Send support an order identifier without payment secrets and ask whether a new profile exists for your location and device.
Reject configuration files forwarded by unknown users. A profile contains a private key and endpoint. Obtain it through a verified dashboard, bot, or support channel linked by the official site.
Prepare a compatible client
Amnezia Docs sets AmneziaVPN 4.8.12.9 as the minimum version. Install a current build from an official store or download page and check the version before import. An older app can display Not installed or ignore version 3.0 fields.
A native AmneziaWG client needs AmneziaWG native format. A standard WireGuard client does not support H1–H4, S1–S4, and signature parameters. The .conf extension alone does not prove compatibility.
Keep a recovery profile where your plan allows one, but label files by protocol and date. Do not edit PrivateKey or masking values.
Request a new file or import link
Version 3.0 requires a newly generated configuration. Request one for the specific device. If INFOCROSS provides a QR code, display it on a trusted screen and avoid a shared photo library. Transfer a file through a protected channel.
Check that the profile identifies AmneziaWG and does not carry a Legacy label. Do not paste its contents into a public forum. Support can work from a sanitised error and client version.
One file across several devices prevents targeted revocation and can disrupt peer behavior. The official Amnezia app guide recommends separate configurations.
Import and run the first checks
Use the supported profile import in AmneziaVPN. In a native AmneziaWG app, choose Add Tunnel and import from file. Review the name and endpoint without exposing the key, then activate the tunnel.
Record the first handshake time. Request an IP literal, a domain, and an external-address page. The sequence separates routing from DNS. Transfer a larger response to expose a possible MTU fault.
Disconnect and test once after changing the access network. One success provides a baseline, while repeated results support a stability claim.
Diagnose common failures
Not installed suggests an obsolete client or unrecognised profile. Update AmneziaVPN and request a new file. A timeout before handshake calls for endpoint, UDP port, network, and server-health checks.
A handshake without websites points to DNS, AllowedIPs, forwarding, NAT, or MTU. Compare an IP request with a domain request. If only one access network fails, preserve the same device and profile for comparison.
Do not rewrite H ranges or I packets from a chat suggestion. The server needs matching settings. Send support time, carrier, OS, app version, and failure stage.
Protect credentials and verify sources
PrivateKey, QR code, and a complete import URI grant profile access. Keep them out of tickets unless the service offers a protected secret field. Revoke and replace a leaked profile. Deleting a chat message cannot recall a copied key.
Retain current configurations only. Remove Legacy from the device after a confirmed migration if support does not need rollback. Check subscription and device limits in the live interface rather than relying on an old article.
Official Amnezia requirements appear at https://docs.amnezia.org/documentation/instructions/new-amneziawg-selfhosted/ and https://docs.amnezia.org/documentation/instructions/use-amneziawg-app/. Verify INFOCROSS-specific availability in the current product and support channel.
After import, record the issue date and assigned device. This inventory allows one profile to be revoked without disabling other users. Remove duplicate tunnels after a successful rollback check and retain a clear name with protocol and location.
Before you choose a configuration
Protocol availability and connection quality depend on the network, device, client version, and server route. Check the current plan terms before payment, use the official client source, and contact support with the operator, device, client, and exact error if the connection fails.
Sources and update policy
Technical statements are checked against the primary project documentation available on the update date. Network behavior can change; the article avoids promising universal availability.