We are using http://timestamp.comodoca.com TSA server to sign our jar and exe files with certificate obtained from Comodo. Signing of jar files happens quite often and it seems that currently something is not working. Here is the output from “jarsigner”:
jarsigner: unable to sign jar: java.io.IOException: MIME Content-Type is not application/timestamp-reply
It seems it’s not only the timestamp server that’s not working. I just discovered ‘Trusted Site Seal from Comodo’ (for EV SSL certificates) reports:
“This site is currently undergoing maintenance. We will be back shortly.”
Although these are my first posts in this forum, I’ve been happily using Comodo certificates for over 10 years. But they are quite messing up now. The timestamp server is down for at least 17 hours…
Time stamp server is still not working. When will this be back up??? We have a release that needs to go out today and this is the only thing preventing us from releasing. Please give us a response!!!
The server came back online, but it seems unreliable and is failing with this same error intermittently. Anyone else having the same problem? Any word on COMODO as to when this will actually be completely fixed?
It seems that the server is down again. Or something is wrong with the configuration. We started getting the following error during signing of jar file:
jarsigner: unable to sign jar: java.io.IOException: MIME Content-Type is not application/timestamp-reply