Knowledgebase
Knowledgebase: PaperCut > Debugging
How to enable SSL debug mode
Last modified on 12 August 2020 11:10 PM

“I’ve been asked to enable SSL debugging by a member of the PaperCut Support Team. I’ve looked everywhere, how am I meant to do that?”

From time to time the PaperCut developers may call on the PaperCut Support Team to enable Java SSL debugging in a PaperCut environment when troubleshooting SSL handshake issues. This can give us a highly verbose logging of SSL connections to the PaperCut NG/MF Application server. For most PaperCut System Administrators the resulting information can be overwhelming unless you know exactly what you’re looking for before you begin searching through the resulting debug logs, so only look to follow this guide if you’re an SSL or Security expert.

Please note: as all the steps below require you to download the debug mode diagnostics bundle as the final steps of retrieving your logs to provide to the PaperCut Support Team, we would recommend enabling debug mode on the PaperCut Application Server before enacting any of the following procedures.

After v17.3

  1. Log onto the server hosting and running PaperCut NG/MF.
  2. Using a text editor (such as notepad.exe or SublimeText), open the server.properties file with administrator-level privileges.

For example; on a 64-bit Windows server running PaperCut MF this would be found in C:\Program Files\PaperCut MF\server\custom\server.properties.

  1. Using the text editor’s search function, find the line: #server.ssl.debug-output=N
  2. Remove the # entry and change the value to Y.


For example, server.ssl.debug-output=Y.

  1. Save the server.properties file.
  2. Re-start the PaperCut Application Server service. The verbose SSL debugging will output additionally into the existing service.log file when the change takes effect.


For example, on a 64-bit Windows server running PaperCut MF this would be C:\Program Files\PaperCut MF\server\logs\service.log.

  1. Attempt to reproduce the SSL issue you’re having.
  2. Download the debug .zip file from your PaperCut NG/MF server to share with Support Team. This is found in Options > Advanced > Diagnostics > Download Diagnostics File.

Before v17.3

Windows & Linux

  1. Log onto the server hosting and running PaperCut NG/MF.
  2. Using a text editor (such as notepad.exe or SublimeText), find and open the service.conf file.

For example, on a 64-bit Windows server running PaperCut MF would be C:\Program Files\PaperCut MF\server\custom\service.conf.

  1. Add the following line: wrapper.java.additional.8=-Djavax.net.debug=all
  2. Save the service.conf file.
  3. Restart the PaperCut Application Server. The verbose SSL debugging will output to a new server-out.log file when the change takes effect.


For example, on a 64-bit Windows server running PaperCut MF this would be C:\Program Files\PaperCut MF\server\logs\server-out.log

  1. Attempt to reproduce the SSL issue you’re having.
  2. Download the debug .zip file from your PaperCut NG/MF server to share with Support Team. This is found in Options > Advanced > Diagnostics > Download Diagnostics File.

macOS

  1. Log onto the server hosting and running PaperCut NG/MF.
  2. Using a text editor (such as SublimeText), find and open the service.conf file.

For example, on a macOS server running PaperCut MF this would be PaperCut MF/server/custom/launch-app-server.conf

  1. Add the following line at the end of the service.conf file: PC_CUSTOM_SERVER_ARG=-Djavax.net.debug=all
  2. Save the service.conf file.
  3. Restart the PaperCut Application Server. The verbose SSL debugging will output to a new server-out.log file when the change takes effect.


For example; on a PaperCut MF server on macOS, this file would be located in: PaperCut MF/server/logs/server-out.log

  1. Attempt to reproduce the SSL issue you’re having.
  2. Download the debug .zip file from your PaperCut NG/MF server to share with Support Team. This is found in Options > Advanced > Diagnostics > Download Diagnostics File.