albony mirror has https to http redirect issues

[Chandramauli-Arm64]

I just opened termux and tried to update( pkg update & pkg upgrade) as usual and then this mirror issue occurred:-

Checking availability of current mirror:
[*] https://mirror.albony.in/termux/termux-main: ok
Ign:1 https://mirror.albony.in/termux/termux-main stable InRelease
Err:2 https://mirror.albony.in/termux/termux-main stable Release
  Redirection from https to 'http://mirror.hyd.albony.in/termux/termux-main/dists/stable/Release' is forbidden [IP: 64:ff9b::52b4:91c4 443]
Reading package lists... Done
E: The repository 'https://mirror.albony.in/termux/termux-main stable Release' does not have a Release file.
N: Metadata integrity can't be verified, repository is disabled now.
N: Possible causes: unstable or tampered Internet connection, wrong sources.list, outdated keyring or host is down currently.
N: Please note that all hosting problems or other serious issues we announce on our social media pages.
N: Use termux-change-repo for switching to a mirror.

As usual this occurs 1 or 2 times in a month. So, How much time will you guys take to fix this? I am willing to wait for this because I don't want to change the mirror and it becomes very slow.

Environment details:-

Termux :- 0.118.3
Os:- RealmeUI 6 ( Android 15)
Mirror:- Asia.
Smartphone:- REALME P1 5G.

Thankyou.

[thunder-coding]

You are using an older version of termux-tools. So you can change your mirror using termux-change-repo, just switch to a mirror group of your geographical location and perform pkg upgrade. That should fix the mirror issues for you.

@2096779623 I see that this user has older version of termux-tools installed. but the change to mirror you did in 36d0779 is not accurate. You seem to have used whatever domain you got redirected to from mirror.albony.in, this mirror seems to have multiple locations in India. for instance I got redirected to http://mirror.hyd.albony.in/ as well as http://mirror.nag.albony.in/ randomly. Both domains have separate ip addresses as well.

@Albonycal can you fix your redirects to use https when connected to mirror.albony.in via https. Also I think DNS-based load-balancing should work better for end-users as users don't have to reach out to central server each time for getting what server to reach out to. Should cut the latency by a huge margin. If users want to pin their mirror location, they can always do so by using those specific domains

I am not someone who usually deals with mirrors. So pinging you @2096779623

[robertkirkman]

Albony mirror URL will be updated when this PR is finished. I don't know if that will fix this problem or not, but it will result in the Albony mirror URL changing.

• [DO NOT MERGE] [TRACKER] Apt 3.1.x termux-packages#24212

also, the reason termux-tools is not currently updated is because agnostic-apollo decided it needs to stay at version 1.45.0 here termux/termux-packages@7786d1d

I don't know the exact reason why that is, because termux-tools 1.46.0 and newer are also compatible with Apt 2.8

[2096779623]

You seem to have used whatever domain you got redirected to from mirror.albony.in, this mirror seems to have multiple locations in India.

I think it was an additional node added after I submitted it and I didn't know about it.

Temporary workaround:

find $PREFIX/etc/apt -name '*.list' -type f -exec sed -i 's/mirror.albony.in/mirror.hyd.albony.in/g' {} \; && if echo $SHELL | grep -q fish; then echo 'set -x TERMUX_PKG_NO_MIRROR_SELECT 1' >> ~/.config/fish/config.fish; else echo 'export TERMUX_PKG_NO_MIRROR_SELECT=1' >> ~/.$(basename $SHELL)rc; fi

[TomJo2000]

You seem to have used whatever domain you got redirected to from mirror.albony.in, this mirror seems to have multiple locations in India.

I think it was an additional node added after I submitted it and I didn't know about it.

Temporary workaround:

find $PREFIX/etc/apt -name '*.list' -type f -exec sed -i 's/mirror.albony.in/mirror.hyd.albony.in/g' {} ;
echo 'export TERMUX_PKG_NO_MIRROR_SELECT=1' >> ~/.$(basename $SHELL)rc

That workaround isn't gonna work for fish users.

[agnostic-apollo]

I reverted/blocked the update because at the time apt3 changes weren't tested fully and work was ongoing on the termux-packages side. If you guys have tested enough and are confident in updating before apt3 work on termux-packages side is complete and that update wont break apt2 users, you can push a release, but I may not be available for any fixes for at least a week if something breaks, wrapping something else up.

[robertkirkman]

I just checked again and it's still working with apt 2.8 with no noticeable problems, but since it's in TomJo2000's PR I guess I have been waiting for TomJo2000 to also test it and to decide whether to make a separate PR for it or not, to make sure multiple people have checked it for problems.

[Albonycal]

@Albonycal can you fix your redirects to use https when connected to mirror.albony.in via https. Also I think DNS-based load-balancing should work better for end-users as users don't have to reach out to central server each time for getting what server to reach out to. Should cut the latency by a huge margin. If users want to pin their mirror location, they can always do so by using those specific domains

Hi, yes I'll look into this

[Albonycal]

HI, I have implemented DNS based load-balancing. This should be fixed now.

Thanks

[thunder-coding]

Thanks, can confirm that the DNS based load-balancing is working on my end (in India). There are occassional SERVFAIL with DNS I can see in my testing though. Are you currently (between your comment and in the time I commented) making some configuration changes?

[Albonycal]

Yes I made some changes. DNS based loadbalancing was on my mind since a long time hence most of the setup was already ready for this change, there were some issues with TLS cert which prevented me from moving to it.

But everything should work fine now.

Thanks

[Chandramauli-Arm64]

Yes I made some changes. DNS based loadbalancing was on my mind since a long time hence most of the setup was already ready for this change, there were some issues with TLS cert which prevented me from moving to it.

But everything should work fine now.

Thanks

Thanks.