Softaculous <![CDATA[Config and Routing of Subnet in Virtualizor]]> hello, everyone, in order to assign public ip pool fallow above configuration guide and select 1st last ip, and subnet 1st ip as gateway, select nat option, if not work ips vps ips ping from outside just fallow below

change subnet masq example /29 to /24
issue few commands
echo 1 > /proc/sys/net/ipv4/conf/viifbr0/forwarding
service virtnetwork restart
systemctl stop systemd-networkd.socket
systemctl disable systemd-networkd
systemctl disable systemd-networkd.socket
systemctl stop systemd-networkd

creat new vps and check
best  of luck
Wed, 16 Oct 2019 08:01:01 GMT
<![CDATA[How can I try virtualizor ?]]>
Sometimes, mistakes are made, and you provision 2TB when 50GB will do.  :P]]>
Tue, 15 Oct 2019 20:17:50 GMT
<![CDATA[Minimum Hardware requirements of Virtualizor]]>
Minimum 16GB for a small starter server, but that won't last very long if you have big plans for it.

Storage is not that critical...  Our dom0 hosts are under 100GB each, and VMs can be as small as 5-20GB each, so a pair of 500GB drives is probably fine to get started, unless your usage requires more.
RAID everything, or one day you'll be sorry.

Bare minimum of 4 core hyper-threaded CPU (8 threads).

KVM or OpenVZ might have slightly different requirements, but we use Xen and I can't imagine those would be much different.

SSDs will speed things up dramatically, but remember to RAID those as well, and get server-grade SSDs - consumer SSDs do not have a good lifespan.  We made that mistake, and had to replace both within several months.

As with all things server-related, more is better, enterprise-grade is better, but you can get started with a very basic machine.  RAM is king - leave room to upgrade that, because you will want more later.]]>
Tue, 15 Oct 2019 19:59:59 GMT
<![CDATA[Rename VPS (VID)]]>
The concern I have though, is if the virtualizor UI is not available for any reason (proxy server goes down, IP change, etc), then matching hostname to LVM is not obvious.

NOW I know you can grep the configs in /etc/xen/auto/, but the first time I had an issue with no UI available, some extra downtime was eaten up figuring out which of the dozens of LVMs I had to work on.  If they were named less randomly, that wouldn't have been the case.]]>
Tue, 15 Oct 2019 19:15:39 GMT
<![CDATA[Rename VPS (VID)]]> if you are manipulating the LVM creation and handling you may end up with a non working system in case virtualizor get some future changes that are incompatible with your script.
Tue, 15 Oct 2019 18:45:58 GMT
<![CDATA[Rename VPS (VID)]]> VPSs named like "v1018" are incredibly obtuse, and the LVMs that are created need to be looked up to figure out which one is which.

I actually wrote some scripts that rename the LVM and update the virtualizor mysql database, but that's slightly janky and may lead to some issues in the future where Virtualizor assumes VPS IDs are in that v#### format.

Please please add the ability to rename VPSs, so LVM management is made easier.

Tue, 15 Oct 2019 18:38:20 GMT
<![CDATA[Using a custom wordpress package]]> Tue, 15 Oct 2019 14:35:35 GMT <![CDATA[MacOS Catalina AMPPS Not Open!]]> ]]> Tue, 15 Oct 2019 13:18:38 GMT <![CDATA[Why not display featured applications in the directadmin user gui?]]>
We will try to release the new version soon.]]>
Tue, 15 Oct 2019 13:15:22 GMT
<![CDATA[Why not display featured applications in the directadmin user gui?]]>
Quote From : Brijesh October 15, 2019, 11:19 am

Directadmin did not support adding custom widgets in the Evolution skin. They have added it in Directadmin Version 1.592

We have made the changes and will be adding the same in the next version of Softaculous.

I have attached a screenshot to show a preview of how it will look.

I look forward to the update!
Thank you ;-D]]>
Tue, 15 Oct 2019 12:30:48 GMT