Homeserver Forum

Unfortunately, things do not look good with DSM 7.

Synology does not allow packages running with root privileges with DSM 7.
During the beta there was a workaround (bug) https://community.synology.com/enu/forum/20/post/140589
but this has been blocked or fixed in the meantime.

Without root privileges Lights-Out can not do anything, neither monitor network traffic nor shutdown the server.

Whether the users are willing to edit files via SSH to give Lights-Out root rights is questionable.

I will prepare a test package to see what else needs to be changed, but simply installing it won't work.

The outcry in the community is so far also rather restrained and will certainly not move Synology to provide an option.

Greetings
Martin

I'll probably release a beta on Wednesday, and in it I'll describe the manual steps on how to get root privileges for Lights-Out again.

Regards
Martin

Here's the promised beta:
https://www.green-it-software.com/10289 ... available/

Have fun!
Martin

Hey,

I have uploaded the package to DSM 7.0, but I had to uninstall it after I realized Mono was not installed. I have now installed Mono, but I cannot reload the beta package. It gets stuck at "processing changes" right after I select the package for upload. Any idea how I could clean up the situation?

Have you run make-root via ssh?

I couldn't get there, because I cannot install Lights-Out at all. I have mono installed. When I try to do a manual install of the lights-out beta spk package, it doesn't even get to the warning about not being an official package. I just see "processing changes".
There may be some issue with left-overs from the previous successful installation/uninstallation and I guess there must be a way to use SSH to clean this up and make sure the next install is a clean install, but I am a noob with Linux admin and I am just stuck, not being able to install the beta package a second time.

Can you please add a screen shot of this message?

Hey,

So, I tried again today and it worked. I don't know what changed. I suspect my Firewalla home network security device was blocking some site,... and then stopped blocking it/them? Not sure.
At any rate I was able to reinstall the package and I will proceed with giving it the right privileges.

Here is what happened. I was successful at installing the package. I then tried to connect with the console from a Windows PC. That didn't work.


I looked around and found some posts about recreating the certificate. I deleted the certificate and rebooted the NAS. The certificate is back.


The reverse proxy looks correct.


However I cannot connect with the console.

NB> I tried to reinstall the package and got the same problem as before, FYI

Edited to remove usernam einfo

You have two issues. Let's try to answer each.

1. Successful installation, but failed login

That happens because you do not use the name of the NAs. The IP-Address does not work because the certificate only has the name. Please enter zpcloud without any port.


2. Unsuccessful reinstallation

Have you tried a NAS reboot?

"Processing. Please wait..." happens while the package gets uploaded to the NAS.
How long have you waited in that screen?

Which version have you tried to install? Build 4770 or 4775?
Which NAs are you using (model)?

Regards
Martin

Hello Martin,

1) I tried the IP address because using the name was generating unspecified errorrs, see below


I don't know if this is relevant by "ZPCloud" is also the name for quickconnect access

2) Yes, I have tried a NAS reboot. This is the only way I can get out of the Package Center Processing Changes situation. I have let that situation go on for about an hour, so I am not showing impatience either

I am using 3.7.0.4770

My NAS is a 718+ model

Thank you very much for your quick follow up!

Hello,

Today I installed the latest version 3.7.0.4775_Beta on Synology DSM 7 and the console on Windows 10. I still cannot connect to the server through the console. I cannot connect to it using the "join server application". Apparently from the logs, the console software cannot get the expected token upon connection:
With the previous version:

2021-09-24 19:34:33:438 [ 1] DEBUG UserCredentials.Login: start to get access token
2021-09-24 19:34:33:442 [ 1] DEBUG Testing with Tls, Tls11, Tls12=4032 -
2021-09-24 19:34:34:473 [ 15] DEBUG Success OK
2021-09-24 19:34:34:473 [ 1] DEBUG GetResourceOwnerTokenAsync: serverUri=https://zpcloud:7783/, credential=admin, otp=
2021-09-24 19:34:34:473 [ 1] DEBUG Started resource owner token request for admin on https://zpcloud:7783/token
2021-09-24 19:34:34:507 [ 1] ERROR Can't get token, HttpErrorStatusCode=0, HttpErrorReason=
2021-09-24 19:36:10:271 [ 1] DEBUG > LightsOutConsoleClosing, Size={Width=950, Height=640}/{Width=950, Height=640}, Location={X=50,Y=50}, WindowState=Normal
2021-09-24 19:36:10:398 [ 1] DEBUG Settings saved with backup
2021-09-24 19:36:10:398 [ 1] DEBUG < LightsOutConsoleClosing, Size={Width=950, Height=640}, Location={X=50,Y=50}, WindowState=Normal
2021-09-24 19:36:10:398 [ 1] DEBUG < LightsOutConsoleShown: Size={Width=950, Height=640}, Location={X=50,Y=50}, WindowState=Normal

With the latest version
2021-09-27 08:37:59:575 [ 1] DEBUG UserCredentials.Login: start to get access token
2021-09-27 08:37:59:575 [ 1] DEBUG Testing with Tls, Tls11, Tls12=4032 -
2021-09-27 08:38:00:640 [ 14] DEBUG Success OK
2021-09-27 08:38:00:640 [ 1] DEBUG GetResourceOwnerTokenAsync: serverUri=https://zpcloud:7783/, credential=[Correct USERNAME DELETED HERE], otp=
2021-09-27 08:38:00:640 [ 1] DEBUG Started resource owner token request for [Correct USERNAME DELETED HERE] on https://zpcloud:7783/token
2021-09-27 08:38:00:672 [ 1] ERROR Can't get token, HttpErrorStatusCode=0, HttpErrorReason=

Have you modified the default ports in Control Panel->Login Portal->DSM?
That's supported in the next build later today. If you changed the ports, then please reset to 5000/5001 and give it a try.

Martin

Hello,

I tried with the defaults port number but it still fails. The logs are now showing I cannot establish a secure channel:

2021-09-29 08:45:36:521 [ 1] DEBUG ---- UserCredentials.BtnLoginClick ----
2021-09-29 08:45:36:532 [ 1] DEBUG UserCredentials.Login: start to get access token
2021-09-29 08:45:36:532 [ 1] DEBUG Testing with Tls, Tls11, Tls12=4032 -
2021-09-29 08:45:37:559 [ 13] DEBUG Failed An error occurred while sending the request.
2021-09-29 08:45:37:559 [ 13] DEBUG System.Net.WebException: The request was aborted: Could not create SSL/TLS secure channel.
2021-09-29 08:45:37:567 [ 13] DEBUG Testing with Tls12=3072 -
2021-09-29 08:45:37:567 [ 13] DEBUG Failed An error occurred while sending the request.
2021-09-29 08:45:37:567 [ 13] DEBUG System.Net.WebException: The request was aborted: Could not create SSL/TLS secure channel.
2021-09-29 08:45:37:567 [ 13] DEBUG Testing with Tls11=768 -
2021-09-29 08:45:37:567 [ 13] DEBUG Failed An error occurred while sending the request.
2021-09-29 08:45:37:567 [ 13] DEBUG System.Net.WebException: The request was aborted: Could not create SSL/TLS secure channel.
2021-09-29 08:45:37:567 [ 13] DEBUG Testing with Tls=192 -
2021-09-29 08:45:37:581 [ 13] DEBUG Failed An error occurred while sending the request.
2021-09-29 08:45:37:581 [ 13] DEBUG System.Net.WebException: The request was aborted: Could not create SSL/TLS secure channel.
2021-09-29 08:45:37:581 [ 13] DEBUG Testing with Ssl3=48 -
2021-09-29 08:45:37:581 [ 13] DEBUG Failed An error occurred while sending the request.
2021-09-29 08:45:37:581 [ 13] DEBUG System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a receive.
2021-09-29 08:45:37:581 [ 13] DEBUG GetWorkingProtocolsDefault: https://zpcloud:7783/ - no working protocol found!
2021-09-29 08:45:37:581 [ 1] DEBUG SslClientSupport.DownloadCert: Trying to download new Root-CA from server http://zpcloud:7782/ to C:\ProgramData\LightsOut3\data\zpcloud-root-ca.cer
2021-09-29 08:45:38:618 [ 7] DEBUG SslClientSupport.DownloadCertAsFileAsync root-ca.cer, result OK size 1224
2021-09-29 08:45:38:633 [ 1] DEBUG SslClientSupport.DownloadCert: Root-CA downloaded, thumprint=10E0113AD8146FD21C678A2FF01C96470B352652
2021-09-29 08:45:38:633 [ 1] DEBUG SslClientSupport.InternalInstallSslCert: Adding cert to system trust
2021-09-29 08:45:38:646 [ 1] DEBUG InstallCerts.Install CurrentUser: Found Root-CA already in store with thumbprint 10E0113AD8146FD21C678A2FF01C96470B352652
2021-09-29 08:45:38:646 [ 1] DEBUG GetResourceOwnerTokenAsync: serverUri=https://zpcloud:7783/, credential=, otp=
2021-09-29 08:45:38:646 [ 1] DEBUG Started resource owner token request for [Username] on https://zpcloud:7783/token
2021-09-29 08:45:38:646 [ 1] ERROR Can't get token: An error occurred while sending the request.
2021-09-29 08:45:38:646 [ 1] ERROR Can't get token: The request was aborted: Could not create SSL/TLS secure channel.

Please upgrade to the latest build which works with changed ports also:
https://www.green-it-software.com/downl ... a-dsm7.spk

Run make-root again and click repair.

Try to log in via Console, then collect the logs on the NAS, see here https://help.green-it-software.com/help ... gyNAS.html

Send the logs to beta at green-it-software dot com.

Regards
Martin