This means that I shouldn't really do anything and the best mirror would somehow be magically selected for me. This is however either misleading or completely false: while running zypper dup, I checked traffic with wireshark and all downloads were coming from downloadcontent.opensuse.org (195.135.221.157) which is the main download server in Germany and there are dozens of mirrors that are geographically closer to me.
download.opensuse.org mirror
Download Zip https://t.co/E3ay6H4lWx
The list also claims to be up-to-date, however it contains mirrors that are severely outdated, like 23Media GmbH, which was last updated in 2017 and is marked with 3 stars priority which seems to be the maximum. Super misleading.
Other sites work for me, including other sites under opensuse.org. I was able to switch over to provo-mirror.opensuse.org, but of course it lacks community repos (and, weirdly, openSUSE:/Factory:/NonFree/standard). Maybe DNS is resolving to a bad mirror?
Tangentially related question: if I wanted to run my own mirror (and mirror everything on download.opensuse.org, including community/OBS repos), how much disk space would I need? Ain't the first time download.opensuse.org has been funky for me right when I really need to install something, and running my own mirror would sidestep that issue.
The problem is the SSL certificate from this source is expired. I'm trying to change the source url to download this file without satisfactory results. I change mirrorlist with some valid sources, but always I tried to update I got the same result with the same source URL.
You have cached metadata about this repository that is no longer valid, or you have a network problem reaching the mirror. Start with a yum clean all and try again. If it still fails, start investigating the network stack. (Are you caching a bad DNS record on this host for download.opensuse.org, etc.)
Still no good news from the original machine. Meanwhile we changed the DNS entries to point to a mirror server in Provo. Please excuse the low bandwidth and delays for the moment, we are working on a permanent fix.
[ENG] Registered mirrors get access to stage.opensuse.org. This server provides the updated content of download.opensuse.org before the official release and has a higher transfer rate than the public servers. You may want to register for access at mailto:ftpadmin suse.de, if your mirror has at least a 100MBit connection, and if the conditions outlined in the following paragraph are met.
A few words about "staged content" up front. Staged content is content that is not meant to be public yet -- but which we still would like to spread to mirrors already, so that at the time of the public release it is already mirrored, and thereby accessible for many people. So how can that be achieved? We set the permissions of the directory to be protected to 'rwxr-x---' (0750). The directory is then served as part of the tree which is hosted on the stage rsync server. When mirrors sync from it, they will replicate those permissions. And when the to release has come, the directory permissions are changed to rwxr-xr-x (0755), and when the mirrors sync the next time, they catch up with it and the directory becomes accessible on their HTTP/FTP servers as well. This process of release by permission change is sometimes called "bit flip release".
You should be subscribed to the mirror mailing list (see bottom of this page), so we can keep you up to date with regard to ongoing release activities. We will inform you of the release schedule, and exact timing of public release -- and you can actively support us in fact.
If you provide this data in writing to mailto:ftpadmin suse.de, we will add your mirror to our mirror database. The mirror database is used by our download server to actively redirectclients to your server. We attempt to distribute requests on ageographical basis per client IP address. The amount of redirects issued also depends on a score which we will determine together with you, in order to match your capacities.
Furthermore, we actively monitor content on mirrors, so that we redirectonly to files which actually exists on them. rsync is themost efficient way to do this; scanning through 300.000 files might takeonly a few minutes with it. The second best method, if rsync isnot available, is via FTP, but it is much less efficient (takes considerably longer and places more load on your server). As last resort, wecan fall back to HTTP, if neither rsync nor FTP is available. But it crawls.Thus, please do consider adding an rsync module for opensuse content, whichallows for much faster scanning of your server.
You may also want to add your mirror to our official mirror list for the released versions or for the development builds, but those lists are not used for the download redirector and might be phased out later. These are wiki pages, simply hit the "Edit" button at the top ;)
The mirror opensuse.org mailing list (previously called suse-mirror suse.de) is low-traffic and used mainly for announcements. It is also a suitable place for discussions around mirroring openSUSE content, should the need arise. To subscribe, please write to mailto:mirror+subscribe opensuse.org and, since it is a closed list, also send a note to mailto:ftpadmin suse.de and ask to be added.
Then, we need rsync read access to scan your mirror for our download redirector. The download redirector database needs to be updated periodically so it reflects the actual files on your mirror. The scanning happens from 195.135.220.0/22.
This rsync server is open to anyone. It offers public access via rsync protocol to the download.opensuse.org content. Access is usually limited to 50 concurrent connections, so you might not always be able to access it. Some of the mirrors listed here might also offer rsync services.
Registered mirrors get access to stage.opensuse.org. This server provides the updated content of download.opensuse.org before the official release and has a higher transfer rate than the public servers. You may want to register for access at mailto:ftpadmin suse.de, if your mirror has at least a 100MBit connection, and if the conditions outlined in the following paragraph are met.
f448fe82f3