Skip to content

WireSock Secure Connect - 3.9.2.1 ​

Release date: 2026-11-18

Here is the new beta build of WireSock Secure Connect 3.9.2.1

This release adds support for AmneziaWG 3.x profiles, checks profiles more strictly before it saves or connects them, and explains more clearly what each DPI protection setting does and why a connection was refused.

Please treat it as a beta release — feedback and bug reports are welcome.

What's New ​

Version 3.9.2.1 ​

AmneziaWG 3.x Support ​

  • Profiles made for AmneziaWG 3.0 and 3.1 servers can be imported, viewed, created, edited, exported and connected in the app. The command line can import, export and connect them. The feature is available in both WireSock Secure Connect and WireSock Secure Connect Pro.
  • Nine new profile settings are supported:
    • Header protection key: scrambles the packet headers so that DPI cannot simply read the packet type from them. The same key must be set on the server.
    • Packet padding: adds bytes to each packet so that its size varies.
    • Random data at the end of the packet.
    • Key rotation interval, handshake retry interval, key lifetime, keepalive interval and handshake attempts: the timers and limits of the connection.
    • Cookie replies: whether the tunnel answers with cookie replies under load.
  • The profile wizard has a new AmneziaWG 3.x section. The header protection key can be generated and copied there; the field hides it unless you choose to show it. The timer settings are in a collapsed "Advanced settings (timers and handshake)" block, with a note to change them only when the server administrator says so.
  • The text editor highlights the new settings and checks them as you type.
  • The profile details show an "AmneziaWG 3.x" row that lists the features that are on. The profile details and the connection log never show the key: the log lists the AmneziaWG 3.x settings in use and shows the key only as <set> (or <all zero, protection off> for a key of zeros). The text editor and exported profiles show the key in full, as they show your private key. Anyone with an exported profile can connect as you, and anyone with the header protection key can recognize this VPN traffic, so do not share them; for another device, ask your VPN provider for a profile of its own.
  • The AmneziaWG settings I1–I5 are still accepted, but WireSock does not send them, so the DPI protection they give in other apps does not apply. Without them the profile still connects, unless the network blocks the handshake. The text editor and the connection log say that I1–I5 are not used. While protocol masking and header protection are both off, the profile details say so too and suggest protocol masking instead, as does the text editor (see "Clearer texts for DPI protection" under "Improvements").

Improvements ​

  • The profile details show the DPI protection that is actually used. Each row reads "state (source)" and says whether the profile's own settings or the global settings apply. A new "Protocol masking" row shows the masking protocol in use.
  • Clearer texts for DPI protection. Protocol masking, magic headers, junk packets and the SOCKS5 proxy are now described by what they do. Earlier texts promised more than these settings do. Protocol masking, for example, sends packets that look like QUIC, DNS, SIP or STUN before each handshake that the app starts, so that DPI may mistake the connection for that protocol. If S1, S2 and H1–H4 are all set, the padding at the start of the VPN packets looks like that protocol too; otherwise the VPN packets themselves are not changed. Masking is on once a masking domain is set (see "Protocol masking needs a masking domain" under "Checks and Limits").
  • The SOCKS5 proxy works as before; its description now says what it does. By default only the WireGuard handshake goes through the SOCKS5 proxy. Check "Send all WireGuard traffic through the proxy" to send every WireGuard packet through it, for example when the server cannot be reached directly. The proxy adds no encryption or disguise of its own: the packets to it still carry the server's address.
  • Advice on choosing a masking domain. The masking domain tooltip advises a popular domain that opens in your region without a VPN, for example that of a large local online store. It warns that a blocked domain can keep the VPN from connecting or cut it off.
  • A refused connection is reported once, with the reason. When an AmneziaWG 3.x profile or a masking setting from the global settings is refused, the app stops trying. 3.8.2.1 stopped only for some DNS and SOCKS5 settings. With tray notifications on, the app shows one notification, "Couldn't connect to" and the profile or server name, with a short reason. The title is just "Couldn't connect" when "Hide the VPN server name and address" is on, or when the app has no name for the attempt, for example one started from the command line or by the service at Windows startup. The main window keeps the full reason under that profile until the next attempt, and a screen reader announces it. The Logs tab shows the tunnel engine's reason, at the default log level too.
  • When the app stops trying because of a refusal, the kill switch does not start blocking traffic. Until you fix the profile or the setting and the app connects again, traffic can go outside the VPN.
  • PersistentKeepalive can be a range, such as 25-35. A new interval in that range is drawn each time, as in AmneziaWG.
  • The magic headers section of the wizard reminds you that S1–S4 and H1–H4 must match the server.
  • The profile wizard shows the split tunneling description.
  • The main window's profile list works with a screen reader and the keyboard. Each profile is read by its name, typing the first letters of a name selects it, and the Down and End keys or the mouse wheel no longer open "Import profile...".
  • The new and changed texts of this version are translated into all languages of the app.
  • Better high contrast and right-to-left display. Texts, selected items and the title bar are readable in Windows high contrast themes. Arabic, Persian and Urdu pages lay out Latin names, error marks and tooltips in the right order and on the right side. The text editor shows profile text left to right, and numbers are shown with the digits you typed.

Bug Fixes ​

  • Saving a profile from the wizard no longer drops S3 and S4.
  • Saving a profile from the wizard keeps the settings meant for WireSock only: lines that start with #@ws:, which other WireGuard and AmneziaWG apps skip. They are still readable in the file. Earlier, a wizard save wrote them as plain settings, so another app applied them after an export. A profile already saved that way keeps its plain lines: add #@ws: again in the text editor.
  • With no masking protocol chosen, the protocol list now shows QUIC, the protocol that is actually used. Earlier it showed SIP.
  • A + sign before Jc, Jmin, Jmax or Jd is now dropped when the profile is loaded, so the number applies as written.
  • In the Pro edition, an encrypted profile whose text starts with a UTF-8 byte order mark now loads correctly.
  • After profiles are copied into an empty profile folder and the list is reloaded, the main window leaves the "No profiles are registered" state.
  • Large replies that other applications receive from the VPN server's address are delivered whole. Earlier, some of these replies arrived damaged or were lost.

Configuration Changes When Upgrading ​

Profiles and settings are kept when you upgrade. Some stored profiles behave differently or need a fix. If you use the kill switch, check after the upgrade that your profile still connects (see "When the app stops trying because of a refusal, the kill switch does not start blocking traffic" under "Improvements").

  • Profiles that no longer load. A profile whose S1–S4 is 1280 or more, whose S or H value is written in hexadecimal or with a sign, or whose PersistentKeepalive has a sign (such as +25), is refused. It appears in the profile list with the reason. Use "Edit text" to correct the value: S1–S4 are whole numbers from 0 to 1279, and H1–H4 are decimal numbers or ranges such as 123456-234567.
  • Profiles that are no longer listed: a profile file whose name the app cannot use, for example a name made only of spaces or, on Windows 10, a name Windows opens as a device, such as CON. The file stays in the profile folder: rename it there to list it again.
  • Profiles that load, but must be fixed before you can save a change:
    • only part of S1, S2 and H1–H4 set, with the others left out: the profile connects without magic headers, as before;
    • one of them present with an empty value: see "A setting with an empty value" under "Checks and Limits";
    • junk packet sizes the app no longer accepts: the profile connects and sends junk packets of 50 to 1000 bytes, as before;
    • H1–H4 values that overlap: as before, the profile does not connect, and the app keeps trying. Meanwhile the kill switch may not block traffic, even when the app says that the network is blocked. Copy H1–H4 from the server's configuration again (or ask your VPN provider).
  • An explicit MTU now means the size of the packets inside the tunnel. The S4 padding and the SOCKS5 header are no longer subtracted from it, so a profile with MTU set may send larger packets after the upgrade. For example, MTU = 1292 with S4 = 128 allowed 1,164-byte packets before and allows 1,292 bytes now. If large downloads or pages stall after the upgrade, lower the profile's MTU by its S4 value, or remove the MTU line so that the app sets the size itself. As before the upgrade, on a 1,500-byte IPv6 connection an S4 above 140 leaves less than 1,280 bytes for each packet inside the tunnel, the minimum IPv6 needs, so IPv6 inside the tunnel may not work.
  • PersistentKeepalive = 0 now turns keepalive off. 3.8.2.1 still sent a keepalive after 25 idle seconds for such a profile. Behind a router, an idle connection may then stop receiving traffic from the server until your computer sends something. To keep the old behaviour, set PersistentKeepalive = 25 or remove the line. This is not the AmneziaWG 3.x keepalive interval, where 0 means the default.
  • A global junk packet count above 128 (the Network tab allowed up to 200) is applied as 128. Earlier, such a count sent no junk packets at all. The Network tab now accepts at most 128.
  • A global masking domain that is not a plain host name is kept, and the Network tab shows an error on it. A profile that cannot use it is refused at connect, with a message that names the Network tab (see "A global masking domain that is not a plain host name" under "Checks and Limits").
  • The masking browser. With QUIC masking and no browser chosen, the app now shows and uses cURL. Earlier it showed Random, and saved Chrome. A browser already stored in a profile or in the global settings is kept, so an upgraded installation that stored Chrome keeps using Chrome.
  • Pro deployments with a global masking domain. If wiresock.config in the services' data folder sets a global masking domain (<Id>) but no browser, QUIC masking now imitates cURL. To keep Chrome, add <Ib>chrome</Ib> next to <Id>. In a template deployment, wiresock.config is made from the service.config template when the app is installed, so add it to the template too.
  • Downgrading. Uninstalling this version keeps your profiles and settings. Going back to 3.8.2.1 was not checked: 3.8.2.1 may not load or use profiles with AmneziaWG 3.x settings or a PersistentKeepalive range, so keep a copy of your profiles first.
  • Command line.
    • wiresock-connect-cli import now exits with code 2 whenever the import fails. Earlier, most failures printed the error but exited with 0. Wrong arguments still exit with 1. Scripts that check the exit code now stop instead of going on.
    • When an AmneziaWG 3.x profile or a masking setting from the global settings is refused, wiresock-connect-cli connect now prints the reason and ends.
    • Connection refusals have new status codes 0xC0030200–0xC0030203; scripts that read the status may notice.

Checks and Limits ​

This version checks profiles and settings that earlier versions accepted without a word. Each check that refuses a profile or a setting says what is wrong and how to fix it, or that the reason is in the connection log.

When you import or save a profile

  • S1–S4 (the padding sizes of the magic headers) must be whole numbers from 0 to 1279.
  • H1–H4 (magic headers) must be decimal numbers from 0 to 4294967295, or ranges such as 123456-234567. Hexadecimal values are refused. H1–H4 must not overlap. A value of 0 sends the standard WireGuard header of that type (1 for H1 up to 4 for H4), so H1 = 0 overlaps H2 = 1. The text editor warns about a 0, because a server that itself sets 0 does not match.
  • S1–S4 and H1–H4 work only as a set. WireSock applies them only when S1, S2 and all of H1–H4 are set (S3 and S4 are optional). Importing a profile that sets only some of them, or saving it in the text editor, is refused with a message such as "AmneziaWG S1-S4 and H1-H4 take effect only when all of S1, S2 and H1-H4 are set. Missing: H3, H4. Copy them from the server's configuration (or ask your VPN provider), or remove S1-S4 and H1-H4." The profile wizard marks each missing field and does not save. Other AmneziaWG apps may accept S1–S4 without H1–H4. If the server's configuration does not set H1–H4, use H1 = 1, H2 = 2, H3 = 3, H4 = 4. If it does not set S1 and S2, use S1 = 0 and S2 = 0. Do not write these values when the server sets its own: the connection then fails without an error.
  • A setting with an empty value (for example H4 =) counts as missing when you import or save. A stored profile with one is still used. If none of the other settings of S1, S2 and H1–H4 is left out (not written at all), the empty value is read as 0 (for H1–H4, the standard WireGuard header) and the magic headers are applied. The profile may then not reach a server that sets its own value, and does not connect if H1–H4 overlap. The connection log says the value is read as 0, but the profile details show the magic headers as off. If another setting of the set is left out, the profile connects without magic headers. Copy the value from the server's configuration (or ask your VPN provider); the editor asks for it before you save.
  • Junk packet sizes: while junk packets are sent (Jc above 0), Jmin is 0 to 1279, Jmax is 1 to 1280, and Jmin must be smaller than Jmax. With Jc at 0 no junk packets are sent, and any sizes from 0 to 1280 are kept, as long as Jmin is not above Jmax. Jmin and Jmax work only as a pair: with one of them alone, the editor shows a note and the profile can be saved. Sizes that cannot be used are replaced with 50 to 1000 bytes, and the profile details and the connection log say so.
  • AmneziaWG 3.x settings must be well formed. The header protection key is 64 hexadecimal digits or a Base64 key. The numbers are whole numbers or ranges such as 30-60. The on/off settings accept on/off, true/false, 1/0 and t/f.
  • Profile names must be plain file names: no folder or drive, no characters that file names cannot hold, at most 250 characters, and not a name Windows opens as a device.

When you save a profile in the wizard or the text editor

These checks are made by the editors only. A profile imported with such values is not refused on import: it may fail when it connects, and the editor asks for a fix when you next change the profile.

  • Header protection needs S1, S2 and H1–H4 in the profile, and all four of S1–S4 set to 12 bytes or more (S3 and S4 are then not optional).
  • The masking domain of a profile must be a plain host name such as example.com for SIP masking, and for DNS and QUIC masking in a profile with AmneziaWG 3.x settings. A domain with other letters is written in Punycode (xn--…).
  • SIP masking with header protection allows S1–S4 of up to 30 bytes. The editors refuse a profile's own SIP masking with larger values, and such a profile is refused when it connects. QUIC is the safe choice with header protection.

When you connect

  • The tunnel engine checks AmneziaWG 3.x profiles and refuses one it cannot use. The app then shows "The tunnel engine refused this AmneziaWG 3.x profile. The reason is in the connection log (the Logs tab)."
  • SIP masking from the global settings is refused for a profile with header protection and an S1–S4 over 30 bytes. The profile can be saved, but it does not connect while SIP is chosen on the Network tab. Choose another protocol there (QUIC is best). Do not change S1–S4: they must match the server.
  • A global masking domain that is not a plain host name is refused for a profile it does not suit: with SIP masking, or with DNS or QUIC masking for a profile with AmneziaWG 3.x settings. Set a host name such as example.com on the Network tab.

What the app does not apply

  • Protocol masking needs a masking domain. Without one, the masking protocol and browser have no effect, and the drop-downs stay disabled. A domain longer than 253 characters turns masking off without a warning; the profile details then show masking as off.
  • While protocol masking is on, Jmin and Jmax are not used: the junk packets take the masking protocol's own sizes. The connection log, the Jmin and Jmax tooltips and the editors' note on a lone Jmin or Jmax say so; the profile details do not.
  • I1–I5 are not used (see "AmneziaWG 3.x Support").

Settings that weaken each other

  • STUN or DNS masking weakens header protection. The profile connects, but header protection starts to repeat. With DNS this happens within a few hundred packets, after which it does little to keep DPI from recognizing the VPN. With STUN it gets weaker after tens of thousands of packets. The editors, the profile details and the Network tab warn about it. Choose QUIC, or SIP if QUIC is blocked and S1–S4 are 30 bytes or less.

On the Network tab

  • The global junk packet sizes follow the same limits: Jmin from 0 to 1279 and below Jmax, Jmax from 1 to 1280.
  • The global masking domain and the masking domain list accept only plain host names. The list shows its first wrong line and cannot be saved until it is fixed.

Download ​

Major Features and Improvements for version 3.x ​

1. New Architecture ​

  • A dedicated separated layer for better performance and security isolation.
  • A UI client for connection control, settings configuration, and profile management. The VPN connection operates independently of the UI: the UI client can be fully closed while the connection remains active.
  • Support for establishing the VPN connection during Windows startup, before user logon.
  • The Virtual Adapter Mode and TCP Socket Termination settings no longer require running the application with administrator privileges.

2. KillSwitch (Network Lock) ​

  • KillSwitch can be configured to block traffic when the VPN connection is lost.

3. Global Split Tunneling Settings ​

  • Split tunneling can now be configured once globally and applied to all profiles in the application.

4. New DPI Protection Options ​

  • Added protocol masking: before each handshake that the app starts, it sends packets that look like QUIC, DNS, SIP or STUN, so that DPI may mistake the connection for that protocol. If S1, S2 and H1–H4 are all set, the padding at the start of the VPN packets looks like that protocol too; otherwise the VPN packets themselves are not changed. See Documentation
  • Supports the AmneziaWG junk packets (Jc, Jmin, Jmax) and magic headers (S1–S4, H1–H4), including the AmneziaWG 2.0 S3, S4 and H1–H4 ranges. AmneziaWG I1–I5 are accepted but not sent, so the DPI protection they give in other apps does not apply; while protocol masking and header protection are off, the app suggests protocol masking instead.
  • AmneziaWG 3.x support (from 3.9.2.1), set in each profile: header protection, packet padding, random data at the end of the packet, cookie replies and the AmneziaWG 3.x timers, in WireSock Secure Connect and WireSock Secure Connect Pro.
  • DPI protection can be configured either globally or individually per profile.

5. New User Interface for Creating and Editing Profiles ​

  • Supports editing profiles in a text-based format.

6. New Command-Line Interface (CLI) ​

  • Introduced a new command-line interface supporting core commands: connect, disconnect, import, export, and delete profile.
  • The CLI enables full operation of the application without the UI.

7. New Language Support ​

  • Arabic
  • Portuguese
  • Korean
  • Vietnamese
  • Bangla (Bangladesh)
  • Bangla (India)
  • Hindi
  • Indonesian
  • Urdu
  • Amharic
  • Afaan Oromo