-
Notifications
You must be signed in to change notification settings - Fork 218
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
SurveillanceStation not found after running the script #17
Comments
From what i can see, the issue is old, but what i found is upgrading to a newer version of Surveilance Station will not allow it to work. I had to disable the update feature in DSM and in the Settings of the Surveilance Station itself. |
We know that. We just need an update of the script.. But @Kaitiz has disappeared |
That's no how it work. Synology patch the exploit. Author must find a new exploit to make it work. It not as simple as "juste update the script". |
I know that, but since @Kaitiz don't answer anymore, it seems exactly that.. vanished :( |
And so what ? You can still downgrade your package to required one to make the patch work and if the upgrade notification annoyed you, you got the perfect answer from here : #13 (comment) :) |
I have a DS418 with DSM 7.0.1-42218 Update 2 and Surveillance Station 9.1.2.10854 installed.
After executing the "install_license" script, the Surveillance page became unavailable with this message:
"Sorry, the page you are looking for is not found."
This is the URL used:
https://MYSYNOLOGY_HOST/webman/3rdparty/SurveillanceStation/
After running the "remove_license" script everything went back to normal.
I tried to install the "SurveillanceStation-x86_64-9.1.2-10854.spk" package but it says "This package is not supported on the platform of DiskStation or is incompatible with the current DSM version.".
When trying to install the "SurveillanceStation-armv8-9.1.2-10854.spk" package it allows the installation.
This is the problem?
Do you have "libssutils.so" for the "armv8" version?
Can you help me?
Thanks.
The text was updated successfully, but these errors were encountered: