Hello,
Server: Debian 9 / WAPT 1.5.1.21
Dev machine / Windows 10
I created a secondary repository, but when I try to install a package on my dev machine from this repository, I get SSL errors. I imagine I need to import the certificate, but I don't know where to find it, or where to put it afterward.
I haven't seen anything about this in the documentation: https://www.wapt.fr/fr/doc/Replicate_Mu ... index.html
If someone could explain this to me...
Thanks in advance.
AND
PS to the admins: I asked this question in the "WAPT packages" section of the forum (along with other questions, by the way). After thinking about it, I thought this might be a more appropriate place... but I can't seem to move the message.
SSL problem on secondary repository
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
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
Good morning
To understand this better:
https://www.wapt.fr/fr/doc/Configuratio ... at-ssl-tls
You have several options; you can generate a CA for HTTPS certificate verification, then simply add the CA as a path for verify_cert.
Another solution is to create an allcert.crt file and place it in ssl\server\
This file will contain all the certificates from the different repositories, allowing for proper verification.
Otherwise, activate a on the customers
To understand this better:
https://www.wapt.fr/fr/doc/Configuratio ... at-ssl-tls
You have several options; you can generate a CA for HTTPS certificate verification, then simply add the CA as a path for verify_cert.
Another solution is to create an allcert.crt file and place it in ssl\server\
This file will contain all the certificates from the different repositories, allowing for proper verification.
Otherwise, activate a
Code: Select all
wapt-get enable-check-certificateHello,
thank you for your reply.
The documentation you provided, and the `wapt-get enable-check-certificate` command, allow me to retrieve the server's certificate. I have no problem with this certificate.
The problem lies with the secondary repository's certificate (only tis-waptrepo is installed on this server).
thank you for your reply.
The documentation you provided, and the `wapt-get enable-check-certificate` command, allow me to retrieve the server's certificate. I have no problem with this certificate.
The problem lies with the secondary repository's certificate (only tis-waptrepo is installed on this server).
Okay,
so I just tried retrieving a package from a web browser. It shed some light on the situation (why didn't I think of that before?).
I do have a certificate problem, but not the one I expected: "
The certificate is not trusted because it is self-signed.
The certificate is only valid for ancien-hostname.
" The created certificate doesn't have the correct hostname ("ancien-hostname" in the lines above). This machine is a virtual server, deployed from a template, and the certificate took the template's name, not the machine's name (which I did change before installing everything else).
Anyway, do you have any idea how I can regenerate an HTTPS certificate on this machine?
Thanks in advance
.
so I just tried retrieving a package from a web browser. It shed some light on the situation (why didn't I think of that before?).
I do have a certificate problem, but not the one I expected: "
The certificate is not trusted because it is self-signed.
The certificate is only valid for ancien-hostname.
" The created certificate doesn't have the correct hostname ("ancien-hostname" in the lines above). This machine is a virtual server, deployed from a template, and the certificate took the template's name, not the machine's name (which I did change before installing everything else).
Anyway, do you have any idea how I can regenerate an HTTPS certificate on this machine?
Thanks in advance
.
