Howdy all,

The new Webmin, and it's tighter referer checking, has caused some issues with our automated installation process.

I've just rolled out new virtualmin-base packages for all supported platforms that corrects this issue. If you have been bitten by the issue during installation, you probably don't have to start from scratch to get things spinning smoothly. I believe you can get a correctly configured system with the following steps:

CentOS/RHEL/Fedora:

Code:

rpm -e virtualmin-base yum install virtualmin-base

Debian/Ubuntu:

Code:

dpkg -r virtualmin-base apt-get install virtualmin-base

I haven't actually tested this very much, but I wanted to get the word out about the issue, since it can seem very frustrating to complete the installation and find a seemingly minimal system (all of the packages are correctly installed...but this doesn't switch everything over to looking like Virtualmin and doesn't configure all of the packages to work with Virtualmin, so it looks like it just installed Webmin and nothing else happened).

As always, file a ticket if you're running into problems and we'll help you get it straightened out.

THIS SUCKED !!!

webmin completely killed VM2 and VM pro and all my themes and modules...... I am not happy

THIS SUCKED !!!

webmin completely killed VM2 and VM pro and all my themes and modules...... I am not happy

Hey Scott,

I have no idea what you're talking about. This post is about botched installations--e.g. fresh systems that never got off the ground. It has nothing to do with systems that are already successfully installed. It can only make things better on a broken installation (since the issue it's meant to address is a failed installation).

all i did was install the update and when it was done all i had left was standard webmin install

i wasn't happy

What update are you talking about?

Again, this thread is about a fresh installation. Updating virtualmin-base shouldn't have any impact on your system at all, as the post installation script (the only thing contained in virtualmin-base) never runs when upgrading the package--only when doing a fresh install (which is what the steps above do).

You didn't follow the above steps on a running Virtualmin system, did you!?

"as the post installation script (the only thing contained in virtualmin-base) never runs when upgrading the package--only when doing a fresh install"

THIS IS NOT TRUE!

Frankly I am less then impressed with the new webmin.

Frankly I am less then impressed with the new webmin.

I still have no idea what you're talking about. What exactly are you seeing wrong with the new Webmin? (And why are we talking about it in a thread about virtualmin-base?)

I'm thoroughly confused...no one is telling me what they're seeing that is so dramatic and terrible. Scott's saying Webmin removed Virtualmin...but I don't see any way it possible could. Perhaps it switched the theme to the default Webmin theme? Or are you saying the Virtualmin package is actually gone?

Updating webmin does NOT transfer ANY modules from the old version to the new version. What you get is a fresh install of webmin.