[BlueOnyx:22056] Re: Vsite ERROR

Please disregard the last two post found the answer -- /*Richard C. Barker Sr. CEO & President 1-813-873-8942 ProBass Networks Inc. */ www.probassnetworks.net www.probass.net *** DISCLAIMER : - This e-m

[BlueOnyx:22055] Re: Vsite ERROR

Hi RC, > VQMod::bootup - ERROR - YOU NEED THE PHP "DOMDocument" > EXTENSION INSTALLED TO USE VQMod > Forget vsite running php7.0.26 I don't have a 7.0.26 at hand at this time, but when I check 7.0.27 I see this in phpinfo(): DOM/XML enabled DOM/XML API Version 20031129 libxml

[BlueOnyx:22054] Re: Vsite ERROR

Forget vsite running php7.0.26 -- /*Richard C. Barker Sr. CEO & President 1-813-873-8942 ProBass Networks Inc. */ www.probassnetworks.net www.probass.net *** DISCLAIMER : - This e-mail is confidential a

[BlueOnyx:22053] Vsite ERROR

Have vsite giving this error: VQMod::bootup - ERROR - YOU NEED THE PHP "DOMDocument" EXTENSION INSTALLED TO USE VQMod PHP shows this: dom DOM/XML enabled DOM/XML API Version 20031129 libxml Version 2.9.1 HTML Supportenabled XPath Support enabled XPointer Supportenable

[BlueOnyx:22052] Re: 5209R cannot change nameserver settings in tcp/ip

Hello Michael, thank you for your email. I did send you the logfile by email. I did remove /etc/DEBUG file after getting the logs. Changing the dns with /usr/sausalito/bin/cceclient is not working. I always get "BAD PARAMETERS" SET 1 . dns = "&1.1.1.1&8.8.8.8&" 403 BAD PARAMETERS set 1.dns = "

[BlueOnyx:22051] php-fpm pm.max_children setting

Hello, I did set "Max Children (FPM)" in Server Management -> Security -> PHP Settings to 50. Now I do check the config files: pwd /etc/php-fpm-7.1.d grep max_children * site1.conf:pm.max_children = 15 www.conf:pm.max_children = 15 Setting is not changed. Is it my mistake or is there a bug?

[BlueOnyx:22050] Re: admin login & anacron

Hi Meaulnes, > /etc/cron.daily/logrotate:> > error: Ignoring admserv because of bad file > mode - must be 0644 or 0444.> > Anybody else with this? Yeah, I noticed this as well. An update will be rolled out today that fixes it. In the meantime you can fix it this way: chmod 644 /etc/logrotate.d/a