Hello, 4-5 months ago I installed Coldfusion 2018 on my new Dell Precision Laptop Workstation. It is high performance and running Windows 10. At that time I was able to access Coldfusion 2018 Admin and had 2 dynamic applications working fine. Three weeks ago I saw there were Coldfusion 2018 Updates available (I think 4 of them) and I did the latest update. Initially everything worked great but after my first reboot I get the error below and cannot access Coldfusion Admin (http://127.0.0.1:8500/CFIDE/administrator/index.cfm). I have since uninstalled and reinstalled Coldfusion 2018 at least 8 times now and still the same exact problem, I can access Admin after a fresh install but once I reboot I have the exact same problem. Really frustrated , any help would be greatly appreciated.
Thanks in advance,
Kirk
This site can’t be reached 127.0.0.1 refused to connect. Try:
- Checking the connection
- Checking the proxy and the firewall
ERR_CONNECTION_REFUSED
Newbie
1 posts
Same thing happened to me when I installed the latest update.
Good job Adobe!
Miker, which “same thing” are you referring to? Do you mean you applied a CF update and since then can’t get to the cf admin, after a reboot, even after uninstalling and reinstalling several times, like Kirk describes above? That was a pretty unusual situation, and I’d been hoping he might reply with more after the couple of comments below from that week.
Or do you mean the JVM problems like insuractive describes in the comment below?
If your problem has arisen after applying a CF update, had you checked out the blog post of mine which insuractive shared, where I help you see how to find and resolve problems after a CF update:
https://coldfusion.adobe.com/2019/03/problems-applying-cf-update-check-first/
As for Kirk, I hope he may get pinged on this like I did (when you offered your comment earlier today), so that he might come back and let us know how it turned out.
I will say finally that I’ve never seen a problem like those being described here (above and below) that I’ve not been able to solve. We can all certainly try to hash things out over time here in the portal comments. But if anyone is ever in a pinch and “just wants it solved” ASAP, I should be able to, in a remote screenshare session–or you won’t pay for the time you don’t value (could be less than an hour of time). More at carehart.org/consulting.
More than that, though, I’ll say this: if I can’t solve the post-update problems that you and Kirk are reporting, I’d even pay YOU my rate for the hour spent coming to that conclusion. That’s how confident I am that these problems should be solvable, and if I can’t, it’s on me. How’s that for putting my money where my mouth is? 🙂
We discovered that the CF updates have been proactively updating the version of the jre installed on our local machines. The problem we encountered was that some of our team was storing the Java folder in their program files directory. Suprise, the CF installer was hitting some sort of install permission issue (that’s our best guess at least since the issue did not affect others). We were able to track down the CF admin file that contained the server java settings and manually update the JRE to point to the new JRE folder and after that we were able to start up the service normally.
That having been said, each Hotfix issue seems to be its own unique challenge – This blog post by Charlie is worth a permanent bookmark: https://coldfusion.adobe.com/2019/03/problems-applying-cf-update-check-first/
Thanks, insuractive. I was just about to post a comment to Kirk to consider what I shared in that post. It nearly always explains the scenario he describes.
If he confirms that perhaps it’s not that, then we can consider other possibilities.
You must be logged in to post a comment.
23 Nov
10AM Pacific
Online
