[Bug]: Previously working dynamic keys no longer accepted in Outline Client 1.14.0

[Sega789]

Application

Outline Client

Describe the bug

Hello, I want to report a problem after updating Outline Client.

I had Outline Client version 1.13.1 (476278) installed from the official website.
I use a key that looks something like this: ssconf://blablalblablablalbla.json#

Everything worked fine.

Recently, Outline Client was updated to version 1.14.0 (480310) and after that it no longer connects to the server.
Error: invalid configuration
I am attaching a picture that shows the error information.

Please note!
Then I decided to uninstall the new version and again launched the old version of Outline Client version 1.13.1 (476278)
And in this version, everything works fine again...

It seems that the problem is related to updating Outline Client to version 1.14.0 (480310)

Please, could you solve this problem?

Steps to reproduce

Described in the section "Describe the bug".

What did you expect to happen?

No response

What actually happened?

No response

Outline Version

Described in the section "Describe the bug".

What operation system are you using?

Linux

Operating System Version

Trisquel 11.0.1 KDE

Screenshots and Videos

No response

[quiqqe]

same problem.
the old client is also self-updating and only helps for once before restarting.

[jyyi1]

Hi @quiqqe @Sega789 , as the error message indicated, could you please double check the port field of your config (if you are using a dynamic key ssconf://<key>, please replace it with https://<key> and check the response content)? It requires a number (e.g., 5000) instead of a string (e.g., "5000").

[goodboy34-tech]

Static key, and dynamic:

[goodboy34-tech]

[Sega789]

Hello, @jyyi1

In my key I replaced ssconf:// to https:// as you wrote. But the problem is the same.

[jyyi1]

Hi @Sega789 @goodboy34-tech , this issue is caused by an invalid dynamic key. According to our doc, the following is a valid content of a dynamic key:

{
  "server": "example.com",
  "server_port": 8388,
  "password": "example",
  "method": "chacha20-ietf-poly1305"
}

But this one is not:

{
  "server": "example.com",
  "server_port": "8388",
  "password": "example",
  "method": "chacha20-ietf-poly1305"
}

Note the difference between the "server_port" values. The old clients didn't check the format, so incorrect keys were accidentally allowed.

So if you created this key, please update it. If you got it from a service provider, please also ask them to fix it for you (you may provide the link of this reply to them).

[Tynnikov]

I am confused. I've created the key and allows you to connect to the server on some phones, but not on others via Android/iOS phones.

I've checked server_port in the hiddify app and I see that it is INT.
In this case what is the problem?

[goodboy34-tech]

В приложении Outline такая же проблема?

I am confused. I've created the key and allows you to connect to the server on some phones, but not on others via Android/iOS phones.

I've checked server_port in the hiddify app and I see that it is INT. In this case what is the problem?

[Tynnikov]

Yes, outline has the same issue.

[Tynnikov]

В приложении Outline такая же проблема?

I am confused. I've created the key and allows you to connect to the server on some phones, but not on others via Android/iOS phones.
I've checked server_port in the hiddify app and I see that it is INT. In this case what is the problem?

Very interesting. My friend installed outline then connected to the server and after one minute get the same error.

[Tynnikov]

The problem is not with a server. Just clean VPN settings in the Iphone or Androind.