Vpro Customer: Install script fails to install on new clean Ubuntu 22.04.3 server

[xlad]

Vpro Customer: Install script fails to install on new clean Ubuntu 22.04.3 server

Try to disable IPv6

[xlad]

And you’re welcomed, ungrateful as you are.

[ID10T]

I’m not a mod, but this is getting out of hand.

[sparticle1]

Wow, you showed me nothing. We already had IPV6 disabled. Nothing is assigned automatically, something is configured to assign for that to happen. On our network that is not the case. And for the last time IPV6 is disabled!

People like you are symptomatic of what’s wrong with the world. Entitled, opinionated idiots, with no respect for facts, logic or intelligent discussion. If something doesn’t fit your narrow level of understanding, shout some more and put out ever more nonsense. Attack anyone who wants to discuss something and has the knowledge and capability to enter into that discussion.

And congratulations for dragging me down to your level and for hijacking this thread with your nonsense.

Ridiculous!

@Ilia please feel free to close this thread as I have already posted the issue, fix and workaround.

Cheers
Spart

[Ilia]

The point is Dovecot doesn’t know it has anything.

I agree, this is either dovecot-imapd or dovecot-core package bug. Please report it upstream!

I have also said as much to the Dovecot team!

Great!

@sparticle1

@Ilia I am not sure I agree with your assertion that there is nothing the script can do. I also not suggesting it is your problem. Just sharing my experience and admittedly a little frustration as a paying customer. But, it is entirely feasible to catch this in an installer script. Modify the config file and re-start Dovecot and carry on with the install. I am not saying you need to fix it. But, it is entirely possible to script around the issue. Catching the failed start of Dovecot, modify the config file and loop around and continue.

This issue is happening in apt-get install, and is what is catching the signal. We cannot work-around it. Package manager breaks installing it and exists with non-zero code, before any configs can be edited.

And again before I once again get attacked by the keyboard warriors.

Sadly, some folks lack patience and courtesy.

@xlad

Your server thinks that has a legit IPv6, and preffers it over the old IP (version 4), but HAS NO ACCes to the network that YOU blocked it.

The server itself doesn’t have IPv6 enabled, this is why the installer fails, as it cannot bind to :: address. If it could, it wouldn’t fail.

@sparticle1

I am not making it Virtualmins fault just looking for a practical solution.

How about enabling IPv6 locally, for the instance (server), before installing anything? If it has IPv6 locally enabled, I don’t think it would be a big problem … right? Perhaps, not that clean as you wanted it, I understand it. But if there are other services that break it may be tedious to address it in timely manner.

Although, for your case, the other work around, and probably most straight forward and clean one would be install (on clean and minimal Ubuntu 22.04) dovecot-core package at first. Then fix Dovecot config to listen on the right interface, i.e. *, then install dovecot-imapd and dovecot-pop3d, and then install Virtualmin using virtualmin-install.sh script. If the Dovecot package is the only package that fails to work without IPv6 enabled, then you’ll be good to go. Also, this solution is easy to automate.

@ID10T

I’m not a mod, but this is getting out of hand.

They speak about different problems, in different languages.

@sparticle1

And congratulations for dragging me down to your level and for hijacking this thread with your nonsense.

It is paramount for everyone to remain anchored to the core essence of the topic. Should anyone deviate, exercise discernment and filter out the distractions.