Skip to main content
Question

Centreon package repository

  • August 22, 2023
  • 10 replies
  • 461 views
S
Forum|alt.badge.img+6

Hello there,

 

There is a issue when we try to setup the centreon repositories:

deb https://packages.centreon.com/apt-plugins-stable/ bullseye main
deb https://packages.centreon.com/apt-standard-23.04-stable/ bullseye main


because, apt will try to connect to another address/domains than centreon.com :

jfrog-prod-euw1-shared-ireland-main.s3.amazonaws.com:443

This is bad because we can’t go and only allow the connections to *.centreon.com on our configurations/firewall/proxy, but we need to allow connections to *.s3.amazonaws.com on the list of allowed domains too.

 

Do you see the problem ?? Can you check and fix it ??

 

Thanks in advance.

10 replies

lpinsivy
Centreonian
Forum|alt.badge.img+21
  • lpinsivy
  • Centreonian
  • August 30, 2023

Hi @supervhs we made some changes, can you test?

S
Forum|alt.badge.img+6
  • supervhs
  • Author
  • Steward **
  • September 3, 2023

Hi,

 

not sure why my reply didn’t have been published !!! 

 

Writing it again, the changes are partially OK, some repositories/packages (centreon, centreon-poller) are only going to centreon.com, but others (centreon-connector. centreon-connector-ssh, centreon-connector-perl and perhaps oterhs) are still going to jfrog-prod-euw1-shared-ireland-main.s3.amazonaws.com:443

 

Thanks and attentive

lpinsivy
Centreonian
Forum|alt.badge.img+21
  • lpinsivy
  • Centreonian
  • September 4, 2023

Hi @supervhs do you use a proxy to access to Centreon repository?

S
Forum|alt.badge.img+6
  • supervhs
  • Author
  • Steward **
  • September 4, 2023

Yes..  why ?? 

the problem/redirect happened not only using proxy, but without proxy too.

 

 

lpinsivy
Centreonian
Forum|alt.badge.img+21
  • lpinsivy
  • Centreonian
  • September 4, 2023

We made some test since we fixed it and we don’t reproduce this issue.

S
Forum|alt.badge.img+6
  • supervhs
  • Author
  • Steward **
  • September 4, 2023

Hi,

Now it is working (inclusive for the centreon-connector-* packages).

Thanks

    E
    • edup
    • Steward *
    • October 24, 2024

    Hello,

    We got the same problem for a few days in a redhat environnement.
    Everything was working fine a few days ago.

    Could you check ?

     

    Here are some logs from our proxy. It seems a HTTP403 is sent by jfrog :

    Oct 24 16:55:20 hostname (squid-1)[781616]: [24/Oct/2024:16:55:20 +0000]    213 <server_ip> TCP_TUNNEL/200 6291 CONNECT packages.centreon.com:443 - HIER_DIRECT/52.49.160.245 -
    Oct 24 16:55:20 hostname (squid-1)[781616]: [24/Oct/2024:16:55:20 +0000]    103 <server_ip> TCP_TUNNEL/200 6291 CONNECT packages.centreon.com:443 - HIER_DIRECT/52.49.160.245 -
    Oct 24 16:55:21 hostname (squid-1)[781616]: [24/Oct/2024:16:55:21 +0000]     23 <server_ip> TCP_DENIED/403 4048 CONNECT jfrog-prod-euw1-shared-ireland-main.s3.amazonaws.com:443 - HIER_NONE/- text/html
    Oct 24 16:55:21 hostname (squid-1)[781616]: [24/Oct/2024:16:55:21 +0000]      0 <server_ip> TCP_DENIED/403 4048 CONNECT jfrog-prod-euw1-shared-ireland-main.s3.amazonaws.com:443 - HIER_NONE/- text/html
    Oct 24 16:55:21 hostname (squid-1)[781616]: [24/Oct/2024:16:55:21 +0000]      0 <server_ip> TCP_DENIED/403 4048 CONNECT jfrog-prod-euw1-shared-ireland-main.s3.amazonaws.com:443 - HIER_NONE/- text/html
    Oct 24 16:55:21 hostname (squid-1)[781616]: [24/Oct/2024:16:55:21 +0000]      0 <server_ip> TCP_DENIED/403 4048 CONNECT jfrog-prod-euw1-shared-ireland-main.s3.amazonaws.com:44

     

    A curl issued from the proxy a random internet host shows the same result :

    curl https://jfrog-prod-euw1-shared-ireland-main.s3.amazonaws.com
    <?xml version="1.0" encoding="UTF-8"?>
    <Error><Code>AccessDenied</Code><Message>Access Denied</Message><RequestId>MAZWF3PM31T19PXN</RequestId><HostId>/YyPgAM6h92gShCGKaPGba7ynjQMsaYdycHoFVBeqkjjw7I9AY8PbzhOJA9+QIAqSBmO6dkkzFI=</HostId></Error>

     

    -iv version of curl :

    < HTTP/1.1 403 Forbidden
    HTTP/1.1 403 Forbidden
    < x-amz-bucket-region: eu-west-1
    x-amz-bucket-region: eu-west-1
    < x-amz-request-id: RQ2W2AVYNEG8NZ6J
    x-amz-request-id: RQ2W2AVYNEG8NZ6J
    < x-amz-id-2: meBU10rLhH4neR6zF/wsoUQv8nOf4AaFzZRMEkzpVCkRf81dWmi7IyrFVAtt/snm3d/fjgWtB4Y=
    x-amz-id-2: meBU10rLhH4neR6zF/wsoUQv8nOf4AaFzZRMEkzpVCkRf81dWmi7IyrFVAtt/snm3d/fjgWtB4Y=
    < Content-Type: application/xml
    Content-Type: application/xml
    < Transfer-Encoding: chunked
    Transfer-Encoding: chunked
    < Date: Thu, 24 Oct 2024 15:14:37 GMT
    Date: Thu, 24 Oct 2024 15:14:37 GMT
    < Server: AmazonS3
    Server: AmazonS3

    < 
    <?xml version="1.0" encoding="UTF-8"?>

     

    Could you help ?

     

    Thanks in advance

     

    P
    Forum|alt.badge.img
    • PierreN
    • Steward *
    • November 2, 2024

    I also have the problem from a few days. We have some denied access on our proxy for the jfrog domain.

     

    Could you check if there were some changes on your repositories? 

    lpinsivy
    Centreonian
    Forum|alt.badge.img+21
    • lpinsivy
    • Centreonian
    • November 4, 2024

    Hi, you repo url is something like: https://packages.centreon.com/rpm-standard/

    P
    Forum|alt.badge.img
    • PierreN
    • Steward *
    • November 5, 2024

    Hi, you repo url is something like: https://packages.centreon.com/rpm-standard/

    Yes we didn't modify the url repositories and since 2 weeks at least, we have the new queries for the jfrog domain

    PS: our environment is redhat based

    Terms & ConditionsAccessibility statement