Support multi-server in ssconf (Dynamic Access Keys)

[moranno]

I tried to use the following json config for my Dynamic Access Keys

[
    {
        "server": "127.0.0.1",
        "server_port": 4444,
        "password": "98cb61c8-76dc-4d0e-939c-3ed9e11327b5",
        "method": "chacha20-ietf-poly1305",
        "remarks": "sstest"
    },
    {
        "server": "127.0.0.1",
        "server_port": 4443,
        "password": "98cb61c8-76dc-4d0e-939c-3ed9e11327b5",
        "method": "chacha20-ietf-poly1305",
        "remarks": "sstest1"
    }
]

But the Outline client pops an error:

Outline
ServerAccessKeyInvalid: Failed to parse VPN information fetched from dynamic access key.
Cause: TypeError: Missing JSON fields: method, password, server, server_port.

What did I do wrong? Thanks

[daniellacosse]

Thank you for flagging this! We desperately want to support this, but currently don't. Changing to a feature request.

[rorosin]

Actually, this functionality is already defined in original ShadowSocks' standard for online configuration delivery - SIP008

[alexander-potemkin]

Following up the implementation / the way things done on some other VPN systems, it would be nice to add some simple ping test - to let client connect to the servers that are alive / closer