[SOLVED] Error during duplication of package(s)

Questions about WAPT Packaging / Requests and help regarding Wapt packages.
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
Locked
screams
Messages: 2
Registration: December 15, 2022 - 4:52 PM

August 5, 2024 - 09:32

Hello everyone,

We recently upgraded our server to version 2.5 Enterprise. Everything worked after changing the TLS version to 1.2 in the Nginx configuration.
Client updates worked, as did package updates.

However, for the past few days, we haven't been able to update packages.

We get the following message:
Error duplicating packet(s): package name:THttpClientSocket.Wget:....:442/wapt/package name fails as 400 Bad Request
<html>
<head><title>400 The plain HTTP request was sent to HTTPS port</title></head>
<body>
<center><h1>400 bad Request</<h1></center>
<center>The plain HTTP request was sent to HTTPS port</center>
<hr><center>ngxinx</center>
</body>
</html>


We can't see where the problem could be coming from... a certificate issue...?

Thank you in advance for your help.
Attachments
Screenshot 2024-08-05 085401.png
Screenshot 2024-08-05 085401.png (102.4 KB) Viewed 4624 times
Last edited by cris on August 6, 2024 - 09:42, edited 1 time.
User avatar
t.heroult
Messages: 307
Registration: December 8, 2020 - 10:13 AM

August 5, 2024 - 3:54 PM

Hello,
I'm joining this request.
Since today only, and not on all packages, some work fine.
I should point out that in my case, nothing has changed in the server configuration, which has been up to date for a while.
Server: WAPT Enterprise 2.6.1.17786 on Debian
Consoles: Windows 10 & 11
Infrastructure: Windows

Did you know? When parrotfish undergo smoltification, their osmoregulation mechanism is reversed!
User avatar
kguerineau
Messages: 26
Registration: March 6, 2018 - 4:28 PM

August 6, 2024 - 09:25

Hello,

the problem was related to a misconfiguration on the Wapt store. This should now be resolved.

Have a good day
screams
Messages: 2
Registration: December 15, 2022 - 4:52 PM

August 6, 2024 - 09:37

I confirm ;) everything is back to normal, thank you.
User avatar
t.heroult
Messages: 307
Registration: December 8, 2020 - 10:13 AM

August 6, 2024 - 10:00

Everything is OK for me too, thank you!
Server: WAPT Enterprise 2.6.1.17786 on Debian
Consoles: Windows 10 & 11
Infrastructure: Windows

Did you know? When parrotfish undergo smoltification, their osmoregulation mechanism is reversed!
Locked