I am trying to login to MirrorManager to make some changes but am unable to
do so. When I login, I get the above error (OpenID request was cancelled).
This is happening in Chrome and Firefox for me.
Anyone else having the same issue?
Hi, please add this server to your public Fedora Epel mirror list:
Sync schedule: Every 6 hrs
Sponsor: Silknet JSC
Sponsor URL: https://silknet.com/
IPv4 address to authorize: 126.96.36.199
Email contact: itavartkiladze(a)silknet.com<mailto:email@example.com>
Mirroring AltArch: no
Tel: +995 32 2100000 ext: 1505
+995 32 2770100 ext: 7634
3, Gotua str, Right Side of the River Mtkvari
This message (including any attachments) is confidential and may be privileged. If you have received it by mistake please notify the sender by return e-mail and delete this message from your system. Any unauthorized use or dissemination of this message in whole or in part is strictly prohibited. Please note that e-mails are susceptible to change. Silknet shall not be responsible nor liable for the proper and complete transmission of the information contained in this communication nor for any delay in its receipt or damage to your system. Silknet does not guarantee that the integrity of this communication has been maintained nor that this communication is free of viruses, interceptions or interference
I am sending this to identify myself according to the instructions on the
mirror-list subscription page. I do not have any knowledge or experience
about any related projects. I am just trying to follow the instructions
from the article at this url:
I found this article while looking for a way to alleviate the very slow
times for the automatic repository refresh step when using dnf commands. I
am not sure I will have the time, resources, or proficiency to complete
more than the first few steps.
We've been seeing this intermittently but with increasing frequency of late: the filelist provided does not match the contents of the mirror (kernel.org in our case) which results in a lot of "No such file or directory" errors spammed out from the quick-fedora-mirror script.
Is this something we should try to tune on our end or is there a sync issue upstream from us which needs to be looked into?