Error: Unable to update the password. The value provided for the new password does not meet the length, complexity, or history requirements of the domain
If you are meeting the complexity and length requirements. You are most likely not meeting the history requirements. Which means the password was recently changed and you will have to wait depending on the length set in the password policy.
Check the local security policy settings on the system under the control panel – Administrative – local security policy.
If you are seeing “deny not allowed here” within your error logs .Try adding the following to your httpd conf file for the virtual site.
 [error] [client ::1] client denied by server configuration: /var/www/example.com/
Options Indexes FollowSymLinks MultiViews +Includes
allow from all
of course replace the trouble folder with the actual folder name . If you do not have access to the httpd conf file , you may need to ask your System Admin to do this for you.
*We need clarification on if this setting inherits to the sub folders.*
send me a message on twitter if you can assist with clarifying the above for me .
How to free up some space under /var/cache/ on Fedora
run the command
sudo pkcon refresh force -c -1
Reference : https://bugs.freedesktop.org/show_bug.cgi?id=80053
You can disable priorities in
/etc/yum/pluginconf.d/priorities.conf set enabled to 0
A Cautionary Note
Note: The upstream maintainer of yum, Seth Vidal, had the following to say about ‘yum priorities’ in September 2009:
Gosh, I hope people do not set up yum priorities. There are so many things about
priorities that make me cringe all over. It could just be that it reminds me of
apt ‘pinning’ and that makes me want to hurl.
This matter was discussed in more depth in the mailing list thread starting here. The Repositories article noted in that thread, which discusses the exclude and includepkg options for yum, is a better place to start in understanding priorities.
The primary concern is that priorities is heavy handed over removing packages from the transaction set. It makes it difficult to readily determine what packages are being ignored and why. Even so, it is very flexible and can be extremely useful to provide the largest available list of packages.
If you enable both of the SymLinksIfOwnerMatch and FollowSymLinks configuration settings, Apache becomes vulnerable to a race condition through symlinks. This symlink vulnerability allows a malicious user to serve files from anywhere on a server that strict OS-level permissions do not protect. The cPanel Hardened Kernel update provides Symlink Race Condition Protection.
This document explains how to implement symlink race condition protection on systems that run EasyApache 4.