No ColdFusion 2023 debug output
I have just installed CF2023 developer on a new Windows 11 Pro system. I have enabled debug output in CF Admin, and confirmed my IP address (127.0.0.1) is allowed to see the debug output. The pages have cfsetting showdebugoutput=”Yes” in place. However, no debug output is included when running the application (via the built-in CF server using localhost:8500). The application seems to be running fine, but I need to see the debug output.
Newbie
2 posts
Thank you both for your suggestions. Unfortunately, since my original post, the issue has gotten muddier. It’s not the IP address nor “localhost”. The sites work fine with 127.0.0.1:8500, and I have begun seeing some of the debug output. However, I only see the “database activity” section (sql queries) on some CFM pages but not others, even though I know the pages where it is missing invoked new queries. I have not yet determined the differences between those CFM templates where database debug is shown and those where it is not.
The 2nd strangeness is that the section of debug which is selected with the “Report Execution times” checkbox, and offers “summary” and “tree” modes never appears. It’s as if some piece of the CF install is missing or broken. If it’s logging errors about this, I can’t find them.
That’s not a known problem I’ve heard of, though perhaps Priyank or others might have seen it. Same about your wondering if something is not quite installed right.
Priyank’s suggestion should work, and assuming it does I would propose you could solve the problem differently by adding ::1 to the cf admin debugging ip addresses page. That way you’d need not remember to change the url. 🙂
The issue is not a change in cf (nor a bug), but a change in your move to Windows 11. It enables ipv6 by default, and so if you do a “ping localhost” at the command line that should return ::1 (if all our assumptions here are true). And THAT is why the need to consider one option or the other to resolve this.
Some may suggest also that you could edit your Windows hosts file, to tell THAT to change your system to regard localhost as resolving to 127.0.0.1, instead. Indeed, you could even turn off ipv6 in windows entirely. There are arguments for and against either of those, and a Google search on the topics will find details.
Hope either of our simpler solutions will suffice for this issue you raise. (And sorry that it took so long for a reply.)
Hi,
Instead of using localhost:8500, try using 127.0.0.1:8500 and let me know if that will show the debug info that you are looking for.
You must be logged in to post a comment.
23 Nov
10AM Pacific
Online
