Unable to restart Waptserver 1.6 debian9

Questions about WAPT Server / Requests and help related to the WAPT server
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Locked
RUGAL
Messages: 2
Registration: Apr 17, 2019 - 1:56 p.m.

April 17, 2019 - 2:13 PM

Hello.
I'm having trouble with Waptserver installed on Debian 9.
It keeps crashing due to a 1/failure error.
Picture

Initially, the error was similar but with "Status=203/EXEC".
I managed to fix it by modifying the permissions on server.py as shown here,
Picture

but the server crashed immediately, and since then the error has been the one mentioned at the beginning.
As for the cause of all this, I couldn't say, but when it happened, I was using the console and encountered an "SSL3 wrong number, bad handshake" error on the Template repository. The server crashed shortly after.
RUGAL
Messages: 2
Registration: Apr 17, 2019 - 1:56 p.m.

April 18, 2019 - 4:31 PM

Problem solved.

The "postgres-9.6" service was down; don't confuse it with "postgres," which was up and misled me.
I must have made a mistake in my attempts to resolve this error (which is still present :? ).
Picture
Locked