Enabling Content Gateway debugging and locating relevant log files
- Article Number: 000006644
- Products: Forcepoint V10000 Appliance, Forcepoint V20000 Appliance, Forcepoint V5000 Appliance, Forcepoint Virtual Appliance, Forcepoint Web Security, Forcepoint X Series Appliance, TRITON AP-WEB
- Version: 8.5, 8.4, 8.3, 8.2, 8.1, 8.0
- Last Published Date: October 21, 2020
Notes & Warnings
Important: Only keep Web Content Gateway (WCG) debugtags enabled as long as you are actively troubleshooting issues. Always disable debugging after you have collected the required information. Debugging on production servers should be enabled only long enough to reproduce a specific issue.
Note: The following WCG alarm may trigger if when debug is enabled:
Debugging has been enabled and is active. Disable debugging as soon as the needed information is captured, and then clear this alarm.
Follow the below steps to disable any previously enabled debugging before clearing the Alarm.
Note: Using record.config entry proxy.config.diags.debug.client_ips can suppress output of other debugtag see Content Gateway Debug and proxy.config.diags.debug.client_ips for details .
Applications are failing when proxying through the Content Gateway. What troubleshooting logs are available to help diagnose this issue?
Three types of logs are available when troubleshooting the Web Content Gateway.
Note The file paths shown below are provided for Content Gateway software installations. For V-Series appliances users, direct file access is only available with assistance from Forcepoint Technical Support.
Click Configure > My Proxy > Logs > Access tab > Log File > extended.log and error.log.
Separate each debug string with a pipe. For example:
or for a single tag:
Press CTRL+C to disable debugging.
For Content Gateway installed on a V-Series appliance without Root Access:
Note With 8.3-8.5 or higher using CLI, the reload configuration option (content-line -x) was removed as the file will read immediately.
For versions 7.7-8.2
In the Content Gateway console, click Configure > My Proxy > Logs > System tab > Log File > content_gateway.out.
Common debug tags:
Log locations within the Content Gateway management console
Keywords: debug; debugging; debugtag; content gateway; proxy error; troubleshooting; error.log; extended.log; records.config; content_gateway.out; web content gateway not working