Opened 4 years ago

Closed 6 weeks ago

#1204 closed Bug / Defect (wontfix)

OpenVPN Connect 3.0.0 (272) client can't accept server-pushed [compressor]

Reported by: keber Owned by: OpenVPN Inc.
Priority: minor Milestone:
Component: OpenVPN Connect Version:
Severity: Not set (select this one, unless your'e a OpenVPN developer) Keywords:


Using OpenVPN Server from pfsense community edition 2.4.4-release-p3.
Trying out OpenVPN Connect 3.0.0 (272) on Windows 10.
Previously had lzo compression enabled.
Changed this setting to 'Disable Compression, retain compression packet framing [compress]' and enabled Push Compression setting to connecting clients.

OpenVPN GUI v11.9.0.0 on Windows 10 seems to work ok.

OpenVPN Connect 3.0.0. (272) on Windows 10 and OpenVPN Connect 3.0.5 (1819) on Android 9 fails to connect after Sending PUSH_REQUEST to server.

log shows it recieved [compress] option among others. Then the following message:

Client exception in transport_recv: process_server_push_error: Problem accepting server-pushed compressor: option_error: option 'compress' must have at least 2 arguments.
Client terminated, restarting in 2000 ms...

Changed compression setting later to '[Legacy style, comp-lzo no]' seemed to work (it starts the connection) but it doesn't (no traffic).

Change History (4)

comment:1 Changed 3 years ago by garga

It's a pfSense bug. See

This ticket can be closed

comment:2 Changed 2 years ago by Gert Döring

Owner: changed from yuriy to denys
Status: newassigned

comment:3 Changed 21 months ago by Antonio Quartulli

Owner: changed from denys to OpenVPN Inc.

comment:4 Changed 6 weeks ago by Gert Döring

Resolution: wontfix
Status: assignedclosed

OpenVPN Inc does not want to receive any feedback for the "Connect"
OpenVPN clients via the community bug trackers (here and in GH issues).

Please resubmit - if still relevant - via

Note: See TracTickets for help on using tickets.