# Options error: --nobind doesn't make sense unless used with --remote **URL:** \ **Category:** Pritunl\ **Tags:** pritunl\ **Created:** [November 16, 2022, 5:18pm UTC](https://forum.pritunl.com/t/options-error-nobind-doesnt-make-sense-unless-used-with-remote/556 "2022-11-16T17:18:45Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![demmostehnes](https://forum.pritunl.com/letter_avatar_proxy/v4/letter/d/7993a0/32.png) [@demmostehnes](https://forum.pritunl.com/u/demmostehnes)\ **Post date:** [November 16, 2022, 5:18pm UTC](https://forum.pritunl.com/t/options-error-nobind-doesnt-make-sense-unless-used-with-remote/556/1 "2022-11-16T17:18:45Z")
The error above I get when I try to connect using pritunl-client v1.3.3343.50. The remote host is specified at the beginning of the file. A line below follows the “nobind” option. ---
**Author:** ![zach](https://forum.pritunl.com/user_avatar/forum.pritunl.com/zach/32/1105_2.png) [@zach](https://forum.pritunl.com/u/zach)\ **Post date:** [November 16, 2022, 8:39pm UTC](https://forum.pritunl.com/t/options-error-nobind-doesnt-make-sense-unless-used-with-remote/556/2 "2022-11-16T20:39:17Z")
The configuration file imported into the client must include remotes in a format by the [**configuration filter**](https://github.com/pritunl/pritunl-client-electron/blob/master/service/parser/ovpn.go) added recently. This can cause issues with configuration files from other OpenVPN servers. ---
**Author:** ![ImLee](https://forum.pritunl.com/letter_avatar_proxy/v4/letter/i/e36b37/32.png) [@ImLee](https://forum.pritunl.com/u/ImLee)\ **Post date:** [June 30, 2024, 2:33pm UTC](https://forum.pritunl.com/t/options-error-nobind-doesnt-make-sense-unless-used-with-remote/556/3 "2024-06-30T14:33:05Z")
Thanks I’m getting the same error. So How to run configuration files from other OpenVPN servers? ---
**Author:** ![nurray](https://forum.pritunl.com/user_avatar/forum.pritunl.com/nurray/32/1301_2.png) [@nurray](https://forum.pritunl.com/u/nurray)\ **Post date:** [July 16, 2025, 7:56am UTC](https://forum.pritunl.com/t/options-error-nobind-doesnt-make-sense-unless-used-with-remote/556/4 "2025-07-16T07:56:58Z")
I ran into the same problem. Looking through the electron code. it appears the “remote” option in your config now needs to “remote hostname port protocol”. When I changed my config to this by adding “udp” on the end of the “remote” option. It worked. This change is stupid. I do not mind allowing the procotol to be a third option, but REQUIRING it. Ever heard of BACKWARDS compatibility numbskulls. Hope this helps. ---
**Author:** ![nurray](https://forum.pritunl.com/user_avatar/forum.pritunl.com/nurray/32/1301_2.png) [@nurray](https://forum.pritunl.com/u/nurray)\ **Post date:** [July 16, 2025, 7:58am UTC](https://forum.pritunl.com/t/options-error-nobind-doesnt-make-sense-unless-used-with-remote/556/5 "2025-07-16T07:58:36Z")
The pritunl website does not appear to have documentation on the configuration file format, which if it had existed would have allowed me to find out the new requirement for the “remote” option, instead of having to examine the source code. My thanks to Zach for the link to the source code which allowed me to find the problem. ---
**Author:** ![zach](https://forum.pritunl.com/user_avatar/forum.pritunl.com/zach/32/1105_2.png) [@zach](https://forum.pritunl.com/u/zach)\ **Post date:** [July 18, 2025, 1:51pm UTC](https://forum.pritunl.com/t/options-error-nobind-doesnt-make-sense-unless-used-with-remote/556/6 "2025-07-18T13:51:06Z")
The [**configuration parser**](https://github.com/pritunl/pritunl-client-electron/blob/master/service/parser/ovpn.go) was added after several privilege escalation issues with OpenVPN configuration files. It significantly limits the options and format to provide the least risk of privilege escalation vulnerabilities in the future.