starred/goproxy
1
0
Fork 0
mirror of https://github.com/snail007/goproxy.git synced 2026-04-27 00:15:51 +03:00
Code Issues 144 Projects Releases 3 Packages Wiki Activity

[GH-ISSUE #462] SPS mode not work with Android #369

New issue
Closed
opened 2026-02-27 23:16:39 +03:00 by kerem · 4 comments
kerem commented 2026-02-27 23:16:39 +03:00
Owner
Copy link

Originally created by @Raymond-C on GitHub (Jan 10, 2022).
Original GitHub issue: https://github.com/snail007/goproxy/issues/462

Work in PCs but shows error "WARN connect to tcp parent fail, ERR:cmd associate not supported" when try to connet in Android device

Expected Behavior

Android device can work

Current Behavior

Try to connect with Shadowrocket_9.6 / BifristV_0.6.3 / v2RayNG_1.3.1 , all not work ,came with same error

Possible Solution

Steps to Reproduce

Context (Environment)

proxy version is : commercial_11.3

full command is : proxy sps -S socks -T tcp -p :12345 -a aa:bb:500:0: -P socks5://xxxx:xxx@a.b.c.d

system is : ubuntu 20.4

Below is full log
2022/01/10 13:46:23.537152 WARN connect to tcp parent fail, ERR:cmd associate not supported, form: 8.218.14.68:51755 from 8.218.14.68:51755
2022/01/10 13:46:23.946307 WARN connect to tcp parent fail, ERR:cmd associate not supported, form: 8.218.14.68:51757 from 8.218.14.68:51757
2022/01/10 13:46:23.946606 WARN connect to tcp parent fail, ERR:cmd associate not supported, form: 8.218.14.68:51759 from 8.218.14.68:51759
2022/01/10 13:46:23.948229 WARN connect to tcp parent fail, ERR:cmd associate not supported, form: 8.218.14.68:51756 from 8.218.14.68:51756
2022/01/10 13:46:25.386507 WARN connect to tcp parent fail, ERR:cmd associate not supported, form: 8.218.14.68:51771 from 8.218.14.68:51771
2022/01/10 13:46:25.794262 WARN connect to tcp parent fail, ERR:cmd associate not supported, form: 8.218.14.68:51775 from 8.218.14.68:51775
2022/01/10 13:46:25.800645 WARN connect to tcp parent fail, ERR:cmd associate not supported, form: 8.218.14.68:51774 from 8.218.14.68:51774
2022/01/10 13:46:25.995680 WARN connect to tcp parent fail, ERR:cmd associate not supported, form: 8.218.14.68:51778 from 8.218.14.68:51778

Originally created by @Raymond-C on GitHub (Jan 10, 2022). Original GitHub issue: https://github.com/snail007/goproxy/issues/462 Work in PCs but shows error "WARN connect to tcp parent fail, ERR:cmd associate not supported" when try to connet in Android device ## Expected Behavior Android device can work ## Current Behavior Try to connect with Shadowrocket_9.6 / BifristV_0.6.3 / v2RayNG_1.3.1 , all not work ,came with same error ## Possible Solution ## Steps to Reproduce ## Context (Environment) proxy version is : commercial_11.3 full command is : proxy sps -S socks -T tcp -p :12345 -a aa:bb:500:0: -P socks5://xxxx:xxx@a.b.c.d system is : ubuntu 20.4 Below is full log 2022/01/10 13:46:23.537152 WARN connect to tcp parent fail, ERR:cmd associate not supported, form: 8.218.14.68:51755 from 8.218.14.68:51755 2022/01/10 13:46:23.946307 WARN connect to tcp parent fail, ERR:cmd associate not supported, form: 8.218.14.68:51757 from 8.218.14.68:51757 2022/01/10 13:46:23.946606 WARN connect to tcp parent fail, ERR:cmd associate not supported, form: 8.218.14.68:51759 from 8.218.14.68:51759 2022/01/10 13:46:23.948229 WARN connect to tcp parent fail, ERR:cmd associate not supported, form: 8.218.14.68:51756 from 8.218.14.68:51756 2022/01/10 13:46:25.386507 WARN connect to tcp parent fail, ERR:cmd associate not supported, form: 8.218.14.68:51771 from 8.218.14.68:51771 2022/01/10 13:46:25.794262 WARN connect to tcp parent fail, ERR:cmd associate not supported, form: 8.218.14.68:51775 from 8.218.14.68:51775 2022/01/10 13:46:25.800645 WARN connect to tcp parent fail, ERR:cmd associate not supported, form: 8.218.14.68:51774 from 8.218.14.68:51774 2022/01/10 13:46:25.995680 WARN connect to tcp parent fail, ERR:cmd associate not supported, form: 8.218.14.68:51778 from 8.218.14.68:51778
kerem closed this issue 2026-02-27 23:16:39 +03:00
kerem commented 2026-02-27 23:16:40 +03:00
Author
Owner
Copy link

@snail007 commented on GitHub (Jan 11, 2022):

sdk's sps is commercial edition feature

<!-- gh-comment-id:1009519219 --> @snail007 commented on GitHub (Jan 11, 2022): sdk's sps is commercial edition feature
kerem commented 2026-02-27 23:16:40 +03:00
Author
Owner
Copy link

@Raymond-C commented on GitHub (Jan 11, 2022):

Hi, I am testing with commercial Version

And I have further findings:
Even though I am visiting same destination, Android APP request in UDP protocol while Win/IOS program request in TCP protocol.

The proxy can run after dropping the parent node

proxy sps -S socks --udp-port 0 --udp -T tcp -p :12345 -a aa:bb:500:0:

If parent node is no authenticated one, below command can work perfect,too

proxy sps -S socks --udp-port 0 --udp -T tcp -p :12345 -a aa:bb:500:0: -P socks5://1.2.3.4:8080

However, I am expecting to use with authenticated parent like socks5://a:b@1.2.3.4:8080

proxy sps -S socks --udp-port 0 --udp -T tcp -p :12345 -a aa:bb:500:0: -P socks5://a:b@1.2.3.4:8080

and get some new errors

2022/01/11 02:43:02.517423 WARN udp outgoing error: proxy: SOCKS5 proxy at 0.0.0.0:0 failed to connect: command not supported
2022/01/11 02:43:02.601543 WARN udp outgoing error: proxy: SOCKS5 proxy at 0.0.0.0:0 failed to connect: command not supported

Is there any way to resolve this issue?

<!-- gh-comment-id:1009554610 --> @Raymond-C commented on GitHub (Jan 11, 2022): Hi, I am testing with commercial Version And I have further findings: Even though I am visiting same destination, Android APP request in UDP protocol while Win/IOS program request in TCP protocol. The proxy can run after dropping the parent node > `proxy sps -S socks --udp-port 0 --udp -T tcp -p :12345 -a aa:bb:500:0:` If parent node is no authenticated one, below command can work perfect,too > `proxy sps -S socks --udp-port 0 --udp -T tcp -p :12345 -a aa:bb:500:0: -P socks5://1.2.3.4:8080` However, I am expecting to use with authenticated parent like `socks5://a:b@1.2.3.4:8080` > `proxy sps -S socks --udp-port 0 --udp -T tcp -p :12345 -a aa:bb:500:0: -P socks5://a:b@1.2.3.4:8080` and get some new errors ``` 2022/01/11 02:43:02.517423 WARN udp outgoing error: proxy: SOCKS5 proxy at 0.0.0.0:0 failed to connect: command not supported 2022/01/11 02:43:02.601543 WARN udp outgoing error: proxy: SOCKS5 proxy at 0.0.0.0:0 failed to connect: command not supported ``` Is there any way to resolve this issue?
kerem commented 2026-02-27 23:16:40 +03:00
Author
Owner
Copy link

@snail007 commented on GitHub (Jan 11, 2022):

pls supply the "Steps to Reproduce", in order to debug the issue fastly.

<!-- gh-comment-id:1009587550 --> @snail007 commented on GitHub (Jan 11, 2022): pls supply the "Steps to Reproduce", in order to debug the issue fastly.
kerem commented 2026-02-27 23:16:40 +03:00
Author
Owner
Copy link

@Raymond-C commented on GitHub (Mar 8, 2022):

Seems to be DNS issue
If I define a specified DNS address is Android setting,the issue will be solved
The PC software will set a random DNS by default while Android one not

<!-- gh-comment-id:1062110687 --> @Raymond-C commented on GitHub (Mar 8, 2022): Seems to be DNS issue If I define a specified DNS address is Android setting,the issue will be solved The PC software will set a random DNS by default while Android one not
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
v15.2
v15.1
v15.0
Labels
Clear labels   
TODO

   
bug

   
duplicate

   
enhancement

   
good first issue

   
help wanted

   
helpful

   
invalid

   
need-confirm

   
pull-request

Mirrored from GitHub Pull Request

  
question

   
wontfix
No labels
TODO
bug
duplicate
enhancement
good first issue
help wanted
helpful
invalid
need-confirm
pull-request
question
wontfix
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/goproxy#369
No description provided.