http://5566971:8wzUFnnGGb@software.virtualmin.com/rhel/6/x86_64/repodata/1c0276087a565feb5d755c9a233398599e5c8cd0-filelists.sqlite.bz2: [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 401"
Trying other mirror.
Error: failure: repodata/1c0276087a565feb5d755c9a233398599e5c8cd0-filelists.sqlite.bz2 from virtualmin: [Errno 256] No more mirrors to try.
http://5566971:8wzUFnnGGb@software.virtualmin.com/rhel/6/x86_64/repodata/repomd.xml: [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 401"
Trying other mirror.
http://5566971:8wzUFnnGGb@software.virtualmin.com/universal/repodata/repomd.xml: [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 401"
Trying other mirror.
Resolving Dependencies
Cleared yum cache and got
http://5566971:8wzUFnnGGb@software.virtualmin.com/rhel/6/x86_64/repodata/repomd.xml: [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 401"
Trying other mirror.
Error: Cannot retrieve repository metadata (repomd.xml) for repository: virtualmin. Please verify its path and try again
well first of all you compromised your license key and as it is saying on this screenshot here you just did that (if you read that red warning msg please):
You compromised this by including on forums - public section of the forums with the lines starting http://5566971:8wzUFnnGGb which does give an glue to anyone. You should really open issue with virtualmin folks here at: https://www.virtualmin.com/node/add/project-issue and mark post private - so you would not share information like this out to public.
401 Authorization Required = This means that the page or server requires that the visitors authenticate with their username and password. If they fail to do that, the server returns this error message (403). In your case that’s license key and license number which you did already compromised by posting it here. I would open new private issue here at: https://www.virtualmin.com/node/add/project-issue and told them what you have done by mistake, they would help you in no time. Perhaps you looking for new keys and best bet would be talking directly privately to virtualmin folks. Keep your keys private at all times!
This license expired in 2017. You’ll want to buy a new license, and use the virtualmin change-license command to update to the new one. It looks like it ended because your billing details no longer worked for billing, and we were unable to contact you to update them. No big deal, just buy a new one and update.
Also, as unborn notes, don’t include license details when posting public questions. The issue tracker defaults to private and is always the best way to get a prompt response to any questions about Virtualmin Pro, so you can post anything you like in the issue tracker…we don’t need to see the license key, generally, but including it in a private issue in the tracker is harmless. But, including it here in the public forums is a bad idea. If this were an active license we’d need to issue a new key for you, to prevent abuse.
Edit: Also make sure your email address on file with us is correct, so we can contact you if any problems with billing come up in the future. Check your spam folder to make sure we aren’t ending up there, as well.
AH got it, I downgraded to GPL last 2017 and it’s only now that I’ve updated for a long time. Changed my license too. Somehow, virtualmin.repo was not updated. I copied my other GPL installation’s repo file, as well as downloaded the GPG key and yum worked.
