[RESOLVED] Update 2.4 to 2.5: Problem accessing the Wapt store with a proxy

Questions about WAPT Server / Requests and help related to the WAPT server
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
VERGEZ
Messages: 1
Registration: February 21, 2024 - 4:07 PM

February 21, 2024 - 5:05 PM

Hello,

WAPT version installed: 2.5.4.15342 Enterprise
- Server OS (Linux/Windows): Windows Server 2022.

During the upgrade from version 2.4 to 2.5.4.15342 Enterprise, we are trying to access updates from the WAPT store (updates from the store). These updates, which previously appeared in red in version 2.4, no longer appear in version 2.5.

We are using a private IP address from our university for our server, behind a Squid proxy for HTTP and HTTPS protocols.

We have correctly configured the proxy settings in the external repository tab, but it no longer works for updating packages from our private repository via the store.

To test for a few minutes: We added a second network card with a public IP address to our WAPT server, which was previously using a private IP address, and we removed the proxy information from the console for a few minutes. We went to our private repository and we again see the new versions of our packages to update, highlighted in red. We can update them from the "Update from the store" menu, just like in version 2.4.

When we switch our WAPT server back to a private IP address with a proxy, we can no longer update packages from the store.

Can you tell us what protocols are used to access the WAPT store via the proxy for these package updates? Is it TCP 443 to the store and TLS 1.2?

We have a configuration with a WAPT 2.5 server behind a Squid proxy for HTTP and HTTPS (for a university). Should we check anything on the proxy side?

Thank you for your help

.
User avatar
sfonteneau
WAPT Expert
Messages: 2318
Registered: July 10, 2014 - 11:52 PM
Contact :

February 21, 2024 - 5:36 PM

I have the impression that your problem is related to this one:
viewtopic.php?t=3756

Are you using the "import from internet" button?

Simon
Locked