Try adding http:// to the URL, it should work better.
Alexandre
Complete Wapt update from 1.3 to 1.5 on Debian
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
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
Are you trying to pull a Man in the Middle with your SonicWall?
Try adding http:// to the URL, it should work better.
Alexandre
Try adding http:// to the URL, it should work better.
Alexandre
-
Anthony Jimenez
- Messages: 17
- Registration: March 15, 2018 - 11:53
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.
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.
-
Anthony Jimenez
- Messages: 17
- Registration: March 15, 2018 - 11:53
Things are moving along, the installation is going well now...
To be continued
. Thanks A.
To be continued
. Thanks A.
-
Anthony Jimenez
- Messages: 17
- Registration: March 15, 2018 - 11:53
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?
I just entered the filename for my key, but I don't have the password for the private key.
How can I retrieve it?
-
dcardon
- WAPT Expert
- Messages: 1930
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
Hello Anthony,
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.
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).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?
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.
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
-
Anthony Jimenez
- Messages: 17
- Registration: March 15, 2018 - 11:53
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
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
