Hi! I can't start shadowbox.
There is an error when installing the plugin
Starting configd.
*** OPNsense\Shadowsocks\General migration failed from 0.0.0 to 1.0.1, check log for details
*** OPNsense\Shadowsocks\Local migration failed from 0.0.0 to 1.0.1, check log for details
When the service is forced to start, the status in the backend log is 127.
If you know, please tell me what I should pay attention to?
Hi,
To second this,
The "broken" shadowsocks correlates when shadowsocks plugin moved from deprecated libev to current rust, ref: https://github.com/opnsense/plugins/issues/4662
2 updates on OPNSense seems to still be required to finalize port from libev to rust:
1- OPNSense GUI still reference the libev filepath and needs update
when shadowsocks plugin is fresh installed in OPNSense GUI,
the page updating the settings (Services > ShadowSocks > Server) saves its content into /usr/local/etc/shadowsocks-libev/config.json instead of /usr/local/etc/shadowsocks-rust/config.json
2- demon start doesn't work from gui - but succeed from cli
Lobby > Dashboard > Services
shadowsocks daemon marked as down - clicking the start button doesn't succeed at launching the deamon
But overall the rust version seems to work:
Assuming settings are properly configured into the OPNSense GUI (Services > ShadowSocks > Server)
Launching this command successfully launches the process
/usr/local/bin/ssserver -c /usr/local/etc/shadowsocks-libev/config.json
Any advise on the process to get these updates into a future release/hotfix?
Cheers
I'm having what appears to be a similar issue. I have an Issue open on GitHub:
https://github.com/opnsense/plugins/issues/4910
@eguun Let me guess what happened here:
os-shadowsocks-devel 1.2 (which uses shadowsocks-rust) was released about a month ago with 25.1.12. Since no issues were reported, it was now moved to production in 25.7.2.
Since you initiated the switch, expectations were that you test the devel version and report potential issues. It seems this didn't happen.
Probably a misunderstanding?
Cheers
Maurice
If someone needs it and doesn't want to mess around, here's a quick-dirty solution.
Delete the files:
/etc/rc.conf.d/shadowsocks_libev
/etc/rc.conf.d/ss_local
/usr/local/etc/rc.d/opnsense-ss-local
/usr/local/opnsense/service/templates/OPNsense/Shadowsocks/shadowsocks_libev
/usr/local/opnsense/service/templates/OPNsense/Shadowsocks/ss_local
/usr/local/opnsense/service/templates/OPNsense/Shadowsocks/ss_local.conf
And copy the files from the attachment. A reboot may be necessary.
Can you provide a PR? I'd rather move this forwards than backwards ;)
FWIW, this should work for now:
# pkg install shadowsocks-libev
# opnsense-revert -r 25.7.1 os-shadowsocks
Cheers,
Franco
Quote from: Maurice on August 24, 2025, 08:53:51 PM@eguun Let me guess what happened here:
os-shadowsocks-devel 1.2 (which uses shadowsocks-rust) was released about a month ago with 25.1.12. Since no issues were reported, it was now moved to production in 25.7.2.
Since you initiated the switch, expectations were that you test the devel version and report potential issues. It seems this didn't happen.
Probably a misunderstanding?
Cheers
Maurice
Hi,
Spot on!
Big misunderstanding indeed: I was eagerly waiting for this release and only saw the new rust version pop in 25.7.2. I totally missed the memo that there's a devel/test version in the backstage.
Sorry to have dropped the ball here, I'll work on this PR to fix
Cheers
Quote from: franco on August 25, 2025, 10:00:39 AMCan you provide a PR? I'd rather move this forwards than backwards ;)
FWIW, this should work for now:
# pkg install shadowsocks-libev
# opnsense-revert -r 25.7.1 os-shadowsocks
Cheers,
Franco
Hi Franco,
I did a PR to match the content provided by slashing
https://github.com/opnsense/plugins/pull/4913
My first PR
Quote from: Slashing on August 24, 2025, 09:11:37 PMIf someone needs it and doesn't want to mess around, here's a quick-dirty solution.
Delete the files:
/etc/rc.conf.d/shadowsocks_libev
/etc/rc.conf.d/ss_local
/usr/local/etc/rc.d/opnsense-ss-local
/usr/local/opnsense/service/templates/OPNsense/Shadowsocks/shadowsocks_libev
/usr/local/opnsense/service/templates/OPNsense/Shadowsocks/ss_local
/usr/local/opnsense/service/templates/OPNsense/Shadowsocks/ss_local.conf
And copy the files from the attachment. A reboot may be necessary.
Thanks for this, this works (tested on both x64 and aarch64)
Dear all,
Quick update on this issue.
PR raised and merged: https://github.com/opnsense/plugins/pull/4913
Expected to be fixed in next update.
Great learning opportunity for me.
Sorry for missing action on the dev cycle
Kudos to Franco reactivity and support
Slashing: maybe mark this thread as solved?
If somebody can confirm our joint efforts on https://github.com/opnsense/plugins/commit/0354e1851 that would be nice. Not sure it opnsense-patches given that we moved some files for clarity.
As soon as I get an ok I will hotfix.
Hotfix is now live.
Quote from: franco on August 26, 2025, 01:03:10 PMHotfix 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?
Quote from: franco on August 26, 2025, 01:03:10 PMHotfix is now live.
bish bash bosh :)
Thank you all so much. You'r the best!!!
Quote from: akolman on August 26, 2025, 08:14:07 PMQuote from: franco on August 26, 2025, 01:03:10 PMHotfix 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.
Quote from: Slashing on August 26, 2025, 08:21:27 PMQuote from: akolman on August 26, 2025, 08:14:07 PMQuote from: franco on August 26, 2025, 01:03:10 PMHotfix 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.
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
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
Maybe you are specifying a "Server Address"? And not a "Local Address"?
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.
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
This is helpful: https://github.com/opnsense/ports/pull/235
Thanks!
How about this one?
# opnsense-patch https://github.com/opnsense/plugins/commit/3a3984f01
Needs a service restart (apply) from the GUI.
Cheers,
Franco