[ZendTo] 500 internal server error on user unlock

[Massimo Forni]

thank you as usual for the fastest reply in the west 😀



Sent from my iPhone

On 8 Oct 2020, at 17:27, Jules <Jules at zend.to> wrote:
 Hi Massimo,

Many thanks for reporting that. I missed one :-(

If you want to fix it yourself, it's very simple.
Edit /opt/zendto/www/unlock.php.
At line 78 you should see the line
        $theDropbox->authenticator()->validUsername($user, $props, $errormsg);
Replace that 1 line with these 2:
        $errormsg = '';
        $theDropbox->authenticator()->validUsername($user, $props, $errormsg);
and refresh the page in your web browser.
That should fix it.

Otherwise, the fix will be in the next beta.

As an alternative to the "unlock" page, there is a very simple "unlockuser" command in /opt/zendto/bin that you can run by hand on the command-line. Mostly you just want to do
    /opt/zendto/bin/unlockuser -a
to unlock all locked users.
Run it without the "-a" to see the usage.

Cheers,
Jules.


On 08/10/2020 15:48, Massimo Forni via ZendTo wrote:

--

Massimo Forni
ICT Infrastructure Manager

Mobile: +393474110278

________________________________

Turboden S.p.A. I via Cernaia 10 I 25124 Brescia I Italy
t. +39 030 3552001 I f. +39 030 3552011
www.turboden.com<http://www.turboden.com>


Confidentiality notice: this message, together with its attachments, may contain strictly confidential and/or legally privileged information and it is destined solely to the intended addressee(s), who only may use it under his/their responsibility. Opinions, conclusions and other information contained in this message, that do not relate to the official business of this firm, shall be considered as not given or endorsed by it. If you have received this communication in error, please notify us immediately by responding to this email and then delete it from your system. Any use, disclosure, copying or distribution of the contents of this communication by a not-intended recipient or in violation of the purposes of this communication is strictly prohibited and may be unlawful.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20201008/7d0b4ea3/attachment-0001.html>