Page 2 of 2

Re: Complete Wapt update from 1.3 to 1.5 on Debian

Published: March 22, 2018 - 3:24 PM
by agauvrit
Are you trying to pull a Man in the Middle with your SonicWall? ;)

Try adding http:// to the URL, it should work better.

Alexandre

Re: Complete Wapt update from 1.3 to 1.5 on Debian

Published: March 22, 2018 - 3:56 PM
by Anthony Jimenez
Still nothing!
Same error!

Error: The certificate for "wapt.tranquil.it" is not trusted.
Error: The certificate for "wapt.tranquil.it" is not from a known issuer.
gpg: no valid OpenPGP data found.

Re: Complete Wapt update from 1.3 to 1.5 on Debian

Published: March 22, 2018 - 4:11 PM
by Anthony Jimenez
Things are moving along, the installation is going well now...
To be continued

. Thanks A.

Re: Complete Wapt update from 1.3 to 1.5 on Debian

Published: March 22, 2018 - 4:44 PM
by Anthony Jimenez
The Wapt server is installed.

I just entered the filename for my key, but I don't have the password for the private key.

How can I retrieve it?

Re: Complete Wapt update from 1.3 to 1.5 on Debian

Published: March 22, 2018 - 5:25 PM
by dcardon
Hello Anthony,
Anthony JIMENEZ wrote: March 22, 2018 - 4:44 PM The Wapt server is installed.

I just entered my key filename, but I don't have the private key password.

How can I retrieve it?
In version 1.3, by default there was no password on the private key (although the WAPT 1.3 environment already supported password-protected keys).

From version 1.5 onwards, the installer requires a password on the key for better security.

So if you are migrating from version 1.3 to 1.5, it is very likely that there is no password on the old key. However, you must set a password to generate the new key/certificate.

Sincerely,

Denis

PS: If you are already using WAPT 1.5 and have lost the key password, you will need to generate a new certificate and re-upload it to all workstations. There is no way to recover the password.

Re: Complete Wapt update from 1.3 to 1.5 on Debian

Published: March 27, 2018 - 09:01
by Anthony Jimenez
Hello,

the WAPT server is operational except that when I try to access my repository at https://myserver.com/wapt/
I get a 403 Forbidden error (nginx/1.10.3).

It's definitely an access problem, but which files need to have their access rights changed?
Thank you