On my Webmin Configuration page in version 2.202, there is no Upgrade Webmin icon. I have version 2.301 installed on another similar server so I know an update is available and it does have an Update Webmin icon. On the version 2.202 dashboard, Package updates says: “All installed packages are up to date”. So webmin doesn’t show up as a package YUM can update.
What is the best way to update to the latest version?
Both servers are the identical version of Centos 7 and thus both EOL. Nonetheless one got updated to the latest and one doesn’t have that option. Both had always previously updated just fine even after Centos went EOL. The repository is already configured. It is enabled in the repository list like this:
No change in the repository list, still says: Index of /download/newkey/yum
Having the repository in the list should allow yum to do an update. But yum says there is no update to version 2.202.
So how did my other server get version 2.301 installed?
I wasn’t aware that YUM could be used to install RPM files. I found the syntax and an interesting comment on the web:
yum install RPM-FILENAME.rpm from the directory you have the package downloaded to.
This has the benefit that if the package requires extra dependencies, they will be found, downloaded, and installed; while a plain rpm will just complain that the dependencies are missing.
Because you should use your system package manager to upgrade, if possible. (Which also appears in Webmin in the GUI. It’s not like this is hiding updates. Something is just wrong with your configuration/system/network that hasn’t yet been identified, I guess.)
It’s not clear to me why the updated package wasn’t available from the repo, though? That’s normally how you should get updates, and I see the 2.301 package in the repo metadata.
So, why can’t your server fetch the updated metadata?
I don’t have dnf, only yum. The Webmin package update system always starts with this:
Clearing package caches …
… done
But it always said this even after Webmin 2.301 was available:
Re-fetching available packages …
… found 0 possible updates
I did finally discover that the Webmin.com Download page required clicking a button to display a list of installation files that can be downloaded. Unfortunately clicking the RPM option resulted in this:
An error has been encountered in accessing this page.
1. Server:webmin.com 2. URL path: /download/rpm/webmin-current.rpm 3. Error notes: Server unable to read htaccess file, denying access to be safe 4. Error type: 403 5. Request method: GET 6. Request query string: NONE 7. Time: 2025-02-24 19:27:56 UTC (1740425276)
Reporting this problem: The problem you have encountered is with a project web site hosted by SourceForge.net. This issue should be reported to the SourceForge.net-hosted project (not to SourceForge.net).
If this is a severe or recurring/persistent problem, please do one of the following, and provide the error text (numbered 1 through 7, above):
1. Contact the project via their designated support resources. 2. Contact the project administrators of this project via email (see the upper right-hand corner of the Project Summary page for their usernames) at user-name@users.sourceforge.net
NOTE: As of 2008-10-23 directory index display has been disabled by default. This option may be re-enabled by the project by placing a file with the name “.htaccess” with this line:
*** Options +Indexes***
That’s not the “correct” address, it’s just another one. The SourceForge one should also work. I can’t fix it, as I don’t have access to the Webmin SourceForge project, but maybe @Jamie can.
But, almost everyone (like 99% of people using any of the popular Linux distributions) should be using their package manager to install Webmin rather than downloading the package directly.
@richard47 which page are you referring to that has the incorrect instructions? I wasn’t able to re-produce that error fetching /download/rpm/webmin-current.rpm
Same here, no errors now, so it was a temporary glitch I stumbled upon. Nonetheless, if you are inclined you might consider not hiding the four manual installation options like this:
It doesn’t save much screen real estate and I didn’t realize I needed to click the triangle, especially since the mouse cursor changes into a magnifying glass typically used for images and frankly I thought it had something to do with “Older Versions” which I had no interest in.
