Debugging & Logging - IP Addresses
Configure IP filtering for debug output and secure debugging access
Overview
The IP Addresses page in ColdFusion Administrator provides centralized configuration for restricting debug output and debugging features to specific IP addresses. This critical security feature ensures that sensitive debugging information is only visible to authorized developers, not to end users or potential attackers. IP filtering enables safe debugging in staging and even production environments when emergency troubleshooting is required.
Without IP filtering, enabling debug output would expose application internals, database queries, variable contents, and file paths to all users. IP filtering creates a secure boundary where only requests from approved IP addresses receive debug output, while all other users see the application normally without any debugging information. Adobe notes that if you do not specify IP addresses and debugging options are active, ColdFusion displays debugging output for all users (source: Use the ColdFusion administrator).
IP Address Configuration
Configure which IP addresses can receive debug output and debugging information.
Adding IP Addresses
192.168.1.100::1 (ColdFusion 2021 and later accept it directly; source: Charlie Arehart)127.0.0.1, 0:0:0:0:0:0:0:1 and ::1 (IPv4 and IPv6 loopback) are the default entries, per neo-debug.xml iplist in the ColdFusion 2025 Update 14 Docker imageRanges
Removing IP Addresses
IP Detection and Challenges
Understanding how ColdFusion detects client IP addresses in different network configurations.
Direct Connections
- Scenario
- User connects directly to CF server
- IP Source
- CGI.REMOTE_ADDR shows the client address ColdFusion received
- Reliability
- Most reliable scenario for IP filtering
CF compares CGI.REMOTE_ADDR to the IP list for matching
Proxy Servers
- Challenge
- ColdFusion may receive the proxy's address instead of the client's
- X-Forwarded-For
- Not used by the debugging IP check; passing the header alone changes nothing
- Configuration
- Only a Tomcat-level change such as RemoteIpValve alters the address CF sees (source: Charlie Arehart)
Adding the proxy IP to the list exposes debug output to every client behind the proxy
Load Balancers
- Issue
- The balancer's address may be what ColdFusion receives
- Headers
- X-Forwarded-For and X-Real-IP are not read by the debugging IP check unless Tomcat's RemoteIpValve is configured
- Alternative
- Debug against a single node directly from an allowed IP
Use cfdump var="#CGI#" to see what CF detects
VPN Connections
- Challenge
- VPN exit node IP may change
- Solution
- Add all possible VPN exit node IPs
- Alternative
- Add each VPN exit address separately
Corporate VPN usually has stable IP range. Test your IP while connected to VPN.
Dynamic IPs (Home/Mobile)
- Problem
- Developer IP changes frequently
- Solution 1
- Use Add Current after your address changes
- Solution 2
- Use VPN with static IP
Remove old addresses when they change. Consider authentication instead of IP filtering.
Security Considerations
Information Disclosure Prevention
Security Best Practices
- Use as few specific IP addresses as possible
- Regularly audit and remove outdated IPs
- Document who owns each IP address
- Monitor for unauthorized access attempts
- Use VPN for remote developers when possible
- Test IP filtering from both allowed and disallowed IPs
Production Debugging
Common Mistakes
- Not testing from disallowed IP: May not realize filtering is ineffective
- Forgetting to update after IP changes: Legitimate developers blocked
- Removing every entry: An empty list shows debug output to all users
- Not documenting IPs: Unclear who each IP belongs to
Testing IP Filtering
Verification Process
- Determine your current IP (use whatismyip.com or similar)
- Add your IP to allowed list in CF Administrator
- Enable debug output in Debug Output Settings
- Access application from your IP - debug output should appear
- Access from different IP or use proxy - no debug output should appear
Test IP Detection Script
Use this script to see what IP ColdFusion detects for your requests:
<!--- /admin/ip-test.cfm --->
<cfscript>
// Display all relevant IP-related CGI variables
ipInfo = {
"REMOTE_ADDR": cgi.remote_addr,
"HTTP_X_FORWARDED_FOR": cgi.http_x_forwarded_for ?: "Not set",
"HTTP_X_REAL_IP": cgi.http_x_real_ip ?: "Not set",
"HTTP_CLIENT_IP": cgi.http_client_ip ?: "Not set"
};
</cfscript>
<!DOCTYPE html>
<html>
<head>
<title>IP Detection Test</title>
<style>
body { font-family: Arial, sans-serif; padding: 20px; }
table { border-collapse: collapse; width: 100%; max-width: 600px; }
th, td { border: 1px solid #ddd; padding: 12px; text-align: left; }
th { background-color: #f0f0f0; font-weight: bold; }
</style>
</head>
<body>
<h1>IP Detection Test</h1>
<p>This shows what IP information ColdFusion can see:</p>
<table>
<tr>
<th>Variable</th>
<th>Value</th>
</tr>
<cfloop collection="#ipInfo#" item="key">
<tr>
<td><cfoutput>#key#</cfoutput></td>
<td><cfoutput>#ipInfo[key]#</cfoutput></td>
</tr>
</cfloop>
</table>
<h2>Recommendations</h2>
<ul>
<li>Add <strong><cfoutput>#cgi.remote_addr#</cfoutput></strong> to IP whitelist</li>
<cfif len(cgi.http_x_forwarded_for)>
<li>Note: X-Forwarded-For detected - you may be behind a proxy/load balancer</li>
</cfif>
</ul>
</body>
</html><!--- /admin/ip-test.cfm --->
<cfset ipInfo = {
"REMOTE_ADDR" = cgi.remote_addr,
"HTTP_X_FORWARDED_FOR" = len(cgi.http_x_forwarded_for) ? cgi.http_x_forwarded_for : "Not set",
"HTTP_X_REAL_IP" = len(cgi.http_x_real_ip) ? cgi.http_x_real_ip : "Not set",
"HTTP_CLIENT_IP" = len(cgi.http_client_ip) ? cgi.http_client_ip : "Not set"
}>
<!DOCTYPE html>
<html>
<head>
<title>IP Detection Test</title>
<style>
body { font-family: Arial, sans-serif; padding: 20px; }
table { border-collapse: collapse; width: 100%; max-width: 600px; }
th, td { border: 1px solid #ddd; padding: 12px; text-align: left; }
th { background-color: #f0f0f0; font-weight: bold; }
</style>
</head>
<body>
<h1>IP Detection Test</h1>
<p>This shows what IP information ColdFusion can see:</p>
<table>
<tr>
<th>Variable</th>
<th>Value</th>
</tr>
<cfloop collection="#ipInfo#" item="key">
<tr>
<td><cfoutput>#key#</cfoutput></td>
<td><cfoutput>#ipInfo[key]#</cfoutput></td>
</tr>
</cfloop>
</table>
<h2>Recommendations</h2>
<ul>
<li>Add <strong><cfoutput>#cgi.remote_addr#</cfoutput></strong> to IP whitelist</li>
<cfif len(cgi.http_x_forwarded_for)>
<li>Note: X-Forwarded-For detected - you may be behind a proxy/load balancer</li>
</cfif>
</ul>
</body>
</html>- Create this file in your webroot (e.g.,
/admin/ip-test.cfm) - Access it from your browser
- Note the REMOTE_ADDR value - this is what CF uses for IP filtering
- Add that IP to the CF Administrator IP whitelist
Troubleshooting Access Issues
- Verify IP actually matches allowed list using the test script above
- Check debug output is enabled in Debug Output Settings
- Confirm your own IP is in the list (it defaults to the loopback addresses only: 127.0.0.1, 0:0:0:0:0:0:0:1 and ::1)
- Behind a proxy or load balancer, CF sees the proxy's IP; X-Forwarded-For is not used unless RemoteIpValve is configured
- Verify IPv4 vs IPv6 - ensure using correct IP version
Multi-Environment Testing
- Test IP filtering in each environment (dev, staging, production)
- Verify proxy/load balancer IP handling in each environment
- Different IPs may be needed for different environments
- Document environment-specific IP configurations
- Localhost (127.0.0.1) works for server-based testing
Development Workflows
Team Development
- IP Management
- Maintain list of all developer IPs
- Updates
- Update IP list as team members join/leave
- VPN
- Use a VPN with static exit addresses for easier management
Document process for developers to add their IP. Add each office address that needs debug output.
Remote Development
- VPN
- Use VPN for consistent IP addressing
- SSH Tunnel
- Secure access to staging servers
- Multiple IPs
- Add home IP plus VPN IP for flexibility
Mobile hotspot IP may differ from home/office. Keep IP list updated as developers work from different locations.
Contractor/Temporary Access
- Documentation
- Note expiration date with contractor IPs
- Removal
- Review and remove after project ends
- Authorization
- Document who authorized each temporary IP
Consider time-limited access mechanisms. Maintain audit log for contractor access.
Configuration Examples
Single Developer
127.0.0.1
192.168.1.100Development Team in Office
127.0.0.1
10.0.1.25 # Office workstation
74.125.224.100 # VPN exit nodeProduction Emergency Debugging
203.0.113.50 # Senior admin home IP
198.51.100.10 # Admin via VPNLoad Balanced Environment
127.0.0.1 # localhost
# Behind a load balancer, ColdFusion may receive the balancer's IP.
# Listing a shared balancer IP exposes debug output to every client behind it.
# Debug against a single node directly from an allowed IP instead.Alternative Approaches
Application-Level Filtering
- Implementation
- IP checking in Application.cfc
- Advantages
- More granular control than CF Administrator
- Features
- Database for dynamic IP management, time-based access rules
Allows per-application customization and dynamic IP lists without administrator access.
Authentication-Based Debugging
- Method
- Require login to enable debug mode
- Session
- Debug tied to authenticated user
- Auditing
- Track who enabled debugging
More flexible than IP-based filtering. Works well for dynamic IPs and remote teams.
Separate Debug URLs
- Method
- Special URL parameters enable debugging
- Security
- Combine with authentication or shared secret
- Control
- Enable/disable per request
Easy to enable/disable per request. Can implement custom debug output tailored to needs.
Common Issues and Solutions
IP Filtering Not Working
- Verify debug output is enabled in Debug Output Settings
- Check the list: it defaults to the loopback addresses (127.0.0.1 and the IPv6 equivalents), and removing every entry can expose debug output to all clients
- Dump
CGI.REMOTE_ADDRto see detected IP - Match detected IP to allowed list format (exact match required)
- Check for typos in IP address entries
Can't Access from Expected IP
- Confirm whatismyip.com matches added IP exactly
- Check if proxy/load balancer is changing your IP
- Look for typos in IP address (e.g., 192.168.1.10 vs 192.168.1.100)
- Verify using IPv4 not IPv6 (or vice versa)
- Use the IP test script above to verify what CF sees
IP Changes Frequently
- Use VPN with static IP: Most reliable solution
- Dynamic IP update mechanism: Build admin tool for developers to update their IP
- Authentication-based debugging: Use login instead of IP filtering