Why virtualmin-lemp-stack 7.0.5-1 update wants to install Apache2 and bunch of packages

SYSTEM INFORMATION
OS type and version Debian Linux 12
Webmin version 2.010
Virtualmin version 2.111
Related packages virtualmin-lemp-stack

Hello guys!

I got an update for virtualmin-lemp-stack and I recognized that it wants to install Apache2 however I use Nginx as webserver.
It also wants to install some new packages which were not needed before.
Why?
How to update this properly?

Thank you for help!

Hitting update button after some hours it wants less packages.
Does it seem fine?

Why did it want to install Apache before?
Was it a bug?

Edit:

I’ve updated it from SSH with apt-get upgrade command.

root@s1:~# apt-get upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  virtualmin-config virtualmin-lemp-stack
2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 53.1 kB of archives.
After this operation, 1024 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 https://software.virtualmin.com/vm/7/gpl/apt virtualmin/main amd64 virtualmin-config all 7.0.21 [39.1 kB]
Get:2 https://software.virtualmin.com/vm/7/gpl/apt virtualmin/main amd64 virtualmin-lemp-stack all 7.0.6-1 [14.0 kB]
Fetched 53.1 kB in 1s (86.4 kB/s)               
[master acc947d] saving uncommitted changes in /etc prior to apt run
 44 files changed, 702 insertions(+), 5 deletions(-)
 create mode 100644 letsencrypt/csr/0136_csr-certbot.pem
 create mode 100644 letsencrypt/csr/0137_csr-certbot.pem
 create mode 100644 letsencrypt/csr/0138_csr-certbot.pem
 create mode 100644 letsencrypt/csr/0139_csr-certbot.pem
 create mode 100644 letsencrypt/csr/0140_csr-certbot.pem
 create mode 100644 letsencrypt/csr/0141_csr-certbot.pem
 create mode 100644 letsencrypt/csr/0142_csr-certbot.pem
 create mode 100644 letsencrypt/csr/0143_csr-certbot.pem
 create mode 100644 letsencrypt/csr/0144_csr-certbot.pem
 create mode 100644 letsencrypt/csr/0145_csr-certbot.pem
 create mode 100644 letsencrypt/csr/0146_csr-certbot.pem
 create mode 100644 letsencrypt/csr/0147_csr-certbot.pem
 create mode 100644 letsencrypt/csr/0148_csr-certbot.pem
 create mode 100644 letsencrypt/csr/0149_csr-certbot.pem
 create mode 100644 letsencrypt/csr/0150_csr-certbot.pem
 create mode 100644 letsencrypt/csr/0151_csr-certbot.pem
 create mode 100644 letsencrypt/csr/0152_csr-certbot.pem
 create mode 100644 letsencrypt/csr/0153_csr-certbot.pem
 create mode 100644 letsencrypt/csr/0154_csr-certbot.pem
 create mode 100644 letsencrypt/csr/0155_csr-certbot.pem
 create mode 100644 letsencrypt/csr/0156_csr-certbot.pem
 create mode 100644 letsencrypt/csr/0157_csr-certbot.pem
 create mode 100644 letsencrypt/csr/0158_csr-certbot.pem
 create mode 100644 letsencrypt/csr/0159_csr-certbot.pem
 create mode 100644 letsencrypt/csr/0160_csr-certbot.pem
 create mode 100644 letsencrypt/csr/0161_csr-certbot.pem
 create mode 100644 letsencrypt/csr/0162_csr-certbot.pem
 create mode 100644 letsencrypt/csr/0163_csr-certbot.pem
 create mode 100644 letsencrypt/csr/0164_csr-certbot.pem
 create mode 100644 letsencrypt/csr/0165_csr-certbot.pem
 create mode 100644 letsencrypt/csr/0166_csr-certbot.pem
 create mode 100644 letsencrypt/csr/0167_csr-certbot.pem
 create mode 100644 letsencrypt/csr/0168_csr-certbot.pem
 create mode 100644 letsencrypt/csr/0169_csr-certbot.pem
 create mode 100644 letsencrypt/csr/0170_csr-certbot.pem
 create mode 100644 letsencrypt/csr/0171_csr-certbot.pem
 create mode 100644 letsencrypt/csr/0172_csr-certbot.pem
 create mode 100644 letsencrypt/csr/0173_csr-certbot.pem
 create mode 100644 letsencrypt/csr/0174_csr-certbot.pem
 create mode 100644 letsencrypt/csr/0175_csr-certbot.pem
 create mode 100644 letsencrypt/csr/0176_csr-certbot.pem
Reading changelogs... Done
(Reading database ... 155359 files and directories currently installed.)
Preparing to unpack .../virtualmin-config_7.0.21_all.deb ...
Unpacking virtualmin-config (7.0.21) over (7.0.19) ...
Preparing to unpack .../virtualmin-lemp-stack_7.0.6-1_all.deb ...
Unpacking virtualmin-lemp-stack (7.0.6-1) over (7.0.4-1) ...
Setting up virtualmin-config (7.0.21) ...
Setting up virtualmin-lemp-stack (7.0.6-1) ...
Processing triggers for man-db (2.11.2-2) ...

It seems it didn’t installed those additional packages.

Check the News category or do a search, this issue has been covered.

Oh sorry, I see it now.

I think I’ve installed the fixed version.
I recognized that the system hostname changes from my IP to 127.0.0.1 and the server doesn’t accept password via SSH client.

I write back the IP to the original but it always switches back to 127.0.0.1 on boot.

I tried to change my root password in Webmin but it says my new password can’t be the same as my old password.

Even my hosting couldn’t help. They said it so messed up they can’t change password and also can’t login.

Are these problems related to this package or not?

Thank you for help!

EDIT:

I reversed my server back to yesterday via backup and updated all packages except virtualmin-config and virtualmin-lemp-stack.

The server now works well so defenetely the updates are still bad.
I keep the old version till it will be safe.
sudo apt-mark hold virtualmin-config virtualmin-lemp-stack

Neither of those packages have anything to do with the problem you’ve described. virtualmin-config only runs on fresh install (unless you manually run it from the command line), and virtualmin-lemp-stack just depends on things, it has no code.

Open a new topic about your problem with the IP, if it shows up again. But, I’m very confident it wasn’t related to either of those packages. But, it’s also harmless to hold them, since they’re mostly only useful during initial installation.

1 Like

Thank you for reply!

When I installed Virtualmin back then my system was Debian 11. I’ve upgraded it to 12 since then.
I’ve edited all of the sources files including PHP and MariaDB too.
I’ve recognized that Virtualmin sources has no difference like the system ones. (Bullseye or Bookworm tags) So I kept it in original state.

Do Virtualmin/Webmin package updates coming for my new system version and should work fine?
If yes, I have no idea why my system cause this weird problem because everything else is just works fine.

Other question:
When I try to update virtualmin-config virtualmin-lemp-stack from Webmin menu, they want to install other packages too.

|libopendbx1|
|librbl1|
|libunbound8|
|libvbr2|
|opendkim|
|libopendbx1-sqlite3|
|opendkim-tools|
|proftpd-mod-crypto|
|virtualmin-config|
|virtualmin-lemp-stack|

When I try to update them from SSH console, only these two want to get installed and other packages not.

What is the correct way to install these updates?

Can you please answer that do I need to install these packages or not?
Thank you!

|libopendbx1|
|librbl1|
|libunbound8|
|libvbr2|
|opendkim|
|libopendbx1-sqlite3|
|opendkim-tools|
|proftpd-mod-crypto|

I think your question was answered here:

that list of packages has nothing specifically to do with the LEMP stack and looks like a list of other packages that just need to be installed. (or even may have been)

Thank you for reply!

Those packages defenetely wants to get installed with one of those virtualmin updates because holding them back made them also hidden.

sudo apt-mark hold virtualmin-config virtualmin-lemp-stack

They dissapeared after that:

|libopendbx1|
|librbl1|
|libunbound8|
|libvbr2|
|opendkim|
|libopendbx1-sqlite3|
|opendkim-tools|
|proftpd-mod-crypto|

The root login / IP problem maybe not related to the updates, but my question about the additional packages yes.

Hence the request by @Joe to open a new topic (It gets annoying to forum users when topics digress/divert from the original topic) .

It is clear in the Forum Guidelines.
But I understand you are new to the forum and so are not yet used to these nuances.

Okay, sorry! I will open new topic for it.

I tought these problems are connected. Thats why I continued the discuss. My bad.

This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.