This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Mozilla Support में खोजें

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

How do I fix SSL error 61 (Linux OS)

  • 6 प्रत्युत्तर
  • 8
  • 1 view
  • के द्वारा अंतिम प्रतियुतर cklugh

more options

Every time I try to connect to my internal website from a Linux OS Thin Client I recieve the SSL error 61. Firefox is the only browser on the Thin Client. There are no issues connecting from Non-Linux systems on any browser including Firefox.

Error Below: SSL error Contact your help desk with the following information: You have not chosen to trust " Go Daddy Secure Certificate Authority - G2", the issuer of the server's security certificate (SSL error 61).

How do I fix this error? I have already tried installing the cert manually to the client.

Every time I try to connect to my internal website from a Linux OS Thin Client I recieve the SSL error 61. Firefox is the only browser on the Thin Client. There are no issues connecting from Non-Linux systems on any browser including Firefox. Error Below: SSL error Contact your help desk with the following information: You have not chosen to trust " Go Daddy Secure Certificate Authority - G2", the issuer of the server's security certificate (SSL error 61). How do I fix this error? I have already tried installing the cert manually to the client.

चुने गए समाधान

Cor-el: This does solve the issue for SHA1 certs.


I have added the certificate to the Citrix DB. I finally found the issue after researching the forums of Citrix and other various sites.

This issue is the cert itself, we purchased a cert and uses SHA2, however the Linux Citrix Receiver does not support SHA2 at this point.

So the only resolution is to either Re-Key the cert to use SHA1 or wait for an update from Citrix.

Thank you both for your time.

c

संदर्भ में यह जवाब पढ़ें 👍 0

All Replies (6)

more options

With Citrix? I do see threads on that on the web:

error-61 "You have not chosen to trust"

The discussion seems to be outside the scope of Firefox support, but it could be that I just don't understand it very thoroughly.

more options

It is connecting through a Citrix Receiver but that should be irreverent as the certs are installed through Firefox and are handled, and Firefox is the application displaying that the CA is not trusted.

I guess what I'm getting at is for some reason the CA is not trusted, how do I force Firefox to realize that the CA is trusted even though I have installed the Root cert already. I have contacted Citrix and they said this is not their issue, HP has no idea why. The last party I have not contacted is Firefox. Maybe I'm just grasping at straws here?

more options

Hmm, I don't think that error message is generated by Firefox...

Are you getting the usual two or three-part error page with a Technical Details section? If so, please copy the contents of that section and paste it in a reply.

more options

No, it does not have the error page. I did however just notice that the prompt is being displayed by Receiver. So, I can rule out Firefox causing the issue. Although the browser does connect to the Receiver hence my thinking that Firefox was causing an issue.

Thank you for you time and helping me talk thought this with a fresh pair of eyes so to speak.

more options

You would have to add this certificate to the Citrix certificate database.

more options

चयनित समाधान

Cor-el: This does solve the issue for SHA1 certs.


I have added the certificate to the Citrix DB. I finally found the issue after researching the forums of Citrix and other various sites.

This issue is the cert itself, we purchased a cert and uses SHA2, however the Linux Citrix Receiver does not support SHA2 at this point.

So the only resolution is to either Re-Key the cert to use SHA1 or wait for an update from Citrix.

Thank you both for your time.

c