<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Cpanel Archives - Chris Gilligan » new media</title>
	<atom:link href="https://chrisgilligan.com/cpanel/feed/" rel="self" type="application/rss+xml" />
	<link>https://chrisgilligan.com/cpanel/</link>
	<description>portfolio of web work</description>
	<lastBuildDate>Fri, 27 Sep 2013 20:12:28 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1</generator>
	<item>
		<title>WordPress Fail2Ban RegEx for RedHat, CentOS, Amazon Linux</title>
		<link>https://chrisgilligan.com/consulting/wordpress-wp-fail2ban-regex-redhat-centos-amazon-linux/</link>
					<comments>https://chrisgilligan.com/consulting/wordpress-wp-fail2ban-regex-redhat-centos-amazon-linux/#respond</comments>
		
		<dc:creator><![CDATA[Chris Gilligan]]></dc:creator>
		<pubDate>Thu, 30 May 2013 00:30:24 +0000</pubDate>
				<category><![CDATA[Amazon Web Services]]></category>
		<category><![CDATA[Consulting]]></category>
		<category><![CDATA[Content Management Systems]]></category>
		<category><![CDATA[Cpanel]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[Virtualmin]]></category>
		<category><![CDATA[Wordpress]]></category>
		<guid isPermaLink="false">https://chrisgilligan.com/?p=1875</guid>

					<description><![CDATA[<p>VacantServer WordPress sites are getting hammered with bad logins and probes. We&#8217;ve implemented a plugin to log failed login attempts to syslog, and a Fail2Ban filter for the same. If you run these on RedHat, you&#8217;ll need some additional configuration info&#8230; here it is: WordPress login failure regex (error_log): ^%(__prefix_line)sAuthentication failure for .* from &#60;HOST&#62;$ [&#8230;]</p>
<p>The post <a href="https://chrisgilligan.com/consulting/wordpress-wp-fail2ban-regex-redhat-centos-amazon-linux/">WordPress Fail2Ban RegEx for RedHat, CentOS, Amazon Linux</a> appeared first on <a href="https://chrisgilligan.com">Chris Gilligan » new media</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><strong><a href="http://vacantserver.net/">VacantServer</a> WordPress sites are getting hammered with bad logins and probes.</strong></p>
<p>We&#8217;ve implemented a <a href="http://wordpress.org/extend/plugins/wp-fail2ban/">plugin to log failed login attempts to syslog</a>, and a Fail2Ban filter for the same. If you run these on RedHat, you&#8217;ll need some additional configuration info&#8230; here it is:</p>
<div>
<div><strong>WordPress login failure regex (error_log):</strong></div>
<div>
<pre class="lang:default decode:true ">^%(__prefix_line)sAuthentication failure for .* from &lt;HOST&gt;$</pre>
<p><strong>Apache nohome regex (error_log):</strong></p>
</div>
<div>
<pre class="lang:default decode:true ">[[]client &lt;HOST&gt;[]] File does not exist: .*/~.*</pre>
<p><strong>PHP noscript regex (/home/*/logs/error_log,/var/log/httpd/error_log):</strong></p>
</div>
<div>
<pre class="lang:default decode:true">[[]client &lt;HOST&gt;[]] (File does not exist|script not found or unable to stat): /\S*(\.php|\.asp|\.exe|\.pl)
[[]client &lt;HOST&gt;[]] script '/\S*(\.php|\.asp|\.exe|\.pl)\S*' not found or unable to stat *$</pre>
<p><strong>XMLRPC flood attacks &#8212; DDoS and probing (/home/*/logs/access_log):</strong></p>
<pre class="lang:default decode:true crayon-selected">&lt;HOST&gt;\s.*\s.POST\s/xmlrpc.php*.\s.*</pre>
<p>Please also enable the generic apache-nohome, apache-noscript. Install wp fail2ban plugin (and configure it for your server) on your high traffic blogs. These all are helping during the current onslaught, which also includes probing for wp-admin directories, probing for /wp-admin/login.php, plus comment spam.</p>
<p>A new XMLRPC exploit has the script kiddies doing DDoS and probing for vulnerable services, and possibly doing remote code execution on vulnerable services.</p>
<h4>Here are some additional resources:</h4>
<ul>
<li>RegEx testing tool: <a href="http://gskinner.com/RegExr/">RegExr (AIR and web versions)</a></li>
<li>use <a href="http://www.fail2ban.org/wiki/index.php/MANUAL_0_8#Testing">Fail2Ban&#8217;s built-in regex testing</a></li>
<li>additionally, try <a href="http://23x.net/908/securing-wordpress-using-fail2ban.html">23x&#8217;s Apache WordPress Fail2Ban advice</a></li>
<li>block spammer IP&#8217;s via <a href="http://blog.shadypixel.com/spam-log-plugin/">Akismet: Spam-Log Plugin</a></li>
</ul>
</div>
</div>
<p>The post <a href="https://chrisgilligan.com/consulting/wordpress-wp-fail2ban-regex-redhat-centos-amazon-linux/">WordPress Fail2Ban RegEx for RedHat, CentOS, Amazon Linux</a> appeared first on <a href="https://chrisgilligan.com">Chris Gilligan » new media</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://chrisgilligan.com/consulting/wordpress-wp-fail2ban-regex-redhat-centos-amazon-linux/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Cpanel Mailman mailing lists: cannot manage lists after migrating to new host</title>
		<link>https://chrisgilligan.com/wordpress/cpanel-mailman-mailing-lists-cannot-manage-lists-after-migrating-to-new-host/</link>
					<comments>https://chrisgilligan.com/wordpress/cpanel-mailman-mailing-lists-cannot-manage-lists-after-migrating-to-new-host/#comments</comments>
		
		<dc:creator><![CDATA[Chris Gilligan]]></dc:creator>
		<pubDate>Tue, 19 Jul 2011 19:27:32 +0000</pubDate>
				<category><![CDATA[Cpanel]]></category>
		<category><![CDATA[Mailman]]></category>
		<category><![CDATA[Wordpress]]></category>
		<category><![CDATA[check_perms]]></category>
		<category><![CDATA[cpanel]]></category>
		<category><![CDATA[directory permissions]]></category>
		<category><![CDATA[hosting]]></category>
		<category><![CDATA[mailing lists]]></category>
		<category><![CDATA[mailman]]></category>
		<category><![CDATA[mailman permissions]]></category>
		<category><![CDATA[migrate]]></category>
		<category><![CDATA[migration]]></category>
		<category><![CDATA[vps]]></category>
		<category><![CDATA[whm]]></category>
		<guid isPermaLink="false">https://chrisgilligan.com/?p=466</guid>

					<description><![CDATA[<p>We recently migrated 2 Cpanel servers to VPS. Most things migrated properly and without incident. However, Mailman mailing lists were the exception. Mailing lists appear to have migrated properly, as they show up under WHM and Cpanel and usr/local/ &#8230; /list_lists However, when cpanel user clicks Manage link, the following message appears: cpanel1.hosting.com mailing lists [&#8230;]</p>
<p>The post <a href="https://chrisgilligan.com/wordpress/cpanel-mailman-mailing-lists-cannot-manage-lists-after-migrating-to-new-host/">Cpanel Mailman mailing lists: cannot manage lists after migrating to new host</a> appeared first on <a href="https://chrisgilligan.com">Chris Gilligan » new media</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p style="float: right; margin: 0 0 10px 15px; width:240px; height: auto;">
		<img src="https://d2lehxir4n36oh.cloudfront.net/wp-content/uploads/2011/07/logo-mailman.jpg?x15172" width="240" style="max-width: 100%; height: auto;" />
		</p><p><strong>We recently migrated 2 Cpanel servers to VPS.</strong> Most things migrated properly and without incident. However, Mailman mailing lists were the exception.</p>
<p>Mailing lists appear to have migrated properly, as they show up under WHM and Cpanel and usr/local/cpanel/3rdparty/mailman/bin/list_lists</p>
<p>However, when cpanel user clicks Manage link, the following message appears:</p>
<blockquote><p>cpanel1.hosting.com mailing lists &#8211; Admin Links<br />
No such list listname_domainname.com<br />
There currently are no publicly-advertised Mailman mailing lists on cpanel1.hosting.com.To visit the administrators configuration page for an unadvertised list, open a URL similar to this one, but with a &#8216;/&#8217; and the right list name appended. If you have the proper authority, you can also create a new mailing list.</p></blockquote>
<p><strong>This turned out to be a permissions issue:</strong></p>
<p><code>root@cpanel1 [/usr/local/cpanel/3rdparty/mailman/bin]# ./check_perms</code></p>
<p><code>--snip--<br />
directory permissions must be 02775: /usr/local/cpanel/3rdparty/mailman/.../list_domain.com/...<br />
--snip--<br />
Problems found: 2999</code></p>
<p><code># ./check_perms -f</code></p>
<p><strong>FIXED!!!</strong></p>
<p>The post <a href="https://chrisgilligan.com/wordpress/cpanel-mailman-mailing-lists-cannot-manage-lists-after-migrating-to-new-host/">Cpanel Mailman mailing lists: cannot manage lists after migrating to new host</a> appeared first on <a href="https://chrisgilligan.com">Chris Gilligan » new media</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://chrisgilligan.com/wordpress/cpanel-mailman-mailing-lists-cannot-manage-lists-after-migrating-to-new-host/feed/</wfw:commentRss>
			<slash:comments>2</slash:comments>
		
		
			</item>
	</channel>
</rss>

<!--
Page Caching using Disk: Enhanced 
Content Delivery Network via Amazon Web Services: CloudFront: d2lehxir4n36oh.cloudfront.net
Lazy Loading (feed)

Served from: chrisgilligan.com @ 2026-09-06 13:09:50 by W3 Total Cache
-->