I can't get my secondary repositories to use HTTPS.
When I change the repository URL, the agent can no longer find it.
- Screenshot 2026-08-31 104015.png (9.72 KB) Viewed 17160 times
THANKS
Secondary repositories using HTTPS
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
-
dcardon
- WAPT Expert
- Messages: 1988
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
Hi Clément,
which CA did the certificates deployed to the secondary repositories come from? Is this CA recognized by the WAPT agent?
Regards,
Denis
which CA did the certificates deployed to the secondary repositories come from? Is this CA recognized by the WAPT agent?
Regards,
Denis
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
The repositories contain the certificates of the technicians who have console access in the folder C:\Program Files (x86)\wapt\ssl,
and the certificate of the main server in C:\Program Files (x86)\wapt\ssl\server.
They also have the remote-repo-http package without any special configuration.
and the certificate of the main server in C:\Program Files (x86)\wapt\ssl\server.
They also have the remote-repo-http package without any special configuration.
-
sfonteneau
- WAPT Expert
- Messages: 2363
- Registered: July 10, 2014 - 11:52 PM
- Contact :
If you want an HTTPS repository, you need a Public Key Infrastructure (PKI
. You must create a certificate issued by a Certificate Authority (CA) (which you already have, such as OpenSSL, ADCS, or another) for your repositories and your WAPT server.
Then, in `verify_cert` (wapt-get.ini), you must specify your CA.
This will enable valid HTTPS validation.
. You must create a certificate issued by a Certificate Authority (CA) (which you already have, such as OpenSSL, ADCS, or another) for your repositories and your WAPT server.
Then, in `verify_cert` (wapt-get.ini), you must specify your CA.
This will enable valid HTTPS validation.
