Hi, https://mirror-master.debian.org/status/mirror-info/debian-mirror.behostings.net.html doesn't go back far enough to show what the problem was, but the negative "score" column indicates that there was some kind of issue with the mirror recently. The score needs to stay positive for enough days, then it will get automatically included in the published list.
Regards, Adam On Fri, 2024-09-13 at 09:20 +0200, basi...@thgnet.net wrote: > Hi, > > Its been more than 13 days and our mirror has not been added to your > mirror list. > > Thank you. > > On 26-08-2024 15:32, Adam D. Barratt wrote: > > Hi, > > > > Yes, that seems like a reasonable solution. > > > > Regards, > > > > Adam > > > > On Mon, 2024-08-26 at 09:38 +0200, basi...@thgnet.net wrote: > > > Hi, currently, our "RSYNC_HOST="ftp.be.debian.org". > > > > > > so shall we change the rsync_host to "mirror.as35701.net" to fix > > > the > > > issue ? > > > > > > Awaiting your response. > > > > > > On 25-08-2024 17:35, Adam D. Barratt wrote: > > > > On Tue, 2024-08-20 at 15:32 +0000, basil mathews wrote: > > > > > Submission-Type: new > > > > > Site: debian-mirror.behostings.net > > > > Our automated checks noticed an issue with your setup: > > > > > > > > o We recommend mirrors not sync directly from service aliases > > > > such > > > > as > > > > ftp.<CC>.debian.org (only HTTP is guaranteed to be > > > > available at > > > > ftp.<CC> sites). Maybe change your config to sync from > > > > the site currently backing the ftp.<CC>.debian.org service > > > > you > > > > sync > > > > from? > > > > > > > > Regards, > > > > > > > > Adam >
