<?xml version="1.0" encoding="utf-8"?>
			<?xml-stylesheet type="text/css" href="https://www.carehart.org/blog/client/rss.css" ?>
			
			<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
			<channel>
			<title>Charlie Arehart - Server Troubleshooting - apache</title>
			<link>https://www.carehart.org/blog/client/index.cfm</link>
			<atom:link href="https://www.carehart.org/blog/client/rss.cfm" rel="self" type="application/rss+xml" />
			<description>Charlie Arehart - Server Troubleshooting</description>
			<language>en-us</language>
			<lastBuildDate>Tue, 25 Feb 2025 19:55:00 -0500</lastBuildDate>
			<generator>BlogCFC</generator>
			<docs>http://blogs.law.harvard.edu/tech/rss</docs>
			<managingEditor>blogmaster@carehart.org (Charlie Arehart)</managingEditor>
			<webMaster>blogmaster@carehart.org (Charlie Arehart)</webMaster>
			
			<item>
				<title>ColdFusion 2025 released, Feb 25 2025 - resources and my initial thoughts</title>
				<link>https://www.carehart.org/blog/2025/2/25/coldfusion_2025_released</link>
				<description>
				
				ColdFusion 2025 has been released today, Feb 25 2025. In this post I am not only helping share news of the release, and pointing to available resources, but I also share some thoughts/observations on related matters that may be a bit challenging for most to find more about on their own (if they may only assess a couple of resources, or hear only tidbits shared in social media). 

First, for more on the many features and changes, I share many Adobe resources--about which I also offer some additional comment. I also discuss changes regarding OS and DB support as well as the fact that &lt;b&gt;CF2025 now runs on Java 21&lt;/b&gt;-- and that the traditional server deployment of CF comes installed atop &lt;b&gt;Tomcat 10.1&lt;/b&gt;. I then share still more info on other matters and resources related to the new version.

I then focus on &lt;b&gt;the major change in licensing, for CF2025 and forward, to being subscription only&lt;/b&gt;--which I&apos;ll note has no effect on those currently running CF2023 or earlier. I share pricing info and also help in assessing differences in the EULA, and more.

Finally I discuss some &lt;b&gt;migration considerations&lt;/b&gt;--including important &lt;b&gt;REMOVAL of some older features from CF2025&lt;/b&gt;, as CF continues to be made more secure and modernized. I also identify tools and resources to help aid you in that migration, when you&apos;re ready to begin attempting it. 

For all that and more, read on.  [More]
				</description>
				
				<category>tomcat</category>
				
				<category>IIS</category>
				
				<category>admin</category>
				
				<category>licensing</category>
				
				<category>installation</category>
				
				<category>security</category>
				
				<category>news</category>
				
				<category>docker</category>
				
				<category>cf2025</category>
				
				<category>cf2023</category>
				
				<category>apache</category>
				
				<pubDate>Tue, 25 Feb 2025 19:55:00 -0500</pubDate>
				<guid>https://www.carehart.org/blog/2025/2/25/coldfusion_2025_released</guid>
				
			</item>
			
			<item>
				<title>Announcing ColdFusion emergency update released March 14 2023 - what to do about it</title>
				<link>https://www.carehart.org/blog/2023/3/17/coldfusion_march_2023_emergency_update</link>
				<description>
				
				If you&apos;ve not heard, a new update has been released (March 14, 2023) for ColdFusion 2021 and 2018. Despite what you may hear, &lt;b&gt;this is an URGENT (rated &quot;Priority 1&quot; by Adobe) update that everyone should apply ASAP&lt;/b&gt;, for reasons I will explain in this post. In fact, &lt;a href=&quot;https://thehackernews.com/2023/03/cisa-issues-urgent-warning-adobe.html&quot;&gt;Hackernews reported yesterday&lt;/a&gt; (Mar 16) that the U.S. Cybersecurity and Infrastructure Security Agency (CISA) had issued an urgent warning about this, giving federal agencies a deadline to apply the update. 

&lt;b&gt;TLDR;&lt;/b&gt; For some folks, &lt;b&gt;the above may be all you need to hear&lt;/b&gt;: you may be dropping your coffee and donuts now to get the update applied.  &lt;b&gt;Still others will see this &quot;huge post&quot; and think, &quot;crap, I don&apos;t have time for this&quot;.&lt;/b&gt; For you, skip to the bottom and its &quot;&lt;a href=&quot;#concludingkeypoints&quot;&gt;concluding key points&lt;/a&gt;&quot;. You can then decide what you think you do or don&apos;t &quot;need to know&quot; and pick and choose from the sections as you like. 

Finally, &lt;b&gt;for those who prefer because of the importance of all this to be led more carefully through understanding things&lt;/b&gt; (in a way that&apos;s worked for the many people I have helped so far this week, and is far more than either Adobe or Hackernews has shared), please do read on.  [More]
				</description>
				
				<category>updates</category>
				
				<category>cf2016</category>
				
				<category>IIS</category>
				
				<category>cf2021</category>
				
				<category>commandbox</category>
				
				<category>cf11</category>
				
				<category>security</category>
				
				<category>apache</category>
				
				<category>cf2018</category>
				
				<pubDate>Fri, 17 Mar 2023 03:00:00 -0500</pubDate>
				<guid>https://www.carehart.org/blog/2023/3/17/coldfusion_march_2023_emergency_update</guid>
				
			</item>
			
			<item>
				<title>The 100 most interesting posts on the Adobe ColdFusion blog, the past 3 years</title>
				<link>https://www.carehart.org/blog/2017/2/9/100_most_interesting_Adobe_ColdFusion_Team_blog_posts</link>
				<description>
				
				The &lt;a href=&quot;https://coldfusion.adobe.com&quot;&gt;Adobe ColdFusion team blog&lt;/a&gt; often has really some interesting content, but I find that some people are either not aware of the blog or just don&apos;t keep up on it, or perhaps they have trouble finding something they saw before or maybe heard was there. 

So here I present what I feel are the 100 (technically, 105) most interesting/useful posts made there over the past 3 years (2014-16), offering information about CF and CFML which should be valuable to readers for years to come.  [More]
				</description>
				
				<category>cf2016</category>
				
				<category>IIS</category>
				
				<category>cf10</category>
				
				<category>cf11</category>
				
				<category>blogging</category>
				
				<category>troubleshooting</category>
				
				<category>apache</category>
				
				<pubDate>Thu, 09 Feb 2017 13:32:00 -0500</pubDate>
				<guid>https://www.carehart.org/blog/2017/2/9/100_most_interesting_Adobe_ColdFusion_Team_blog_posts</guid>
				
			</item>
			
			<item>
				<title>The ColdFusion &apos;metrics log&apos;, an oft-missed or misunderstood feature, &apos;new&apos; since CF10 (Part 1)</title>
				<link>https://www.carehart.org/blog/2016/3/2/cf_metrics_log_part1</link>
				<description>
				
				I&apos;d like to take a diversion from my recent posts focused on CF2016 and talk about something that applies (and should interest) anyone using CF 10, 11, or 2016.

Have you heard of the new &quot;metrics log&quot; option that was enabled in CF10? If you have not, it&apos;s worth knowing about (there&apos;s precious little documentation, and I&apos;ll point to it, and give you still more info to help you use it). It&apos;s a useful, low-impact mechanism to get some high-level metrics logged by CF every 60 seconds (by default), and stored along with other CF logs.

If you did know about it, you&apos;ve probably had some problems with it. Why does it show &quot;nulls&quot;? What do reported metrics really mean? Why do they not jive with what I&apos;d expect to be the numbers reported?

In this post, and a Part 2 to come, I will introduce the metrics log, pointing out some key things you need to know to have it setup to work at all, and then I&apos;ll share my observations of things I&apos;ve come to understand about the reported metrics.  [More]
				</description>
				
				<category>performance</category>
				
				<category>cf2016</category>
				
				<category>IIS</category>
				
				<category>logs</category>
				
				<category>cf10</category>
				
				<category>cf11</category>
				
				<category>monitoring</category>
				
				<category>webserver</category>
				
				<category>troubleshooting</category>
				
				<category>apache</category>
				
				<pubDate>Wed, 02 Mar 2016 02:13:00 -0500</pubDate>
				<guid>https://www.carehart.org/blog/2016/3/2/cf_metrics_log_part1</guid>
				
			</item>
			
			<item>
				<title>ColdFusion 2016 - Changes in the CF Administrator</title>
				<link>https://www.carehart.org/blog/2016/2/23/cf2016_CF_Admin_changes</link>
				<description>
				
				As folks continue to explore ColdFusion (2016 Release), aka CF2016, regarding what&apos;s new or changed, I thought I&apos;d put together a listing of what has changed in the CF Admin specifically. This is another in a &lt;a href=&quot;http://www.carehart.org/blog/client/index.cfm/cf2016-intro&quot;&gt;series of posts I started last week on CF2016&lt;/a&gt;.  [More]
				</description>
				
				<category>CF2016 Intro Series</category>
				
				<category>cf2016</category>
				
				<category>IIS</category>
				
				<category>admin</category>
				
				<category>troubleshooting</category>
				
				<category>apache</category>
				
				<pubDate>Tue, 23 Feb 2016 22:32:00 -0500</pubDate>
				<guid>https://www.carehart.org/blog/2016/2/23/cf2016_CF_Admin_changes</guid>
				
			</item>
			
			<item>
				<title>Released today - CF2016, or &apos;ColdFusion (2016 release)&apos;. What&apos;s new, and more</title>
				<link>https://www.carehart.org/blog/2016/2/16/CF2016_announced_today_whats_new_and_more</link>
				<description>
				
				If you&apos;re not following the Adobe &lt;a href=&quot;http://coldfusion.adobe.com&quot;&gt;CF team blog&lt;/a&gt;, you may have missed the &lt;a href=&quot;https://coldfusion.adobe.com/2016/02/announcing-the-launch-of-the-newest-version-of-coldfusion-adobe-coldfusion-2016-release/&quot;&gt;announcement there today of the newest version of CF, ColdFusion 2016&lt;/a&gt;. More on the name in a moment.

And while that Adobe blog post mentions a few of the main new features, as is nearly always the case it leaves out many other new features which may interest folks.  It also doesn&apos;t point to resources to learn more. I do those things here in this post.  [More]
				</description>
				
				<category>CF2016 Intro Series</category>
				
				<category>cf2016</category>
				
				<category>IIS</category>
				
				<category>news</category>
				
				<category>apache</category>
				
				<pubDate>Tue, 16 Feb 2016 10:04:00 -0500</pubDate>
				<guid>https://www.carehart.org/blog/2016/2/16/CF2016_announced_today_whats_new_and_more</guid>
				
			</item>
			
			<item>
				<title>Monitoring ColdFusion web server connectors, more on Tomcat &apos;Status Workers&apos;</title>
				<link>https://www.carehart.org/blog/2015/8/3/more_on_tomcat_status_worker</link>
				<description>
				
				If you&apos;ve configured your web server (IIS or Apache) to be connected to CF--which can be done using the CF &quot;web server configuration&quot; or wsconfig tool--did you know that there is an optional monitor to observe the status of that web server connector? That connector is technically the Tomcat &quot;AJP connector&quot;, which Adobe implements for us. And this monitor, called the Tomcat &quot;Status worker&quot;, is an optional feature which we can configure (the CF wsconfig tool doesn&apos;t do it for us). 

In this post, I discuss the tool, elaborating on a post that Adobe offered about it last month (July 2015: for future readers, note that the feature remains essentially unchanged and just as potentially valuable in 2025, when I have tweaked this post just a bit, adding a table of contents and changing the order of some topics). 

You may well want to consider enabling the &quot;Status Worker&quot; feature, which the Adobe post shows is easily done. Still, in this post &lt;b&gt;I elaborate on some observations and caveats&lt;/b&gt; not covered in that brief post, which you will want to consider before enabling or trying to understand the output of the tool.  [More]
				</description>
				
				<category>tomcat</category>
				
				<category>carehart classics</category>
				
				<category>IIS</category>
				
				<category>monitoring</category>
				
				<category>webserver</category>
				
				<category>troubleshooting</category>
				
				<category>apache</category>
				
				<category>connector</category>
				
				<pubDate>Mon, 03 Aug 2015 01:10:00 -0500</pubDate>
				<guid>https://www.carehart.org/blog/2015/8/3/more_on_tomcat_status_worker</guid>
				
			</item>
			
			<item>
				<title>CF911- Help, How do I connect sites to a new instance w/ the ColdFusion 10/11 webserver config tool?</title>
				<link>https://www.carehart.org/blog/2015/2/26/cf911_connect_sites_to_an_instance_with_wsconfig</link>
				<description>
				
				This one causes a lot of heartburn for folks: you add a new instance in CF10 or 11 (in editions other than Standard, which do support adding instances), and you find that you can&apos;t seem to have the web server configuration tool (wsconfig) connect sites to that new instance(s). &lt;b&gt;You never see the new instance listed in the UI of the wsconfig tool.&lt;/b&gt; What gives?

The solution is relatively easy, and the problem could maybe be fixed (or at least warned about) by Adobe (and I just filed a bug report for it). Until that happens, I wanted to share this. For more, read on.  [More]
				</description>
				
				<category>IIS</category>
				
				<category>admin</category>
				
				<category>cf911</category>
				
				<category>cf10</category>
				
				<category>cf11</category>
				
				<category>webserver</category>
				
				<category>troubleshooting</category>
				
				<category>apache</category>
				
				<pubDate>Thu, 26 Feb 2015 22:35:00 -0500</pubDate>
				<guid>https://www.carehart.org/blog/2015/2/26/cf911_connect_sites_to_an_instance_with_wsconfig</guid>
				
			</item>
			
			<item>
				<title>ColdFusion Lockdown/Security guides - there are several, and some you may have missed</title>
				<link>https://www.carehart.org/blog/2014/6/24/ColdFusion_Lockdown_Security_guides</link>
				<description>
				
				While helping people with various problems in my &lt;a href=&quot;http://www.carehart.org/consulting/&quot;&gt;CF server troubleshooting services&lt;/a&gt;, I often have the chance to help people identify security vulnerabilities, especially in their configuration of CF and/or their web server, and sometimes related to their code.

I was wanting to point out to someone the various ColdFusion security resources, and while I have a category on them in my &lt;a href=&quot;http://www.cf411.com/cfsecres&quot;&gt;CF411 site&lt;/a&gt;, I thought this was a list worth pulling out into its own blog entry and expanding a bit.

You may be surprised to find that there are more to CF security guidelines than just the venerable server &quot;lockdown guide&quot; (for those administering and configuring CF, the OS, and the web server, among other things). 

Did you know that there have been &quot;developer security guidelines&quot; as well, focused instead on coding? This latter guide has gone through three iterations, including just recently, as I&apos;ll discuss along with the lockdown guides, below.  [More]
				</description>
				
				<category>IIS</category>
				
				<category>admin</category>
				
				<category>resource lists</category>
				
				<category>railo</category>
				
				<category>security</category>
				
				<category>apache</category>
				
				<pubDate>Tue, 24 Jun 2014 01:43:00 -0500</pubDate>
				<guid>https://www.carehart.org/blog/2014/6/24/ColdFusion_Lockdown_Security_guides</guid>
				
			</item>
			
			<item>
				<title>CF911- Why/when you MUST update the web server connector for ColdFusion 10/11 and may have missed it</title>
				<link>https://www.carehart.org/blog/2013/9/13/why_you_must_update_cf10_webserver_connector</link>
				<description>
				
				Have you installed or updated CF10 (or 11) and found that you still have problems with it running right, even when you have &quot;fully updated&quot; CF10? In this blog entry, I explain how it may NOT be that &quot;CF 10 is broken&quot; but rather that you may have missed an important step when updating it.

In brief, a VERY common problem is that while they MAY WELL have applied the provided &quot;updates&quot; for CF, &lt;b&gt;folks often do NOT notice that they may have to (and generally must) &quot;update&quot; the web server &quot;connector&quot; (if they are using an external web server, like IIS or Apache) as a separate manual step, after applying the update&lt;/b&gt;. 

I explain here what that means, how do to it, and why you may miss that you need to. 

&lt;b&gt;Update in 2019&lt;/b&gt;:&lt;br&gt;
&lt;blockquote&gt;
Since writing this entry, I did one in 2019 on &lt;a href=&quot;https://www.carehart.org/blog/2019/11/13/when_how_update_cf_web_connector&quot;&gt;When and how to upgrade CF web server connector, easier since CF2016&lt;/a&gt;, which at least makes it EASIER to upgrade, though much of what I write here still applies. I also updated this post since originally writing it, in ways discussed below.
&lt;/blockquote&gt;

(Or &lt;b&gt;if you&apos;d rather just have me help you quickly help you analyze and rectify your situation, whether with regard to the connectors or any other CF server troubleshooting, I can do that&lt;/b&gt; in a brief consulting session, likely less than an hour, remotely and securely. I provide all the detail here for those who prefer to &quot;go it on their own&quot;. For more on my consulting services, including rates, approach, satisfaction guarantee, and more, see the &lt;a href=&quot;http://www.carehart.org/consulting&quot;&gt;consulting page at carehart.org&lt;/a&gt;.)  [More]
				</description>
				
				<category>carehart classics</category>
				
				<category>IIS</category>
				
				<category>admin</category>
				
				<category>cf911</category>
				
				<category>cf10</category>
				
				<category>hotfix</category>
				
				<category>troubleshooting</category>
				
				<category>apache</category>
				
				<category>connector</category>
				
				<pubDate>Fri, 13 Sep 2013 01:51:00 -0500</pubDate>
				<guid>https://www.carehart.org/blog/2013/9/13/why_you_must_update_cf10_webserver_connector</guid>
				
			</item>
			
			<item>
				<title>Setting up ColdFusion to process html or other file extensions</title>
				<link>https://www.carehart.org/blog/2011/10/14/coldfusion_processing_html_or_other_file_extensions</link>
				<description>
				
				As a follow-on to my last entry, &lt;a href=&quot;http://www.carehart.org/blog/client/index.cfm/2011/10/14/cfbuilder_editing_htm_file_with_cf_editor&quot;&gt;Setting up CFBuilder to process htm files with the ColdFusion editor&lt;/a&gt;, I wanted to offer more info for those who may want to know more about this--or ensure that more is shared with any who would consider doing this.

If you&apos;re looking for &lt;b&gt;how to configure CFBuilder to open htm files with the CFML editor&lt;/b&gt;, see that other entry. &lt;b&gt;This one instead is about the related idea of having CF (the server) process htm (or other) file extensions&lt;/b&gt;. There are certainly pros and cons.  [More]
				</description>
				
				<category>general</category>
				
				<category>IIS</category>
				
				<category>admin</category>
				
				<category>apache</category>
				
				<pubDate>Fri, 14 Oct 2011 20:45:00 -0500</pubDate>
				<guid>https://www.carehart.org/blog/2011/10/14/coldfusion_processing_html_or_other_file_extensions</guid>
				
			</item>
			</channel></rss>