YAML Dynamic Config Not Working on Windows when TCP and UDP ports are different

[khantzawhein]

Application

Outline Client

Describe the bug

The Outline fails to connect to a dynamic config with YAML format on Windows (Mac works fine with the same config).

Outline on Windows fails when TCP and UDP ports are different.

Reproduced on both 1.17.0 and 1.19.0

Steps to reproduce

Use this YAML config as a dynamic key payload:

YAML Config:

transport:
    $type: tcpudp
    tcp:
        $type: shadowsocks
        endpoint: '140.245.119.xx:80'
        cipher: chacha20-ietf-poly1305
        secret: REDUCTED
    udp:
        $type: shadowsocks
        endpoint: '140.245.119.xx:443'
        cipher: chacha20-ietf-poly1305
        secret: REDUCTED

What did you expect to happen?

No response

What actually happened?

The Error:

ProxyConnectionFailure: Failed to connect to server xxxx.ngrok-free.app.
Cause:   ERR_INTERNAL_ERROR: Internal service error
  Cause:     Error: host:port separator not found

Outline Version

1.19.0 / 1.17.0

What operation system are you using?

Windows

Operating System Version

Windows 10

Screenshots and Videos

No response

[emohandesi]

I get the same error message with the following configuration on Outline Windows Version 1.19.0 (490240).

transport:
  $type: tcpudp
  tcp:
    $type: iptable
    table:
      - ips:
          - 34.117.59.0/24
        dialer:
          $type: shadowsocks
          endpoint: sub.domain.com:443
          cipher: chacha20-ietf-poly1305
          secret: xf0Wzuz5NyAUaCV95q4p9N
    fallback:
      $type: direct
  udp:
    $type: shadowsocks
    endpoint: sub.domain.com:443
    cipher: chacha20-ietf-poly1305
    secret: xf0Wzuz5NyAUaCV95q4p9N

ProxyConnectionFailure: Failed to connect to server Split-tunneling.
Cause:   ERR_INTERNAL_ERROR: Internal service error
  Cause:     Error: host:port separator not found

If I use the same connection as UDP for the TCP as shown below, the connection is successfully made without giving an error message.

transport:
  $type: tcpudp
  tcp:
    $type: shadowsocks
    endpoint: sub.domain.com:443
    cipher: chacha20-ietf-poly1305
    secret: xf0Wzuz5NyAUaCV95q4p9N
  udp:
    $type: shadowsocks
    endpoint: sub.domain.com:443
    cipher: chacha20-ietf-poly1305
    secret: xf0Wzuz5NyAUaCV95q4p9N

[ohnorobo]

This is related to our use of this legacy field in the electron client. The newer tcpudp parsing is failing to populate it.

[emohandesi]

This is related to our use of this legacy field in the electron client. The newer tcpudp parsing is failing to populate it.

What does it mean? Is there a workaround to it?

[ohnorobo]

No there isn't a workaround at the moment unfortunately. It's a bug on our end which still requires some debugging to get fixed.