Laura, are you referring to wanting the CF "debugging output" (which appears at the bottom of CF pages)? or are you wanting the interactive step debugger (which you would use via the CFBuilder IDE)?
Your mention of the debug port and your first screenshot are about the latter (step debugging), while your 2 of your 3 other screenshots are about the former (debug output). To be clear, the two sets of features (and their settings) are technically unrelated to each other.
And I'm going to assume for now you are referring to the debug output feature (since you showed those 2 screenshots related to it), and that the issue is that you are visiting a page and expect to see the debug output at the bottom but none appears. But you've not shown us the URL for either your CF admin or the URL you're testing, so for now we have to do some guessing. Is the CF which you're testing against implemented on your own machine?
And if you drop this code into the CF page, it will show the IP address which CF sees you coming from:
<cfoutput>#cgi.remote_addr#</cfoutput>
or as cfscript:
writeoutput(cgi.remote_addr)
The value reported is what needs to be put into your "debugging ip address" list shown in the second screenshot.
Does that help?
BTW, note that if it helps but only temporarily (because your IP address is changing), or you notice that it's not even what you would have thought was your ip address, it could be that the site you're testing is being handled by a proxy like cloudflare. In that case, the IP address may well change, often--but such proxies would normally pass in a request header identifying the original ip adddress, and there's a way to setup CF to regard that header for the value shown for the cgi.remote_addr. I have a blog post on the Adobe CF portal discussing that. And I mention this because that would affect the IP address which would be used by the CF Admin "debugging ip address" list.
If instead you really mean to be dealing with an inability to use the step debugger in CFBuilder, that's a very different discussion with much more to consider.
Finally, since you refer to the error you found in the log, we might wonder if instead of "debugging" you may be referring to wanting to see the "error details" which that "enable robust exception information" option in the 3rd screenshot should enable. If THAT is your problem, that too is a different matter. It also has NOTHING to do with the ip address settings within CF. Instead, that is often blocked for those using IIS as their web server, which is set by default to show error details only to what it regards as "local" requests. See the IIS "error pages" feature and its "edit feature settings" to enable the third of 3 values shown there. But since I'm sitll guessing whether this is at all your issue, I will wait to hear your thoughts. 🙂
/Charlie (troubleshooter, carehart.org)
1 Correct answer
6
Replies
AdChoices
