Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't get public IP from ShadowSocks Rust #3834

Open
mvmaksnet opened this issue Mar 6, 2025 · 28 comments
Open

Can't get public IP from ShadowSocks Rust #3834

mvmaksnet opened this issue Mar 6, 2025 · 28 comments

Comments

@mvmaksnet
Copy link

Expected Behavior

It works but there is message on vps: Can't get public IP from ShadowSocks Rust

Current Behavior

Again like before one ISP can't work with multipath and it won't bond like other operators

Specifications

  • OpenMPTCProuter version: OpenMPTCProuter v0.62rc1-6.6
  • OpenMPTCProuter VPS version: 0.1032-test 6.12.15-x64v3-xanmod1
  • OpenMPTCProuter VPS provider: Maksnet
  • OpenMPTCProuter platform: x86_64

See picture:

Image

@Ysurac
Copy link
Owner

Ysurac commented Mar 6, 2025

Please the country in the template can also be needed.
"The multipath seems..." is only a warning, if aggregation use this interface no problem, else it's really blocked.
The "Can't get public IP" is a problem. It's working when you change proxy in System,=->OpenMPTCProuter, "Wizard" tab, "Check advanced settings" checkbox ?

@mvmaksnet
Copy link
Author

Serbia.

"Multipath seems.." is only for Yettel provider and it won't bond.
I solved this by checking box MPTCP over VPN on that network interface (for me it is WAN2) - now Yettel is working in bonding like other operators.

When I tried system>check advanced settings> then I lost internet at all on mptcp router.

@Ysurac
Copy link
Owner

Ysurac commented Mar 6, 2025

When you tried what ? the checkbox only display more option and change nothing by itself.

@mvmaksnet
Copy link
Author

What should I do when go to advanced settings?

@mvmaksnet
Copy link
Author

I have set Shadowsock instead of shadowsock rust. Now everything is working perfectly.

@Pajjja
Copy link

Pajjja commented Mar 7, 2025

I have the same problem with ShadowSocks Rust - what are the exact instructions to fix the issue? In which place do I need to change the values?

OpenMPTCProuter version: OpenMPTCProuter v0.62rc1-6.6
OpenMPTCProuter VPS version: KERNEL="6.6"
OpenMPTCProuter platform: x86_64

@Ysurac
Copy link
Owner

Ysurac commented Mar 7, 2025

I first need to find the issue...
What do you have in uci show shadowsocks-rust via SSH on the router ? (obfuscate the password if here)
And what VPS script did you use ?

@Andrik-user
Copy link

r0+28431-92e020b50f)


PACKAGE: openmptcprouter
VERSION: v0.62rc1
TARGET: rpi4
ARCH: aarch64_cortex-a72

BUILD REPO: https://github.com/ysurac/openmptcprouter
BUILD DATE: Fri Feb 28 16:36:02 UTC 2025

root@OpenMPTCProuter:# uci show shadowsocks-rust
shadowsocks-rust.hi1=ss_redir
shadowsocks-rust.hi1.server='sss0'
shadowsocks-rust.hi1.local_address='::'
shadowsocks-rust.hi1.local_port='1100'
shadowsocks-rust.hi1.mode='tcp_and_udp'
shadowsocks-rust.hi1.timeout='1000'
shadowsocks-rust.hi1.keep_alive='15'
shadowsocks-rust.hi1.fast_open='0'
shadowsocks-rust.hi1.verbose='0'
shadowsocks-rust.hi1.syslog='1'
shadowsocks-rust.hi1.reuse_port='0'
shadowsocks-rust.hi1.mptcp='1'
shadowsocks-rust.hi1.ipv6_first='1'
shadowsocks-rust.hi1.no_delay='1'
shadowsocks-rust.hi2=ss_redir
shadowsocks-rust.hi2.server='sss1'
shadowsocks-rust.hi2.local_address='::'
shadowsocks-rust.hi2.local_port='1101'
shadowsocks-rust.hi2.mode='tcp_and_udp'
shadowsocks-rust.hi2.timeout='1000'
shadowsocks-rust.hi2.keep_alive='15'
shadowsocks-rust.hi2.fast_open='0'
shadowsocks-rust.hi2.verbose='0'
shadowsocks-rust.hi2.syslog='1'
shadowsocks-rust.hi2.reuse_port='0'
shadowsocks-rust.hi2.mptcp='1'
shadowsocks-rust.hi2.ipv6_first='1'
shadowsocks-rust.hi2.no_delay='1'
shadowsocks-rust.ss_rules=ss_rules
shadowsocks-rust.ss_rules.disabled='0'
shadowsocks-rust.ss_rules.redir_tcp='all'
shadowsocks-rust.ss_rules.src_default='forward'
shadowsocks-rust.ss_rules.dst_default='forward'
shadowsocks-rust.ss_rules.local_default='forward'
shadowsocks-rust.ss_rules.server='sss0'
shadowsocks-rust.ss_rules.ifnames='lo' 'eth0' 'tun0'
shadowsocks-rust.sss0=server
shadowsocks-rust.sss0.disabled='0'
shadowsocks-rust.sss0.server='185.181.8.110'
shadowsocks-rust.sss0.server_port='65280'
shadowsocks-rust.sss0.method='2022-blake3-aes-256-gcm'
shadowsocks-rust.sss0.obfs='0'
shadowsocks-rust.sss0.password='cmREp6HXyfl+Wvh8Dj689PLCl2JuKVPVXrS7Ff0wcmw=:TVEfUq31v/TIMezatKpUw7U4IH2eH41S2rMJsVMp8SU='
shadowsocks-rust.sss1=server
shadowsocks-rust.sss1.disabled='1'
shadowsocks-rust.sss1.server='185.181.8.110'
shadowsocks-rust.sss1.server_port='65280'
shadowsocks-rust.sss1.method='2022-blake3-aes-256-gcm'
shadowsocks-rust.sss1.obfs='0'
shadowsocks-rust.sss1.password='cmREp6HXyfl+Wvh8Dj689PLCl2JuKVPVXrS7Ff0wcmw=:TVEfUq31v/TIMezatKpUw7U4IH2eH41S2rMJsVMp8SU='
shadowsocks-rust.dns=ss_tunnel
shadowsocks-rust.dns.disabled='1'
shadowsocks-rust.dns.mode='tcp_and_udp'
shadowsocks-rust.dns.server='sss0'
shadowsocks-rust.dns.local_port='5353'
shadowsocks-rust.dns.forward_address='8.8.8.8'
shadowsocks-rust.dns.forward_port='53'
shadowsocks-rust.tracker_sss0=ss_local
shadowsocks-rust.tracker_sss0.server='sss0'
shadowsocks-rust.tracker_sss0.local_address='127.0.0.1'
shadowsocks-rust.tracker_sss0.local_port='1111'
shadowsocks-rust.tracker_sss0.mode='tcp_and_udp'
shadowsocks-rust.tracker_sss0.timeout='600'
shadowsocks-rust.tracker_sss0.keep_alive='15'
shadowsocks-rust.tracker_sss0.fast_open='0'
shadowsocks-rust.tracker_sss0.syslog='0'
shadowsocks-rust.tracker_sss0.reuse_port='1'
shadowsocks-rust.tracker_sss0.mptcp='1'
shadowsocks-rust.tracker_sss0.verbose='0'
root@OpenMPTCProuter:
#

@Ysurac
Copy link
Owner

Ysurac commented Mar 8, 2025

What VPS script did you use ? rc1 URL script or snapshot script ?
I updated shadowsocks-go in snapshot, maybe a problem here... Can you give me the result of journalctl -u shadowsocks-go on the VPS (about 10 latest lines) ?
And then, can you test rc1 script ?

@Andrik-user
Copy link

Image

VPS script: wget -O - https://www.openmptcprouter.com/server-rc/debian-x86_64.sh | KERNEL="6.12" sh
OpenMPTCprouter v0.62rc1 here: https://download.openmptcprouter.com/release/v0.62rc1-6.6/

Mar 08 16:11:03 mp12tcp systemd[1]: Stopped shadowsocks-go.service - shadowsocks-go Service.
Mar 08 16:11:03 mp12tcp systemd[1]: Started shadowsocks-go.service - shadowsocks-go Service.
Mar 08 16:11:03 mp12tcp shadowsocks-go[42167]: 2025-03-08T16:11:03.680-0500 FATAL Failed to load config {"confPath": "/etc/shadowsocks-go/server.json", "error": "json: unknown field "listeners""}
Mar 08 16:11:03 mp12tcp systemd[1]: shadowsocks-go.service: Main process exited, code=exited, status=1/FAILURE
Mar 08 16:11:03 mp12tcp systemd[1]: shadowsocks-go.service: Failed with result 'exit-code'.
Mar 08 16:11:03 mp12tcp systemd[1]: shadowsocks-go.service: Scheduled restart job, restart counter is at 524.
Mar 08 16:11:03 mp12tcp systemd[1]: Stopped shadowsocks-go.service - shadowsocks-go Service.
Mar 08 16:11:03 mp12tcp systemd[1]: Started shadowsocks-go.service - shadowsocks-go Service.
Mar 08 16:11:03 mp12tcp shadowsocks-go[42171]: 2025-03-08T16:11:03.931-0500 FATAL Failed to load config {"confPath": "/etc/shadowsocks-go/server.json", "error": "json: unknown field "listeners""}
Mar 08 16:11:03 mp12tcp systemd[1]: shadowsocks-go.service: Main process exited, code=exited, status=1/FAILURE
Mar 08 16:11:03 mp12tcp systemd[1]: shadowsocks-go.service: Failed with result 'exit-code'.
Mar 08 16:11:04 mp12tcp systemd[1]: shadowsocks-go.service: Scheduled restart job, restart counter is at 525.
Mar 08 16:11:04 mp12tcp systemd[1]: Stopped shadowsocks-go.service - shadowsocks-go Service.
Mar 08 16:11:04 mp12tcp systemd[1]: Started shadowsocks-go.service - shadowsocks-go Service.
Mar 08 16:11:04 mp12tcp shadowsocks-go[42207]: 2025-03-08T16:11:04.179-0500 FATAL Failed to load config {"confPath": "/etc/shadowsocks-go/server.json", "error": "json: unknown field "listeners""}
Mar 08 16:11:04 mp12tcp systemd[1]: shadowsocks-go.service: Main process exited, code=exited, status=1/FAILURE
Mar 08 16:11:04 mp12tcp systemd[1]: shadowsocks-go.service: Failed with result 'exit-code'.
Mar 08 16:11:04 mp12tcp systemd[1]: shadowsocks-go.service: Scheduled restart job, restart counter is at 526.
Mar 08 16:11:04 mp12tcp systemd[1]: Stopped shadowsocks-go.service - shadowsocks-go Service.
Mar 08 16:11:04 mp12tcp systemd[1]: Started shadowsocks-go.service - shadowsocks-go Service.
Mar 08 16:11:04 mp12tcp shadowsocks-go[42243]: 2025-03-08T16:11:04.431-0500 FATAL Failed to load config {"confPath": "/etc/shadowsocks-go/server.json", "error": "json: unknown field "listeners""}
Mar 08 16:11:04 mp12tcp systemd[1]: shadowsocks-go.service: Main process exited, code=exited, status=1/FAILURE
Mar 08 16:11:04 mp12tcp systemd[1]: shadowsocks-go.service: Failed with result 'exit-code'.
Mar 08 16:11:04 mp12tcp systemd[1]: shadowsocks-go.service: Scheduled restart job, restart counter is at 527.
Mar 08 16:11:04 mp12tcp systemd[1]: Stopped shadowsocks-go.service - shadowsocks-go Service.

@Ysurac
Copy link
Owner

Ysurac commented Mar 9, 2025

ok, an error in the config.
Can you give me the result on the server of cat /etc/shadowsocks-go/server.json ?

@Andrik-user
Copy link

root@mp12tcp:# cat /etc/shadowsocks-go/server.json
{
"servers": [
{
"name": "ss-2022",
"protocol": "2022-blake3-aes-256-gcm",
"tcpListeners": [
{
"network": "tcp",
"address": ":65280",
"fastOpen": false,
"reusePort": false,
"multipath": true
}
],
"enableTCP": true,
"listenerTFO": true,
"enableUDP": true,
"mtu": 1500,
"psk": "5Ry4ogZM5WabVthmUFsTBkevO07UlXkpT1OtWGb/RYI=",
"uPSKStorePath": "/etc/shadowsocks-go/upsks.json"
}
],
"stats": {
"enabled": true
},
"api": {
"enabled": true,
"debugPprof": false,
"trustedProxies": [],
"listeners": [
{
"network": "tcp",
"address": "127.0.0.1:65279"
}
]
}
root@mp12tcp:
#

@Ysurac
Copy link
Owner

Ysurac commented Mar 9, 2025

Should be fixed in rc and snapshot script, you can run it again.

@Andrik-user
Copy link

Now everything works.

@mvmaksnet
Copy link
Author

Should we update VPS to make SC RUST work as it should?

@Ysurac
Copy link
Owner

Ysurac commented Mar 10, 2025

What you mean ?

@mvmaksnet
Copy link
Author

Cant get public ip address for sc rust.
How to solve this?
Shadowssocks works but shadowsocks rust don't work.

@Ysurac
Copy link
Owner

Ysurac commented Mar 10, 2025

As it's indicated, should work with latest VPS script.

@mvmaksnet
Copy link
Author

mvmaksnet commented Mar 10, 2025 via email

@Ysurac
Copy link
Owner

Ysurac commented Mar 10, 2025

Yes. Same VPS script is used to install and update. Here you have to run it again to fixe issue.

@mvmaksnet
Copy link
Author

mvmaksnet commented Mar 11, 2025

I have tested it. IT WORKS NOW.
Thank you very much.

For one operator Yettel I was forced to enable mptcp over vpn and now this provider work in bonding like other operaors.

Image

Image

@DENZAKIN
Copy link

DENZAKIN commented Mar 14, 2025

I get the same error, how do I fix it? I tried snapshot, same error.

FATAL Failed to load config {"confPath": "/etc/shadowsocks-go/server.json", "error": "illegal base64 data at input byte 0"}
in process exited, code=exited, status=1/FAILURE

@Ysurac
Copy link
Owner

Ysurac commented Mar 15, 2025

Not the same error, can you copy /etc/shadowsocks-go/server.json from VPS here ?

@DENZAKIN
Copy link

{
"servers": [
{
"name": "ss-2022",
"protocol": "2022-blake3-aes-256-gcm",
"tcpListeners": [
{
"network": "tcp",
"address": ":65280",
"fastOpen": false,
"reusePort": false,
"multipath": true
}
],
"listenerTFO": true,
"enableUDP": true,
"mtu": 1500,
"psk": "bjKkU/9JVBw1/zH8T2vBUyVK0VuigykRpUyB5ZFUcyw=",
"uPSKStorePath": "/etc/shadowsocks-go/upsks.json"
}
],
"stats": {
"enabled": true
},
"api": {
"enabled": true,
"debugPprof": false,
"trustedProxies": [],
"listen": "127.0.0.1:65279"
}

@Ysurac
Copy link
Owner

Ysurac commented Mar 15, 2025

Update VPS script.

@DENZAKIN
Copy link

DENZAKIN commented Mar 15, 2025

I was using the snapshot script and the latest standard script and was getting the same error. I decided to use the
debian9-x86_64.sh script because you edited it recently and the error persisted.

@Ysurac
Copy link
Owner

Ysurac commented Mar 15, 2025

I would need same /etc/shadowsocks-go/server.json file and journalctl -u shadowsocks-go on the VPS.

@DENZAKIN
Copy link

DENZAKIN commented Mar 17, 2025

I was able to get everything green quickly by using the or command or (in case of failure). :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants
@Ysurac @DENZAKIN @mvmaksnet @Pajjja @Andrik-user and others