Shadowsocks causing ERR_SSL_BAD_RECORD_MAC_ALERT on Windows 10
I am a regular Shadowsocks user. Recently when I perform certain actions, all my browsers stop to display the page for me, and the action is not done. For example, while I can browse and comment on posts on Stack Exchange, I cannot ask new questions or submit new answers, unless I turn off Shadowsocks. Some authorization also fails, for example I can't log in to GitHub, and even after logging in, I cannot use GitHub OAuth to authorize other services, but I can browse code as normal. I also cannot open new issues or PRs, or add comments or upload images.
It seems like many "write" actions gets this error while "read" don't.
In Google Chrome I frequently see ERR_SSL_BAD_RECORD_MAC_ALERT on errored pages and I think this is the exact error across all problems I'm having.
I Googled that keyword and found many solutions, and I tried some of them, but to no avail.
- I set the MTU of my current network adapter to 1400 (was 1500) with
netsh interface ipv4 set ......and rebooted - I unchecked "TLS 1.0" and "TLS 1.1" in IE settings, leaving only "SSL 3.0" and "TLS 1.2" checked (there's no option for "SSL 2.0")
- Cleared SSL cache
- Hyper-V is not active on my PC - I am a VMware user
- I have no bridged network.
Another thing is that my network entry is my mobile hotspot, while I have perfectly no issues if I do these things on my phone, even if it's connected to the same server with Shadowsocks for Android.
Quitting Shadowsocks is not an option for a mainland China user, nor is re-installing Windows fresh (don't have time for now). How can I solve this problem?
networking windows-10 proxy socks-proxy
asked Dec 17 '18 at 5:30
iBugiBug
2,45841839
add a comment |
I am a regular Shadowsocks user. Recently when I perform certain actions, all my browsers stop to display the page for me, and the action is not done. For example, while I can browse and comment on posts on Stack Exchange, I cannot ask new questions or submit new answers, unless I turn off Shadowsocks. Some authorization also fails, for example I can't log in to GitHub, and even after logging in, I cannot use GitHub OAuth to authorize other services, but I can browse code as normal. I also cannot open new issues or PRs, or add comments or upload images.
It seems like many "write" actions gets this error while "read" don't.
In Google Chrome I frequently see ERR_SSL_BAD_RECORD_MAC_ALERT on errored pages and I think this is the exact error across all problems I'm having.
I Googled that keyword and found many solutions, and I tried some of them, but to no avail.
- I set the MTU of my current network adapter to 1400 (was 1500) with
netsh interface ipv4 set ......and rebooted - I unchecked "TLS 1.0" and "TLS 1.1" in IE settings, leaving only "SSL 3.0" and "TLS 1.2" checked (there's no option for "SSL 2.0")
- Cleared SSL cache
- Hyper-V is not active on my PC - I am a VMware user
- I have no bridged network.
Another thing is that my network entry is my mobile hotspot, while I have perfectly no issues if I do these things on my phone, even if it's connected to the same server with Shadowsocks for Android.
Quitting Shadowsocks is not an option for a mainland China user, nor is re-installing Windows fresh (don't have time for now). How can I solve this problem?
networking windows-10 proxy socks-proxy
asked Dec 17 '18 at 5:30
iBugiBug
2,45841839
FYI: SSL3 was broken 4 years ago (POODLE) and if you managed make an SSL3 connection it would be badly insecure, but all properly run servers in the world (sadly not nearly all) since at least 2-3 years ago ignore any attempt to negotiate it. TLS1.1 is still safe (though 1.2 is better) and in practice most of the time 1.0 is safe enough although standards like PCI DSS prohibit it. But that doesn't help with your problem.
– dave_thompson_085
Dec 17 '18 at 8:13
add a comment |
I am a regular Shadowsocks user. Recently when I perform certain actions, all my browsers stop to display the page for me, and the action is not done. For example, while I can browse and comment on posts on Stack Exchange, I cannot ask new questions or submit new answers, unless I turn off Shadowsocks. Some authorization also fails, for example I can't log in to GitHub, and even after logging in, I cannot use GitHub OAuth to authorize other services, but I can browse code as normal. I also cannot open new issues or PRs, or add comments or upload images.
It seems like many "write" actions gets this error while "read" don't.
In Google Chrome I frequently see ERR_SSL_BAD_RECORD_MAC_ALERT on errored pages and I think this is the exact error across all problems I'm having.
I Googled that keyword and found many solutions, and I tried some of them, but to no avail.
- I set the MTU of my current network adapter to 1400 (was 1500) with
netsh interface ipv4 set ......and rebooted - I unchecked "TLS 1.0" and "TLS 1.1" in IE settings, leaving only "SSL 3.0" and "TLS 1.2" checked (there's no option for "SSL 2.0")
- Cleared SSL cache
- Hyper-V is not active on my PC - I am a VMware user
- I have no bridged network.
Another thing is that my network entry is my mobile hotspot, while I have perfectly no issues if I do these things on my phone, even if it's connected to the same server with Shadowsocks for Android.
Quitting Shadowsocks is not an option for a mainland China user, nor is re-installing Windows fresh (don't have time for now). How can I solve this problem?
networking windows-10 proxy socks-proxy
asked Dec 17 '18 at 5:30
iBugiBug
2,45841839
I am a regular Shadowsocks user. Recently when I perform certain actions, all my browsers stop to display the page for me, and the action is not done. For example, while I can browse and comment on posts on Stack Exchange, I cannot ask new questions or submit new answers, unless I turn off Shadowsocks. Some authorization also fails, for example I can't log in to GitHub, and even after logging in, I cannot use GitHub OAuth to authorize other services, but I can browse code as normal. I also cannot open new issues or PRs, or add comments or upload images.
It seems like many "write" actions gets this error while "read" don't.
In Google Chrome I frequently see ERR_SSL_BAD_RECORD_MAC_ALERT on errored pages and I think this is the exact error across all problems I'm having.
I Googled that keyword and found many solutions, and I tried some of them, but to no avail.
- I set the MTU of my current network adapter to 1400 (was 1500) with
netsh interface ipv4 set ......and rebooted - I unchecked "TLS 1.0" and "TLS 1.1" in IE settings, leaving only "SSL 3.0" and "TLS 1.2" checked (there's no option for "SSL 2.0")
- Cleared SSL cache
- Hyper-V is not active on my PC - I am a VMware user
- I have no bridged network.
Another thing is that my network entry is my mobile hotspot, while I have perfectly no issues if I do these things on my phone, even if it's connected to the same server with Shadowsocks for Android.
Quitting Shadowsocks is not an option for a mainland China user, nor is re-installing Windows fresh (don't have time for now). How can I solve this problem?
networking windows-10 proxy socks-proxy
networking windows-10 proxy socks-proxy
asked Dec 17 '18 at 5:30
iBugiBug
2,45841839
asked Dec 17 '18 at 5:30
iBugiBug
2,45841839
asked Dec 17 '18 at 5:30
iBugiBug
2,45841839
asked Dec 17 '18 at 5:30
iBugiBug
2,45841839
asked Dec 17 '18 at 5:30
iBugiBug
2,45841839
2,45841839
FYI: SSL3 was broken 4 years ago (POODLE) and if you managed make an SSL3 connection it would be badly insecure, but all properly run servers in the world (sadly not nearly all) since at least 2-3 years ago ignore any attempt to negotiate it. TLS1.1 is still safe (though 1.2 is better) and in practice most of the time 1.0 is safe enough although standards like PCI DSS prohibit it. But that doesn't help with your problem.
– dave_thompson_085
Dec 17 '18 at 8:13
add a comment |
FYI: SSL3 was broken 4 years ago (POODLE) and if you managed make an SSL3 connection it would be badly insecure, but all properly run servers in the world (sadly not nearly all) since at least 2-3 years ago ignore any attempt to negotiate it. TLS1.1 is still safe (though 1.2 is better) and in practice most of the time 1.0 is safe enough although standards like PCI DSS prohibit it. But that doesn't help with your problem.
– dave_thompson_085
Dec 17 '18 at 8:13
FYI: SSL3 was broken 4 years ago (POODLE) and if you managed make an SSL3 connection it would be badly insecure, but all properly run servers in the world (sadly not nearly all) since at least 2-3 years ago ignore any attempt to negotiate it. TLS1.1 is still safe (though 1.2 is better) and in practice most of the time 1.0 is safe enough although standards like PCI DSS prohibit it. But that doesn't help with your problem.
– dave_thompson_085
Dec 17 '18 at 8:13
FYI: SSL3 was broken 4 years ago (POODLE) and if you managed make an SSL3 connection it would be badly insecure, but all properly run servers in the world (sadly not nearly all) since at least 2-3 years ago ignore any attempt to negotiate it. TLS1.1 is still safe (though 1.2 is better) and in practice most of the time 1.0 is safe enough although standards like PCI DSS prohibit it. But that doesn't help with your problem.
– dave_thompson_085
Dec 17 '18 at 8:13
add a comment |
1 Answer
1
active
oldest
votes
After a few hours of re-installing Windows and various stuff, I finally found out that this is a driver issue.
TL;DR If you are a MSI laptop user and encounter this issue, please update your Killer network adapter driver. You can find latest drivers here.
I was looking into another issue when I accidentally found the solution.
I re-installed Windows fresh a few days ago, installed a few "basic software" like Office and WinRAR, as well as all the drivers downloaded from MSI's official website. I soon noticed that it was ridiculous for a freshly-installed Windows 10 to eat up 5.5 GB of RAM at boot, but no suspicious program was running.
Later I spared some time for experiments. I set aside a partition and installed Windows fresh again, carefully watching RAM usage when installing every single piece of software. It didn't took me long to spot that during the "install driver" phase in the installation of Killer Network Suite, the RAM usage suddenly went from 1.6 GB to 3.4 GB.
I then searched for killer driver too much ram and found this thread. It said disabling "Windows Network Data Usage Monitor Driver" would help, but it was already disabled on my laptop. So I just went on and updated my driver, enjoying the fix for the memory leak.
Later I found this page which mentions some network error related to Killer drivers. I then verified that my SSL error was no longer there, so I considered that it was fixed by the driver update.
answered Dec 17 '18 at 13:39
iBugiBug
2,45841839
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
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%2fsuperuser.com%2fquestions%2f1385145%2fshadowsocks-causing-err-ssl-bad-record-mac-alert-on-windows-10%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
After a few hours of re-installing Windows and various stuff, I finally found out that this is a driver issue.
TL;DR If you are a MSI laptop user and encounter this issue, please update your Killer network adapter driver. You can find latest drivers here.
I was looking into another issue when I accidentally found the solution.
I re-installed Windows fresh a few days ago, installed a few "basic software" like Office and WinRAR, as well as all the drivers downloaded from MSI's official website. I soon noticed that it was ridiculous for a freshly-installed Windows 10 to eat up 5.5 GB of RAM at boot, but no suspicious program was running.
Later I spared some time for experiments. I set aside a partition and installed Windows fresh again, carefully watching RAM usage when installing every single piece of software. It didn't took me long to spot that during the "install driver" phase in the installation of Killer Network Suite, the RAM usage suddenly went from 1.6 GB to 3.4 GB.
I then searched for killer driver too much ram and found this thread. It said disabling "Windows Network Data Usage Monitor Driver" would help, but it was already disabled on my laptop. So I just went on and updated my driver, enjoying the fix for the memory leak.
Later I found this page which mentions some network error related to Killer drivers. I then verified that my SSL error was no longer there, so I considered that it was fixed by the driver update.
answered Dec 17 '18 at 13:39
iBugiBug
2,45841839
add a comment |
After a few hours of re-installing Windows and various stuff, I finally found out that this is a driver issue.
TL;DR If you are a MSI laptop user and encounter this issue, please update your Killer network adapter driver. You can find latest drivers here.
I was looking into another issue when I accidentally found the solution.
I re-installed Windows fresh a few days ago, installed a few "basic software" like Office and WinRAR, as well as all the drivers downloaded from MSI's official website. I soon noticed that it was ridiculous for a freshly-installed Windows 10 to eat up 5.5 GB of RAM at boot, but no suspicious program was running.
Later I spared some time for experiments. I set aside a partition and installed Windows fresh again, carefully watching RAM usage when installing every single piece of software. It didn't took me long to spot that during the "install driver" phase in the installation of Killer Network Suite, the RAM usage suddenly went from 1.6 GB to 3.4 GB.
I then searched for killer driver too much ram and found this thread. It said disabling "Windows Network Data Usage Monitor Driver" would help, but it was already disabled on my laptop. So I just went on and updated my driver, enjoying the fix for the memory leak.
Later I found this page which mentions some network error related to Killer drivers. I then verified that my SSL error was no longer there, so I considered that it was fixed by the driver update.
answered Dec 17 '18 at 13:39
iBugiBug
2,45841839
add a comment |
After a few hours of re-installing Windows and various stuff, I finally found out that this is a driver issue.
TL;DR If you are a MSI laptop user and encounter this issue, please update your Killer network adapter driver. You can find latest drivers here.
I was looking into another issue when I accidentally found the solution.
I re-installed Windows fresh a few days ago, installed a few "basic software" like Office and WinRAR, as well as all the drivers downloaded from MSI's official website. I soon noticed that it was ridiculous for a freshly-installed Windows 10 to eat up 5.5 GB of RAM at boot, but no suspicious program was running.
Later I spared some time for experiments. I set aside a partition and installed Windows fresh again, carefully watching RAM usage when installing every single piece of software. It didn't took me long to spot that during the "install driver" phase in the installation of Killer Network Suite, the RAM usage suddenly went from 1.6 GB to 3.4 GB.
I then searched for killer driver too much ram and found this thread. It said disabling "Windows Network Data Usage Monitor Driver" would help, but it was already disabled on my laptop. So I just went on and updated my driver, enjoying the fix for the memory leak.
Later I found this page which mentions some network error related to Killer drivers. I then verified that my SSL error was no longer there, so I considered that it was fixed by the driver update.
answered Dec 17 '18 at 13:39
iBugiBug
2,45841839
After a few hours of re-installing Windows and various stuff, I finally found out that this is a driver issue.
TL;DR If you are a MSI laptop user and encounter this issue, please update your Killer network adapter driver. You can find latest drivers here.
I was looking into another issue when I accidentally found the solution.
I re-installed Windows fresh a few days ago, installed a few "basic software" like Office and WinRAR, as well as all the drivers downloaded from MSI's official website. I soon noticed that it was ridiculous for a freshly-installed Windows 10 to eat up 5.5 GB of RAM at boot, but no suspicious program was running.
Later I spared some time for experiments. I set aside a partition and installed Windows fresh again, carefully watching RAM usage when installing every single piece of software. It didn't took me long to spot that during the "install driver" phase in the installation of Killer Network Suite, the RAM usage suddenly went from 1.6 GB to 3.4 GB.
I then searched for killer driver too much ram and found this thread. It said disabling "Windows Network Data Usage Monitor Driver" would help, but it was already disabled on my laptop. So I just went on and updated my driver, enjoying the fix for the memory leak.
Later I found this page which mentions some network error related to Killer drivers. I then verified that my SSL error was no longer there, so I considered that it was fixed by the driver update.
answered Dec 17 '18 at 13:39
iBugiBug
2,45841839
edited Dec 17 '18 at 14:33
answered Dec 17 '18 at 13:39
iBugiBug
2,45841839
answered Dec 17 '18 at 13:39
iBugiBug
2,45841839
answered Dec 17 '18 at 13:39
iBugiBug
2,45841839
2,45841839
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- 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%2fsuperuser.com%2fquestions%2f1385145%2fshadowsocks-causing-err-ssl-bad-record-mac-alert-on-windows-10%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
FYI: SSL3 was broken 4 years ago (POODLE) and if you managed make an SSL3 connection it would be badly insecure, but all properly run servers in the world (sadly not nearly all) since at least 2-3 years ago ignore any attempt to negotiate it. TLS1.1 is still safe (though 1.2 is better) and in practice most of the time 1.0 is safe enough although standards like PCI DSS prohibit it. But that doesn't help with your problem.
– dave_thompson_085
Dec 17 '18 at 8:13