starred/Cloak
1
0
Fork 0
mirror of https://github.com/cbeuw/Cloak.git synced 2026-04-26 04:55:58 +03:00
Code Issues 144 Projects Releases 10 Packages Wiki Activity

[GH-ISSUE #20] listen tcp: address [...] too many colons in address #13

New issue
Closed
opened 2026-02-26 12:33:43 +03:00 by kerem · 6 comments
kerem commented 2026-02-26 12:33:43 +03:00
Owner
Copy link

Originally created by @Alireza2n on GitHub (Mar 17, 2019).
Original GitHub issue: https://github.com/cbeuw/Cloak/issues/20

Hi,
I have built ck-client from souce (using latest code from master branch) inside a docker container. The server runs fine, but while attempting to run ck-client I ran into this errors:

 2019-03-17 06:41:57 INFO: plugin "/go/github.com/cbeuw/Cloak/build/ck-client" enabled
 2019-03-17 06:41:57 INFO: initializing ciphers... chacha20-ietf-poly1305
 2019-03-17 06:41:57 INFO: listening at 0.0.0.0:1080
 2019-03-17 06:41:57 INFO: udprelay enabled
2019/03/17 06:41:57 ck-client.go:158: Listening for ss on ::1:45643
2019/03/17 06:41:57 ck-client.go:160: listen tcp: address ::1:45643: too many colons in address
 2019-03-17 06:41:57 INFO: running from root user
 2019-03-17 06:41:57 ERROR: plugin service exit unexpectedly

Any ideas?

Thanks

Originally created by @Alireza2n on GitHub (Mar 17, 2019). Original GitHub issue: https://github.com/cbeuw/Cloak/issues/20 Hi, I have built ck-client from souce (using latest code from master branch) inside a docker container. The server runs fine, but while attempting to run ck-client I ran into this errors: ``` 2019-03-17 06:41:57 INFO: plugin "/go/github.com/cbeuw/Cloak/build/ck-client" enabled 2019-03-17 06:41:57 INFO: initializing ciphers... chacha20-ietf-poly1305 2019-03-17 06:41:57 INFO: listening at 0.0.0.0:1080 2019-03-17 06:41:57 INFO: udprelay enabled 2019/03/17 06:41:57 ck-client.go:158: Listening for ss on ::1:45643 2019/03/17 06:41:57 ck-client.go:160: listen tcp: address ::1:45643: too many colons in address 2019-03-17 06:41:57 INFO: running from root user 2019-03-17 06:41:57 ERROR: plugin service exit unexpectedly ``` Any ideas? Thanks
kerem closed this issue 2026-02-26 12:33:43 +03:00
kerem commented 2026-02-26 12:33:43 +03:00
Author
Owner
Copy link

@malikshi commented on GitHub (Mar 21, 2019):

yeah its made server cant be accessed by client, should restart the service

<!-- gh-comment-id:475117465 --> @malikshi commented on GitHub (Mar 21, 2019): yeah its made server cant be accessed by client, should restart the service
kerem commented 2026-02-26 12:33:43 +03:00
Author
Owner
Copy link

@Alireza2n commented on GitHub (Mar 23, 2019):

yeah its made server cant be accessed by client, should restart the service

Thanks, I'll give it a go and tell what happened. :)

<!-- gh-comment-id:475867189 --> @Alireza2n commented on GitHub (Mar 23, 2019): > yeah its made server cant be accessed by client, should restart the service Thanks, I'll give it a go and tell what happened. :)
kerem commented 2026-02-26 12:33:43 +03:00
Author
Owner
Copy link

@cbeuw commented on GitHub (Mar 23, 2019):

Actually this issue is due to IPv6 addresses not being in square brackets and then concatenated to a port (e.g. ::1:45643). The proper way to represent IPv6 with a port is [a:b:c:d]:xyz. I have fixed this in release 1.1.0

<!-- gh-comment-id:475868842 --> @cbeuw commented on GitHub (Mar 23, 2019): Actually this issue is due to IPv6 addresses not being in square brackets and then concatenated to a port (e.g. ::1:45643). The proper way to represent IPv6 with a port is `[a:b:c:d]:xyz`. I have fixed this in release 1.1.0
kerem commented 2026-02-26 12:33:43 +03:00
Author
Owner
Copy link

@NAVrasZ commented on GitHub (Mar 24, 2019):

@cbeuw Connect using ipv6 only (i.e. "[::]") and got this

Mar 24 02:14:46 vultr.guest ss-server[2251]:  2019-03-24 02:14:46 INFO: tcp server listening at [::1]:50039
Mar 24 02:14:46 vultr.guest ss-server[2251]:  2019-03-24 02:14:46 INFO: udp server listening at [::]:443
Mar 24 02:14:46 vultr.guest ss-server[2251]:  2019-03-24 02:14:46 INFO: running from root user
Mar 24 02:14:46 vultr.guest ss-server[2251]: 2019/03/24 02:14:46 ck-server.go:260: Listening on [::]:443
Mar 24 02:14:47 vultr.guest ss-server[2251]: 2019/03/24 02:14:47 ck-server.go:157: New session from UID:*******, sessionID:*****
Mar 24 02:14:56 vultr.guest ss-server[2251]: 2019/03/24 02:14:56 ck-server.go:172: Failed to connect to ssserver: dial tcp: address ::1:50039: too many colons in address
Mar 24 02:14:57 vultr.guest ss-server[2251]: 2019/03/24 02:14:57 ck-server.go:172: Failed to connect to ssserver: dial tcp: address ::1:50039: too many colons in address
Mar 24 02:15:09 vultr.guest ss-server[2251]: 2019/03/24 02:15:09 ck-server.go:172: Failed to connect to ssserver: dial tcp: address ::1:50039: too many colons in address
Mar 24 02:15:12 vultr.guest ss-server[2251]: 2019/03/24 02:15:12 ck-server.go:172: Failed to connect to ssserver: dial tcp: address ::1:50039: too many colons in address

Thx

<!-- gh-comment-id:475922040 --> @NAVrasZ commented on GitHub (Mar 24, 2019): @cbeuw Connect using ipv6 only (i.e. `"[::]"`) and got this ``` Mar 24 02:14:46 vultr.guest ss-server[2251]: 2019-03-24 02:14:46 INFO: tcp server listening at [::1]:50039 Mar 24 02:14:46 vultr.guest ss-server[2251]: 2019-03-24 02:14:46 INFO: udp server listening at [::]:443 Mar 24 02:14:46 vultr.guest ss-server[2251]: 2019-03-24 02:14:46 INFO: running from root user Mar 24 02:14:46 vultr.guest ss-server[2251]: 2019/03/24 02:14:46 ck-server.go:260: Listening on [::]:443 Mar 24 02:14:47 vultr.guest ss-server[2251]: 2019/03/24 02:14:47 ck-server.go:157: New session from UID:*******, sessionID:***** Mar 24 02:14:56 vultr.guest ss-server[2251]: 2019/03/24 02:14:56 ck-server.go:172: Failed to connect to ssserver: dial tcp: address ::1:50039: too many colons in address Mar 24 02:14:57 vultr.guest ss-server[2251]: 2019/03/24 02:14:57 ck-server.go:172: Failed to connect to ssserver: dial tcp: address ::1:50039: too many colons in address Mar 24 02:15:09 vultr.guest ss-server[2251]: 2019/03/24 02:15:09 ck-server.go:172: Failed to connect to ssserver: dial tcp: address ::1:50039: too many colons in address Mar 24 02:15:12 vultr.guest ss-server[2251]: 2019/03/24 02:15:12 ck-server.go:172: Failed to connect to ssserver: dial tcp: address ::1:50039: too many colons in address ``` Thx
kerem commented 2026-02-26 12:33:43 +03:00
Author
Owner
Copy link

@cbeuw commented on GitHub (Mar 24, 2019):

Oops sorry I missed one line which needed the square brackets.
It's fixed in v1.1.1

<!-- gh-comment-id:475932068 --> @cbeuw commented on GitHub (Mar 24, 2019): Oops sorry I missed one line which needed the square brackets. It's fixed in v1.1.1
kerem commented 2026-02-26 12:33:43 +03:00
Author
Owner
Copy link

@Klaaktu commented on GitHub (Nov 24, 2019):

Hi, it seems there is another one in ck-client:
ck-client -i ::1

level=info msg="Starting standalone mode"
level=info msg="Listening on UDP [::1]:1984 for shadowsocks client"
level=fatal msg="address ::1:1984: too many colons in address"

ck-client -i [::1]

level=info msg="Starting standalone mode"
level=info msg="Listening on UDP [[::1]]:1984 for shadowsocks client
<!-- gh-comment-id:557907266 --> @Klaaktu commented on GitHub (Nov 24, 2019): Hi, it seems there is another one in ck-client: `ck-client -i ::1` ``` level=info msg="Starting standalone mode" level=info msg="Listening on UDP [::1]:1984 for shadowsocks client" level=fatal msg="address ::1:1984: too many colons in address" ``` `ck-client -i [::1]` ``` level=info msg="Starting standalone mode" level=info msg="Listening on UDP [[::1]]:1984 for shadowsocks client ```
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
renovate/go-github.com-refraction-networking-utls-vulnerability
dependabot/go_modules/golang.org/x/crypto-0.45.0
utls-1.7.0
deps-20250430
padding
docker-tests
ptspec
legacy-v1
v2.12.0
v2.11.0
v2.10.0
v2.9.0
v2.8.0
v2.7.1-pre
v2.7.0
v2.6.1
v2.6.0
v2.5.5
v2.5.4
v2.5.3
v2.5.2
v2.5.1
v2.5.0
v2.4.1
v2.4.0
v2.3.2
v2.3.1
v2.3.0
v2.2.3
v2.2.2
v2.2.1
v2.2.0
v2.1.3
v2.1.2
v2.1.1
v2.1.0
v2.0.2
v2.0.1
v2.0.0
v1.1.2
v1.1.1
v1.1.0
v1.0.0
v0.2.0
v0.1.0
Labels
Clear labels   
pull-request

Mirrored from GitHub Pull Request

No labels
pull-request
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/Cloak#13
No description provided.