Skip to main content
Question

packages.centreon.com redirects all downloads to an S3 bucket again (Pulp) – breaks installs behind an allowlist

  • September 25, 2026
  • 1 reply
  • 16 views
Forum|alt.badge.img+5

Hello,

Since at least mid-September 2026, every download from packages.centreon.com (the .repo file, repodata and RPMs) is answered with a 302 redirect to centreon-delivery-pulp-packages-prod.s3.amazonaws.com (eu-west-1) with a pre-signed URL. Our servers are only allowed to reach *.centreon.com on the firewall, so the install/upgrade fails:
 

# dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el8/centreon-25.10.repo
Adding repo from: https://packages.centreon.com/rpm-standard/25.10/el8/centreon-25.10.repo
Curl error (35): SSL connect error for https://centreon-delivery-pulp-packages-prod.s3.amazonaws.com/artifact/a2/97161e...?response-content-disposition=attachment%3Bfilename%3Dcentreon-25.10.repo&X-Amz-...[redacted]
[OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to centreon-delivery-pulp-packages-prod.s3.amazonaws.com:443 ]
Error: Configuration of repo failed

 

Environment: AlmaLinux 8.10, Centreon 24.04 → upgrading to 25.10 on Oracle Linux 9, hosted on AWS EC2, outbound traffic restricted to an allowlist that we cannot change. A second server (fresh 25.10 install) is affected the same way.

This is the same situation as this thread from 2023: https://thewatch.centreon.com/centreon-it-100-users-54/centreon-package-repository-2154 - at that time the redirect went to a JFrog bucket, @lpinsivy fixed it server-side so that everything stayed on centreon.com, and it came back in Oct/Nov 2024 for two other users. It looks like the backend has now moved to Pulp with S3 storage and the redirect is back.

Thanks

1 reply

jmathis
Centreonian
Forum|alt.badge.img+2
  • jmathis
  • Centreonian
  • October 1, 2026

Hello Christopher,

Thanks for the detailed report, and apologies for the late reply.

You were right. Package downloads keep growing, so in mid-September we moved to a new repository infrastructure built to handle that volume. The first version of this setup redirected downloads to a storage hostname outside centreon.com, and that broke installs and upgrades for anyone whose firewall only allows *.centreon.com.

This has been fixed in production since September 25 (around 17:30 CEST). Every download, including redirects, is now served from packages.centreon.com, so your servers should only need to reach that hostname.

To confirm on your side:

dnf clean all
curl -sI https://packages.centreon.com/rpm-standard/25.10/el8/centreon-25.10.repo

The location: header should point to packages.centreon.com, not amazonaws.com. Then retry your dnf config-manager --add-repo / dnf update.

If you added the amazonaws.com hostname to your allowlist as a temporary workaround, you can now remove it.

If you still see a redirect to another hostname, please reply here with the full curl -sI output and the time of the test, and we'll look into it right away.

Thanks for your patience,

Terms & ConditionsAccessibility statement