Error loading profile: option_error: option<key> was not properly closed.

Official client software for OpenVPN Access Server and OpenVPN Cloud.
Post Reply
access2nitan
OpenVpn Newbie
Posts: 2
Joined: Tue Jan 10, 2017 11:47 am

Error loading profile: option_error: option<key> was not properly closed.

Post by access2nitan » Tue Jan 10, 2017 11:55 am

Hi All.

Greetings!

This is my first post and I've configured openvpn on centos 7 machine and even its working fine with all kind of machines (windows+linux+mac) But whenever I'm trying to connect through any iphone, its showing an error Error loading profile: option_error: option<key> was not properly closed.
I've murge all three file in one file.ca,crt,key file in .ovpn file. I'm able to connect with openvpn server from machine with same key but not able through iphone

Please help me.

TinCanTech
OpenVPN Protagonist
Posts: 11137
Joined: Fri Jun 03, 2016 1:17 pm

Re: Error loading profile: option_error: option<key> was not properly closed.

Post by TinCanTech » Tue Jan 10, 2017 3:27 pm

I do not understand what you have done but .. this is the correct way to inline your client:
https://community.openvpn.net/openvpn/wiki/IOSinline

access2nitan
OpenVpn Newbie
Posts: 2
Joined: Tue Jan 10, 2017 11:47 am

Re: Error loading profile: option_error: option<key> was not properly closed.

Post by access2nitan » Thu Jan 12, 2017 8:00 am

Hello,

I've worked on above given URL but seems that there is other issue with ios devices.I can connect with same .ovpn file in machine.But no able to connect with mobile devices.
Error message:-
Error loading profile: Inbox/myclient.ovpn
option_error: option <key> was not properly closed out



Please help.

TiTex
OpenVPN Super User
Posts: 310
Joined: Tue Apr 12, 2011 6:22 am

Re: Error loading profile: option_error: option<key> was not properly closed.

Post by TiTex » Thu Jan 12, 2017 8:24 am

I don't think that's true , i'm using openvpn profile on iOS with inline certificates and don't have any issues.
it seems like you are missing a </key> tag or it's not in the correct place.

Post Reply