Firefox: SSL_ERROR_RX_RECORD_TOO_LONG
I know this has been asked before, but have there been any changes recently?
My server machine runs under Ubuntu-18.04 Server (+ lxde).
It has apache-2.4.29 with 2 domains, both with http and https.
It also has a mail server, citadel-917, which has its own webserver for webmail.
At boot up apache2 should use ports 80 and 443, and citadel should use 8080 and 8081.
But Firefox-65.0 gets "Secure Connection Failed. Error code: SSL_ERROR_RX_RECORD_TOO_LONG"
despite "sudo systemctl restart apache2" working without errors and opening port 443.
How can Apache2 and Firefox produce no intelligible error messages when it the system not working?
And how do I fix it? or even find out what is wrong?
I have updated my LetsEncrypt certificates and stared at the conf files and they all look OK.
I have done "apachectl configtest" and it says "syntax OK".
"netstat -nlp" shows port 80 and 443 are listening, but only for tcp6, not tcp, is this right?
gufw-report shows 443 applies to both TCP and TCP(v6).
/var/log/apache2/error.log is OK.
I have had this working before a recent clean install after a new SSD had a boot sector virus.
apache2 firefox
asked 4 mins ago
Dave KimbleDave Kimble
66118
add a comment |
I know this has been asked before, but have there been any changes recently?
My server machine runs under Ubuntu-18.04 Server (+ lxde).
It has apache-2.4.29 with 2 domains, both with http and https.
It also has a mail server, citadel-917, which has its own webserver for webmail.
At boot up apache2 should use ports 80 and 443, and citadel should use 8080 and 8081.
But Firefox-65.0 gets "Secure Connection Failed. Error code: SSL_ERROR_RX_RECORD_TOO_LONG"
despite "sudo systemctl restart apache2" working without errors and opening port 443.
How can Apache2 and Firefox produce no intelligible error messages when it the system not working?
And how do I fix it? or even find out what is wrong?
I have updated my LetsEncrypt certificates and stared at the conf files and they all look OK.
I have done "apachectl configtest" and it says "syntax OK".
"netstat -nlp" shows port 80 and 443 are listening, but only for tcp6, not tcp, is this right?
gufw-report shows 443 applies to both TCP and TCP(v6).
/var/log/apache2/error.log is OK.
I have had this working before a recent clean install after a new SSD had a boot sector virus.
apache2 firefox
asked 4 mins ago
Dave KimbleDave Kimble
66118
I Also get that error when I mistake http with https...
– Rui F Ribeiro
1 min ago
add a comment |
I know this has been asked before, but have there been any changes recently?
My server machine runs under Ubuntu-18.04 Server (+ lxde).
It has apache-2.4.29 with 2 domains, both with http and https.
It also has a mail server, citadel-917, which has its own webserver for webmail.
At boot up apache2 should use ports 80 and 443, and citadel should use 8080 and 8081.
But Firefox-65.0 gets "Secure Connection Failed. Error code: SSL_ERROR_RX_RECORD_TOO_LONG"
despite "sudo systemctl restart apache2" working without errors and opening port 443.
How can Apache2 and Firefox produce no intelligible error messages when it the system not working?
And how do I fix it? or even find out what is wrong?
I have updated my LetsEncrypt certificates and stared at the conf files and they all look OK.
I have done "apachectl configtest" and it says "syntax OK".
"netstat -nlp" shows port 80 and 443 are listening, but only for tcp6, not tcp, is this right?
gufw-report shows 443 applies to both TCP and TCP(v6).
/var/log/apache2/error.log is OK.
I have had this working before a recent clean install after a new SSD had a boot sector virus.
apache2 firefox
asked 4 mins ago
Dave KimbleDave Kimble
66118
I know this has been asked before, but have there been any changes recently?
My server machine runs under Ubuntu-18.04 Server (+ lxde).
It has apache-2.4.29 with 2 domains, both with http and https.
It also has a mail server, citadel-917, which has its own webserver for webmail.
At boot up apache2 should use ports 80 and 443, and citadel should use 8080 and 8081.
But Firefox-65.0 gets "Secure Connection Failed. Error code: SSL_ERROR_RX_RECORD_TOO_LONG"
despite "sudo systemctl restart apache2" working without errors and opening port 443.
How can Apache2 and Firefox produce no intelligible error messages when it the system not working?
And how do I fix it? or even find out what is wrong?
I have updated my LetsEncrypt certificates and stared at the conf files and they all look OK.
I have done "apachectl configtest" and it says "syntax OK".
"netstat -nlp" shows port 80 and 443 are listening, but only for tcp6, not tcp, is this right?
gufw-report shows 443 applies to both TCP and TCP(v6).
/var/log/apache2/error.log is OK.
I have had this working before a recent clean install after a new SSD had a boot sector virus.
apache2 firefox
apache2 firefox
asked 4 mins ago
Dave KimbleDave Kimble
66118
asked 4 mins ago
Dave KimbleDave Kimble
66118
asked 4 mins ago
Dave KimbleDave Kimble
66118
asked 4 mins ago
Dave KimbleDave Kimble
66118
asked 4 mins ago
Dave KimbleDave Kimble
66118
66118
I Also get that error when I mistake http with https...
– Rui F Ribeiro
1 min ago
add a comment |
I Also get that error when I mistake http with https...
– Rui F Ribeiro
1 min ago
I Also get that error when I mistake http with https...
– Rui F Ribeiro
1 min ago
I Also get that error when I mistake http with https...
– Rui F Ribeiro
1 min ago
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1116856%2ffirefox-ssl-error-rx-record-too-long%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1116856%2ffirefox-ssl-error-rx-record-too-long%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
I Also get that error when I mistake http with https...
– Rui F Ribeiro
1 min ago