Web Solutions and Technical Support Resources





WordPress Memory Exhausted Error

This article will guide you on steps to resolve #WordPress #memory exhausted #error by simply increasing #PHP memory limit.
The memory exhausted errors only occur when your web host allocated lower amounts of memory for each website.
To increase the PHP memory limit, you need to manually set a new memory limit for your server. This involves editing the wp-config.php file located in the server.

Read More




DirectAdmin Skin or Interface Issues

This article will guide you on different methods to fix #DirectAdmin #skin or #interface issues.
To fix DirectAdmin Skin or Interface Issues:
What if the DirectAdmin skin is corrupted? How to fix DirectAdmin Skin or Interface Issues? Here are some steps you can try.
1. Reinstall skin.
cd /usr/local/directadmin/data/skins/
./packskins.sh
2. Recompile PHP using the following commands.
cd /usr/local/directadmin/custombuild
./build update
./build clean
./build php d
These steps will fix almost every issues with DirectAdmin skin.

Read More




New files of configuration for Apache error in Plesk

This article will guide you on methods to fix the Plesk error : new files of configuration for Apache.
The causes of this Plesk error:
1. Mailman package is not installed.
2. Database related error.
3. PHP memory issue.
To fix this Plesk issue:
Mailman package is not installed
When you try to reconfigure the domain, you will get the following error.
# /usr/local/psa/admin/sbin/httpdmng --reconfigure-all
No valid mailman bindir detected
So, in this case it is clear that the issue is causing because the mailman package is missing.
To fix the issue, you can follow the steps mentioned below.
a) Download and install the mailman package from  http://autoinstall.plesk.com
b) After that remove all entries from the ‘Configurations’ table of the ‘psa’ database.
mysql -uadmin -p`cat /etc/psa/.psa.shadow` psa -e"delete from Configurations"
c) Remove all ‘Include’ records from configuration files and all content from the directory below:
# sed -i /Include/d /usr/local/psa/admin/conf/ip_vhosts_bootstrap.conf&& sed -i /Include/d /usr/local/psa/admin/conf/vhosts_bootstrap.conf&& sed -i /include/d /usr/local/psa/admin/conf/nginx_vhosts_bootstrap.conf&& sed -i /Include/d /usr/local/psa/admin/conf/webmail_horde_bootstrap.conf&& sed -i /Include/d /usr/local/psa/admin/conf/webmail_atmail_bootstrap.conf&& sed -i /Include/d /etc/httpd/conf.d/zz010_psa_httpd.conf&& rm -f /usr/local/psa/admin/conf/generated/*
d) Now you can reconfigure and that will fix the issues.
/usr/local/psa/admin/bin/httpdmng --reconfigure-all
This will resolve the error.

Read More




An error has occurred in DNN Websites

This article will guide you on how to easily fix 'An #error has occurred' error message appears in #DNN #Pages which occurs when there is a null entry in the #database table. We also looked into the steps for adding the temporary URL.
When trying to add a file attachment to the #DotNetNuke forum module, we received an error that looked like this:
An Error Has Occurred When Attempting To Save The File C:\webroot\site\site.com\wwwroot\Portals\0\imge.jpg. Please Contact Your Hosting Provider To Ensure The Appropriate Security Settings Have Been Enabled On The Server.
If you have a superuser account (common username is HOST) you can login and go to the Host menu, and see if you have an EXTENSIONS page listed, from that page you can see what version of DNN you are on. you can also try the HOST/HOST SETTINGS page.

Read More




Webmail timeout issue in DirectAdmin


This article will guide you on how to resolve #timeout #error in #webmail in #DirectAdmin. Generally, webmail timeout issue can occur if the timeout value is exceeded.
The term timeout or time-out has several meanings, including: A network parameter related to an enforced event designed to occur at the conclusion of a predetermined elapsed time.
To fix Webmail timeout error in DirectAdmin:
Modify the config file "/var/www/html/webmail/inc/config.php" or in /var/www/html/webmail/inc/config.security.php
and set
Code:
# Session timeout for inactivity
#
$idle_timeout = 10; //minutes
to whatever value you need.

Read More




Database version or build from backup file

This article will guide you on how to determine the database #version or build from a #backup file.
To know what #SQL version a #database is:
The first is by using either Enterprise Manager or SQL Server Management Studio and right clicking on the instance name and selecting Properties. In the general section you will see information such as on the following screenshots. The "Product version" or "Version" gives you a number of the version that is installed.
In order to find the SQL Server version from a bak file:
1. Here is the output returned by the RESTORE HEADERONLY statement. Here you will see a DatabaseVersion column that contains the value.
2. That's how you find out from which version of SQL Server a given backup file came.

Read More