ColdFusion 2023, Apache, Windows Server - "Service Unavailable The server is temporarily unable..."

[maryorie01]

The Apache localhost service works correctly, it allows me to browse .html pages; but when I try to browse .cfm pages it shows me the following error:

I really appreciate your guidance in solving this problem.

[Vikram_Kumar_M]

@maryorie01, please try adding the server's IP address to server.xml and workers.properties and restarting both the Apache and CF servers.

Server.xml is located at \ColdFusionxxxx\cfusion\runtime\conf:

Example:

<!-- begin connector-->

<Connector packetSize="65535" protocol="AJP/1.3" port="8020" address="IP-OF-SERVER" redirectPort="8453" secret="0f679950-252f-4b7a-96b1-b4c43650c9dc" maxThreads="500" connectionTimeout="60000" tomcatAuthentication="false"/>

Workers.properties is located at \ColdFusionxxxx\config\wsconfig\magic_folder:

Example:

worker.cfusion.type=ajp13
worker.cfusion.host=IP-OF-SERVER

Thanks,

Vikram

[maryorie01]

@Vikram_Kumar_M 

Hi, thank you very much for your reply. Based on what you have indicated, I have made the following changes:

C:\ColdFusion2023\cfusion\runtime\conf\server.xml: 

<Connector packetSize="65535" protocol="AJP/1.3" port="8022" redirectPort="8455" secret="5bfff42a-0584-407f-b7e7-ee60e013f242" maxThreads="500" connectionTimeout="60000" tomcatAuthentication="false"/>

I have changed "localhost" to 127.0.0.1  <Engine defaultHost="127.0.0.1" name="Catalina" jvmRoute="cfusion">

C:\ColdFusion2023\config\wsconfig workers.properties:

#ColdFusion Web Server Configuration File
#Wed Oct 30 13:36:48 CST 2024
1=Apache,C:/Apache24/conf,All,"",C:\\Apache24\\bin\\httpd.exe,"",false,cfusion,"",bitness64
1.srv=127.0.0.1,cfusion

C:\Apache24\conf\workers.properties

heartbeat_interval=30
heartbeat_limit=90

#Start of workers.properties associated with 'cfusion'
worker.list=cfusion

worker.cfusion.type=ajp13
worker.cfusion.host=127.0.0.1
worker.cfusion.port=8022
worker.cfusion.heartbeat_servlet_path=/__cf_connector_heartbeat__
worker.cfusion.connection_pool_timeout=60
worker.cfusion.monitoringsecret=95ef47e0-f204-44d5-bcab-75e8b36c803d
worker.cfusion.secret=5bfff42a-0584-407f-b7e7-ee60e013f242
#End of workers.properties associated with 'cfusion'

Restart the ColdFusion and Apache services.

But it does not work with Apache

[maryorie01 · Accepted solution]

@Vikram_Kumar_M 

Hi, thanks for your support; after much searching I managed to get ColdFusion pages to be displayed with Apache.

In addition to this, add in etc\hosts

127.0.0.1       localhost

::1             localhost

Thank you!

[Vikram_Kumar_M]

@maryorie01 I'm glad to hear it's working now. Thanks 🙂

[maryorie01]

Hi, @Vikram_Kumar_M thank you very much.
Now I have another question, I can't display the website on the public IP. What should I do additionally to be able to publish it?

[Vikram_Kumar_M]

@maryorie01 Does it work if you are using the IP address? You may have to check the bindings in Apache configuration and see if the Hostname is getting resolved by DNS from outside the server.

[maryorie01]

@Vikram_Kumar_M I'm setting up a new test server, for this reason I'm only accessing the server through the Public IP. But it doesn't work for me.

[Dave Watts]

I think you'd need to change your web server's listener to your public IP. That should be enough. The web server will still talk to CF via the localhost IPs (IPv4 and IPv6). To change the web server's listener, you'll need to edit httpd.conf, which should be in C:\Apache24\conf.

Out of curiosity, is there a reason you're using Apache on Windows instead of IIS? Not that there's anything wrong with that.

[maryorie01]

Hi @Dave Watts  , thank you very much for your response.
The need to use Apache is because we are creating a new server with coldfusion 2023 since the current server is on coldfusion 2018 with apache

I have made all the necessary changes and I have not been able to get the website to be seen through a public IP with Apache, with IIS it is done automatically

[Dave Watts]

What are the necessary changes you made to the Apache configuration?

I hesitate to mention this, but you could still use IIS instead of Apache here. Just change the webroot in IIS to wherever it is in Apache, and everything should work.

[Charlie Arehart]

Mary, you say "I have made all the necessary changes and I have not been able to get the website to be seen through a public IP with Apache, with IIS it is done automatically".

This seems to be a very different problem than what you raised here originally...and especially since that first issue has a marked "answer" above, you should probably create a new discussion.

If you do that, indicate whether this new challenge is limited to cf pages or not (as you indicated originally). I suspect it's about any request.

And if so, this would seem to have nothing to do with CF. As such, there are many things that could be amiss/need to be changed. It may be about a firewall on the box or in your network, or it may be about apache or even OS/networking configuration. 

Indeed, when you refer to iis working "automatically" I'm not sure what you mean, but are you saying one fact that iis IS running on this machine? (Your previous comments suggested that was on another machine.) Assuming it's not, you might find that even if iis WAS on this machine, it would fail to be reachable also--which would reassert my last point. 

Finally, if you feel you could create a new discussion that would address all these questions, doing that might be helpful. But if it feels unwieldy to try that, then just go ahead and answer here if you like.

Hope we can get to your resolution. 

[maryorie01]

Hi, thank you all for your answers and collaboration, maybe I didn't explain myself.

The localhost with Apache and ColdFusion works correctly, but when I try to access it through the public IP it doesn't show the page. If I changed to IIS and access the pages through the public IP it does work, but the navigation is very slow.

For this reason I want the configuration to be with Apache.

[Charlie Arehart]

You can have what you want, and the resolution may well be a simple one. But I'm afraid there's just too much to consider (for your various issues) such that it seems it will not be readily solved via back and forth here. Perhaps someone else will help that way.

But I will say that if you "just want it solved" (working with either apache or iis, whether locally or via your public IP, and without any delay difference between those), I feel confident that we can achieve that via a remote screenshare consulting session. I don't think it would take even a hour--though I can't promise that.

But I can promise that you won't pay for any time you don't find valuable, so if you do really want it solved and are in a position to pay for such help, you can learn more about my rates, approach, satisfaction guarantee, online calendar, and more. Otherwise again perhaps others here (including Adobe) may work to draw out the cause and solution. BTW, I do help daily here with problems suited to such back and forth, so I hope you'll not conclude that I'm withholding help "to get paid".

[maryorie01]

Hi, I have been authorized to request support remotely.
How would I be paid?
We have a standard 2023 license.
1) ColdFusion 2023 with IIS works correctly on localhost and Public IP (automatically), but the response time and navigation are very slow.
2) ColdFusion 2023 with Apache works correctly on localhost, but does not work with Public IP

[Dave Watts]

Has using a public IP address ever worked with your Apache instance at all? Do you think this is a CF issue, or a web server configuration issue, or a networking issue?

[maryorie01]

Hi, there has never been a working instance of the Public IP with Apache because we are setting up a new server.

We are migrating the current server to a new one:
Current Server:
Windows Server 2019
ColdFusion 2018
Apache 2.4.41 (Win32) Open SSQL 1.1.1

New Server:
Windows Server 2022
ColdFusion 2023
Apache 2.4.62 (Win64)

[Dave Watts]

This doesn't sound like a CF problem, really. It sounds like a networking problem or a web server problem. It seems like the more we're talking, the less I understand! Anyway, though, try setting up a static web site for testing using the public IP first.

[jpt61905309]

Always use 127.0.0.1 for any appearance of "localhost". This will solve the confusion of IPv4 from IPv6. Correct the property file at the Apache conf folder and CF connector folder.