@bengmau 

  @bengmau 

Hi,

Does the "remote" parameter inside the *.ovpn file contain any special characters or is it just something ordinary, like remote tp-link.com 1194 ?

  @woozle 

pretty normal.  tried both IP based and dns hostname based.

for reference I've tried public available .ovpn files from vpngate dot net as a reference test and those are also giving the same result when importing.

  @Kevin_Z 

I generated a .ovpn on the tplink be550 itself by temporarily turning on vpn server.  the ovpn generated by the tplink be550 itself imports fine.

the main difference between my own and test ovpn files it they have " # remark" statements and ";" remark statements mainly

  @bengmau 

Looks like this is a bug in TP-Link's ovpn file parser. 

There is a comment line in the *.ovpn files distributed VPN Gate that reads: # You have to specify as 'remote <HOSTNAME> <PORT>'. You can also

If you remove either that whole line or at least the part that reads "remote <HOSTNAME> <PORT>", then the BE550 imports the file correctly.

Normally, all lines that begin with a # should be ignored, but somehow the Archer BE550 doesn't adhere to that.

I might test this on other TP-Link routers, if I have some free time.
 

Edit:

On second thought, if we assume the BE550 V1 indeed processes all the comment lines in the *.ovpn file, then it would be safer to remove all of the references to OpenVPN parameters from the comment lines in the *.ovpn file, because what happens to the "remote" parameter would likely also happen to other parameters, like "dev" or "proto".