[RESOLVED] Update 2.4 to 2.5: Problem accessing the Wapt store with a proxy
Published: 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
.
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
.