SignTool Error: The Specified Timestamp Server Either Could Not Be Reached or Returned an Invalid Response

Unable to sign your code due to this intermittent SignTool.exe error? We’ve got the answer
No matter how good you are at code signing, intermittent warnings can be difficult to identify and resolve. Here, we’ll explore a common SignTool timestamp-related error and will help you nail down how to fix it:
SignTool Error: The specified timestamp server either could not be reached or returned an invalid response.
SignTool Error: An error occurred while attempting to sign: c:\filepath\myexecutable.exe
What ’SignTool Error: The Specified Timestamp Server Either Could Not Be Reached or Returned an Invalid Response’ Means
SignTool failed to add a timestamp to your application because of an issue with the timestamp server.
Possible Cause(s)
There’s a problem with the timestamp server (e.g., it isn’t available, it’s overloaded, or you aren’t using the timestamp server of the CA that issued your code signing certificate).
How to Fix ‘SignTool Error: The Specified Timestamp Server Either Could Not Be Reached or Returned an Invalid Response’
Follow the first three troubleshooting instructions and related solutions suggested by DigiCert. They’ll work just fine, even if you don’t have a DigiCert code signing certificate. Make sure to replace the DigiCert’s details with those of the CA who issued your certificate.
Platform(s)/Systems Affected
Windows, SignTool.exe, Electron Builder.