Hi,
Multiple things : there are two different ticket templates to use for this :
- https://pagure.io/centos-infra/new_issue/?template=mirror-request-legacy (like for this one)
- https://pagure.io/centos-infra/new_issue/?template=mirror-request (for centos stream 9 and beyond)

So can you create a different ticket for Stream 9 ? (as you'll also need to have your mirror registered in mirrormanager - see https://wiki.centos.org/HowTos(2f)CreatePublicMirrors.html#CentOS_Stream_9)

For the "legacy" (that will disappear in June 2024) mirror network request (this one) I guess that url is http://mirrors.centos.behostings.net/centos (tried and it works) so I can add it but can you ensure that you also have rsync open ? it's unreachable for now :

>/dev/tcp/mirrors.centos.behostings.net/873
bash: connect: Connection timed out
bash: /dev/tcp/mirrors.centos.behostings.net/873: Connection timed out

Hi,

Thank you for the update.

1) Regarding "So can you create a different ticket for Stream 9 ?", I
have created a new request via
"https://pagure.io/centos-infra/new_issue/?template=mirror-request (for
centos stream 9 and beyond)"

2) Regarding RSYNC, we have opened the port 873. Please have a check now.

Thank you.

On 24-11-2023 16:36, Fabian Arrotin wrote:

arrfab added a new comment to an issue you are following:
``
Hi,
Multiple things : there are two different ticket templates to use for this :
- https://pagure.io/centos-infra/new_issue/?template=mirror-request-legacy (like for this one)
- https://pagure.io/centos-infra/new_issue/?template=mirror-request (for centos stream 9 and beyond)

So can you create a different ticket for Stream 9 ? (as you'll also need to have your mirror registered in mirrormanager - see https://wiki.centos.org/HowTos(2f)CreatePublicMirrors.html#CentOS_Stream_9)

For the "legacy" (that will disappear in June 2024) mirror network request (this one) I guess that url is http://mirrors.centos.behostings.net/centos (tried and it works) so I can add it but can you ensure that you also have rsync open ? it's unreachable for now :

```

/dev/tcp/mirrors.centos.behostings.net/873
bash: connect: Connection timed out
bash: /dev/tcp/mirrors.centos.behostings.net/873: Connection timed out
```

``

To reply, visit the link below or just reply to this email
https://pagure.io/centos-infra/issue/1322

yes, working now.
your mirror was added btw, and ip added in the ACL already so all good now

Hi,

Regarding:

~~~~
For the "legacy" (that will disappear in June 2024) mirror network request (this one) I guess that url is http://mirrors.centos.behostings.net/centos (tried and it works) so I can add it but can you ensure that you also have rsync open ? it's unreachable for now :
~~~

We cannot find our other centos versions mirror in mirror list "https://www.centos.org/download/mirrors/"

Our other centos versions link is >> http://mirrors.centos.behostings.net/centos

it will only appear there if valid/up2date and as you can see on https://mirror-status.centos.org/#be , your mirror is already 2+days old so not current anymore

Hi,

Thank you.

Could you please update the bandwidth to 10000 Mbps for "centos9" mirror, as have update from 1250 Mbps to 10000 Mbps.

Thank you.

it's a field/setting you can manage yourself in mirrormanager on your host : https://admin.fedoraproject.org/mirrormanager/host/2991 ;-)

Okay, thank you for the update.

Also, one more question. we have create a vault for centos, so how can we get listed in >> https://vault.centos.org/ ?

vault.centos.org is itself fully backed by AWS Cloudfront CDN, so no need to add mirror for the vault network, itself disappearing soon as not needed anymore when centos 7 will be EOL

wait I don't understand your last statement

vault.centos.org is going away when CentOS 7 goes EOL?

that sounds like a reason to mirror it all the more.

what I meant was that it will be just static archive in aws, not receiving any content anymore, as starting from stream 9 (and beyond) src.rpm are to be found on https://mirror.stream.centos.org instead , next to binary packages :)

Thank you for this update.

but we want to participate of the archiving of old linux solution , because in specific case sometime people need to download old version and we are happy to participate from archiving of old data 🙂

Thank you for this update.

but we want to participate of the archiving of old linux solution , because in specific case sometime people need to download old version and we are happy to participate from archiving of old data 🙂

Yes I understand your proposal but as said, https://vault.centos.org is redirecting only to AWS CDN (Cloudfront), backed from some machines sponsored by AWS so no need to add more to the pool :-)