Hello dcardon, and thank you for your instructions.
Indeed, I didn't have the correct key, neither in C:\program files(x86)\wapt\ssl, nor in C:\program files(x86)\wapt\private, nor even in the old location C:\private.
Luckily, I was able to find the certificate and key used, in a...
The search returned 3 results
- April 18, 2023 - 3:55 PM
- Forum: WAPT Server
- Subject: [RESOLVED] [WAPT-Discovery 2.3.0.13516] Package updates no longer possible (setup.py not allowed in manifest)
- Answers: 5
- Views : 3518
- April 18, 2023 - 10:58
- Forum: WAPT Server
- Subject: [RESOLVED] [WAPT-Discovery 2.3.0.13516] Package updates no longer possible (setup.py not allowed in manifest)
- Answers: 5
- Views : 3518
Re: [WAPT-Discovery 2.3.0.13516] Package updates no longer possible (setup.py not allowed in manifest)
Hi Fabien,
it's very likely that the certificate being used is a non-code-signing certificate, which can only be used for configuring machines. We need to find the correct certificate, and that should fix it.
That said, the message isn't very clear; we'll see about making it clearer...
- April 18, 2023 - 09:26
- Forum: WAPT Server
- Subject: [RESOLVED] [WAPT-Discovery 2.3.0.13516] Package updates no longer possible (setup.py not allowed in manifest)
- Answers: 5
- Views : 3518
[RESOLVED] [WAPT-Discovery 2.3.0.13516] Package updates no longer possible (setup.py not allowed in manifest)
Hello everyone,
For about three weeks now, I've been encountering a strange problem that doesn't seem to be related to any update (or perhaps the update happened relatively seamlessly :D)
when I try to update packages on my private repository from the repositories of...
For about three weeks now, I've been encountering a strange problem that doesn't seem to be related to any update (or perhaps the update happened relatively seamlessly :D)
when I try to update packages on my private repository from the repositories of...
