- This topic has 4 replies, 3 voices, and was last updated Mar 19-12:14 am by andfree.
Viewing 5 posts - 1 through 5 (of 5 total)
Viewing 5 posts - 1 through 5 (of 5 total)
- You must be logged in to reply to this topic.
Forum for users of antiX Linux. Mean and Lean and Proudly anti-fascist.
Forum › Forums › New users › New Users and General Questions › Palemoon – Connection Failed
Tagged: connection failed, encryption algorithms, palemoon
When I try to connect to this site, Palemoon gives me this message:
Secure Connection Failed
An error occurred during a connection to athenacard.gr.
Cannot communicate securely with peer: no common encryption algorithm(s).
(Error code: ssl_error_no_cypher_overlap)
The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
Please contact the website owners to inform them of this problem.
No connection problem if using Firefox ESR.
I use palemoon-nonsse2, version 27.8.1 (32-bit).
No connection problem if using Slimjet, too.
So, it seems that the problem has to do with Palemoon.
I did a search at Palemoon forum for this phrase:
ssl_error_no_cypher_overlap
Too many results. It seems to be a quite common connection problem, not only to the specific site.
This seems to be a start point. Perhaps I’ ll see it later.
I’ve been using PM for a long while and in many distros (Obarun, Artix, ….will no longer mention it …, antix, void) and never had a problem accessing this site.
Are you running any plugins on pm that may have it black listed?
anti-X - Adélie - obarun - systemd Free Space
This seems to be a start point. Perhaps I’ ll see it later.
The page you linked, it contains an explanation of “why?” (decidedly “for your own good”) and instructions howto override/change/fix
Well, “point 2” (RC4) is the case. After having set to true security.ssl3.rsa_rc4_128_sha in the preferences list and added the hostname of the site to security.tls.insecure_fallback_hosts, I connect to it without problem. So, I suppose it’s actually an issue for the server operators, and not about the browser. I would mark this topic as “solved” (if I could).
| Cookie | Duration | Description |
|---|---|---|
| cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
| cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
| cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
| cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
| cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
| viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |