Tranquil IT Forum

Hello,

Following an SSL error during package installation via the secondary repository, I modified the repository rules in WAPT to switch the secondary repository from HTTPS to HTTP. However, even after this change, package downloads only work from the command prompt using "wapt-get install", and not via the console (no installation message, just a package list update).

All certificates have been verified, and I confirm that we only have one certificate to sign the packages.

If anyone has encountered this problem before or has any suggestions for resolving it, I would be grateful for any help.



Thank you in advance!

Best regards,
Julien

Hi Julien,

normally the service regularly retrieves the rules.json file which defines the secondary repository rules. Launching it from the command line bypasses the service and should make the call directly, but it's not normal that the agent isn't switching over automatically.

For the machine in question, what information do you have regarding repo_url and rules in the machine's hardware inventory?

Regards,

Denis

Hello,

thank you for your reply.
In repo_url, I have "http://occ005907.occitanie.cci.fr/wapt"
(the rules are attached).
As soon as I remove the rule, everything works.

Thank you.

Hello, as I haven't received a response, I'm taking the liberty of bringing the subject up again.
When I start an installation, I get an update with this message:

Get packages index from [ http://occ005907/wapt verify_cert=C:\Program Files (x86)\wapt\ssl\server\wapt-test.occitanie.cci.fr.crt client_cert_path=C:\Program Files)waptprivate4c4c4544-0036-3310-8048- c8c04f533933.crt >
x86package(s) in repository

But no installation from the secondary depot