[SOLVED] Virtualmin installation problem

virtualmin2018 · 06-18-2019, 02:12 AM

I can't seem to install virtual min and keep getting this error

Code:

[12/23] Configuring Quotas The filesystem / could not be remounted with quotas enabled. You may need to reboot your system, and/or enable quotas in the Disk Quotas module. [ ⚠ ] [13/23] Configuring SASL [ ✔ ] [14/23] Configuring Shells [ ✔ ] [15/23] Configuring SpamAssassin [ ✔ ] [16/23] Configuring Status [ ✔ ] [17/23] Configuring Upgrade [ ✔ ] [18/23] Configuring Usermin [ ✔ ] [19/23] Configuring Webalizer [ ✔ ] [20/23] Configuring Webmin [ ✔ ] [21/23] Configuring Fail2banFirewalld [ ✔ ] [22/23] Configuring Postfix [ ✔ ] [23/23] Configuring Virtualmin [ ✔ ] ▣▣▣ Cleaning up

Device "link" does not exist. [WARNING] Unable to determine IP address of primary interface. Please enter the name of your primary network interface:

Any ideas how to solve this problem?

Im running a OPENVZ centos7 VPS and using gitbash as my command prompt.

scasey · 06-18-2019, 03:11 AM

Quote:

Originally Posted by virtualmin2018

I can't seem to install virtual min and keep getting this error

Code:

[12/23] Configuring Quotas The filesystem / could not be remounted with quotas enabled. You may need to reboot your system, and/or enable quotas in the Disk Quotas module. [ ⚠ ] [13/23] Configuring SASL [ ✔ ] [14/23] Configuring Shells [ ✔ ] [15/23] Configuring SpamAssassin [ ✔ ] [16/23] Configuring Status [ ✔ ] [17/23] Configuring Upgrade [ ✔ ] [18/23] Configuring Usermin [ ✔ ] [19/23] Configuring Webalizer [ ✔ ] [20/23] Configuring Webmin [ ✔ ] [21/23] Configuring Fail2banFirewalld [ ✔ ] [22/23] Configuring Postfix [ ✔ ] [23/23] Configuring Virtualmin [ ✔ ] ▣▣▣ Cleaning up

Device "link" does not exist. [WARNING] Unable to determine IP address of primary interface. Please enter the name of your primary network interface:

Any ideas how to solve this problem?

Im running a OPENVZ centos7 VPS and using gitbash as my command prompt.

Did you "enter the name of your primary network interface:" at that prompt?

virtualmin2018 · 06-18-2019, 05:19 AM

Quote:

Originally Posted by scasey

Did you "enter the name of your primary network interface:" at that prompt?

Exactly I don't know what to input here? I searched around but many users say it's a problem with updates and others ask to input other commands before running the installer which I tried and didn't work. The installation should be smooth without this query.

virtualmin2018 · 06-18-2019, 07:16 PM

Quote:

Originally Posted by scasey

Did you "enter the name of your primary network interface:" at that prompt?

So I tried inputting venet0 and give this message

Quote:

Device "link" does not exist.
[WARNING] Unable to determine IP address of primary interface.
Please enter the name of your primary network interface:
venet0
./slib.sh: line 450: log_debugPrimary address detected as 127.0.0.1: command not found
[SUCCESS] Installation Complete!
[SUCCESS] If there were no errors above, Virtualmin should be ready
[SUCCESS] to configure at https://*** (or https:*****:10000).
[SUCCESS] You'll receive a security warning in your browser on your first visit.
[root@**** ~]# Connection to ***** closed by remote host.
Connection to **** closed.

but when I type the ip with :10000 port it just show ERR_CONNECTION_TIMED_OUT

virtualmin2018 · 06-20-2019, 03:13 AM

Ok this is how I fix it hope it helps

I first type ip ro ls and it will come out something like:

default via xx.x.x.x.x. dev eth0 onlink

for mine it was venet0 instead of eth0 so I used venet0 as the primary IP address of interface and typed it in.

Next, gitbash(the terminal I use) says installation successful however, I cannot get inside https://xx.xx.xx.xx:10000 because I get ERR_CONNECTION_TIMED_OUT and I start to panic again.

So this is because firewall is blocking the port and IP I think so what you do next is input the following:

firewall-cmd --zone=public --add-port=10000/tcp --permanent

then reload with

firewall-cmd --reload

And now you can access virtualmin control panel. All the best!

scasey · 06-20-2019, 09:24 AM

Thank you for posting the solution.

Yes, the *min software uses high port numbers that are usually blocked by firewalls.

You can mark the thread [SOLVED] using the thread tools at the top of the page.

And welcome to LQ.