SOLVED - 25.7.2 shadowsocks broken

[akolman]

Hotfix is now live.

I take it that means I'm OK to run opnsense-patch?  Will be happy to test if so.  Would the command just be:

    # opnsense-patch -c plugins 0354e18?

No need to install the patch, just check for updates.

Ah, splendid.  Thanks!  Up and running.

[eguun]

Hi @maurice

Could you please also enable this update for aarch64?

"check for update" doesn't load the updated plugin (while it works for the x64 repo counterpart)

Danke schön


Edit:
Discussed offline with @maurice, this will be featured in next update for aarch64

Cheers

[beren]

So this was fun, i checked github before here. I'm still having trouble however, sslocal is only listening on 120.0.0.1 not my lan ip that I have set in the conf.

<29>1 2025-08-27T19:15:40-04:00 OPNsense.mid-earth.net daemon 8434 - [meta sequenceId="13"] 2025-08-27T19:15:40.957292457-04:00  INFO shadowsocks local 1.23.4 build 2025-08-21T03:52:31.256707422+00:00
<29>1 2025-08-27T19:15:40-04:00 OPNsense.mid-earth.net daemon 8434 - [meta sequenceId="14"] 2025-08-27T19:15:40.957724556-04:00  INFO shadowsocks socks TCP listening on 127.0.0.1:1080
<29>1 2025-08-27T19:15:40-04:00 OPNsense.mid-earth.net daemon 8434 - [meta sequenceId="15"] 2025-08-27T19:15:40.957743247-04:00  INFO shadowsocks socks5 UDP listening on 127.0.0.1:1080

[Slashing]

Maybe you are specifying a "Server Address"? And not a "Local Address"?

[beren]

Well, under the ShadowSocks: Local I have server address and port set, and local address 10.0.0.1 and local port 1080. I can see in the logs it's binding to 127.0.0.1 port 1080.
The server is set to 127.0.0.1 and port 8388.

I have not changed the config since it was working for the past couple years and use it with FoxyProxy on some of my machines.

I even checked the config.xml and it's correct. For now I was able to rig it to work with port forwarding but that's not ideal.

[franco]

What amazes me is that this stuff wasn't touched for years and apparently used successfully. Now there's an upstream change breaking this intermittently and suddenly "other" issues appear, because "others" have "similar" issues that they post about. 95% of the time these posts correlate with people updating (also likely including a reboot).

Now with that cleared:


If you suspect the config is not written correctly check the config files first. Make sure you applied the changes so that the service can rewrite the config and restart itself. Make sure you check the right file. Make sure that when it's not changing you remove the config file and hit apply to see if a new file is created at all.

If all these are still leading to a file that is wrong check the values filled out by the template, maybe they are filling out the wrong value or you filled out the wrong value perhaps.

None of this is magic. Starting at the "it doesn't do it" end is tedious to start helping when literally anything (including nothing) could be wrong.

So... where are we at?


Cheers,
Franco

[franco]

This is helpful: https://github.com/opnsense/ports/pull/235

Thanks!

[franco]

How about this one?

# opnsense-patch https://github.com/opnsense/plugins/commit/3a3984f01

Needs a service restart (apply) from the GUI.


Cheers,
Franco