Looking a little further..
«Privacy Badger was born out of our desire to be able to recommend a single extension that would automatically analyze and block any tracker or ad that violated the principle of user consent; which could function well without any settings, knowledge, or configuration by the user; which is produced by an organization that is unambiguously working for its users rather than for advertisers; and which uses algorithmic methods to decide what is and isn’t tracking.»So not blocking based on connection.
BUT from that description, its based on anything which ‘tracks’ any information.
Yes, this is used primarily by Ads, where the specific add company when you go to say walmarts site, it writes to a cookie on your machine (or collects to their side) that you visited there, and then when you go somewhere else, reads that you went there and shows you walmarts on that site as well, etc.
Its quite possible, for recording and/or keeping past speed test results, location, etc, that its just trying to write a cookie to the machine to store that information. And the program might be blocking it.
I completely understand the need and how/why people due use the blockers. They are a good thing.
But sometime its the SITE thats the problem, even if they are not trying to do something bad
I have seen sites, which will only load like 3 lines of the site then thats it, because of the blockers.
The code is so bad, and because its not loading in the part, it doesnt load the rest
-
Partition Wizard
-
Partition Magic
- How to Fix: A Socket Error Occurred During the Upload Test
By Amanda | Follow |
Last Updated February 23, 2021
If you are facing the “a socket error occurred during the upload test” error, don’t miss this tutorial from MiniTool Partition Wizard. Here, you will learn about several solutions to this problem, and you can try them one by one according to the given instructions.
Recently, many users are reporting that they receive the socket error message while they are trying to run a speed test on the internet connection. In most cases, this error appears while users are using SpeedTest, but it has been also reported to occur on many other online speed test tools.
The complete error message reading:
Upload test error
A socket error occurred during the Upload test. A firewall could be blocking the connection or the server might be having some issues. Please try again later.
The upload test error could be caused by many factors, but you don’t need to worry. Here are some fixes you can have a try.
Fix 1: Enable Connected Devices Platform
The “Connected Devices Platform – Wi-Fi Direct Transport (TCP-Out)” outbound rule is a known factor that can cause the socket error. To solve the problem, you need to make sure it is enabled.
Step 1: Press Windows + S, input control panel, and click the search result to open it.
Step 2: Navigate to System and Security > Windows Defender Firewall and click Advanced settings in the left pane.
Step 3: Click Outbound Rules and find Connected Devices Platform – Wi-Fi Direct Transport (TCP-Out). Double-click it to open its properties.
Step 4: Under the General tab, make sure the Enabled option is checked. Then, click Apply and OK.
After that, restart your computer and check if you can perform the speed test without the socket error message.
Fix 2: Pause OneDrive Syncing
It is reported that the background cloud solution syncing can take up almost all the available bandwidth and thus trigger the “a socket error occurred during the upload test” when you are performing a speed test.
Therefore, you can try pausing the syncing of your cloud solution like OneDrive or Google Drive. As for OneDrive, you can follow the steps below:
Step 1: Right-click the cloud icon associated with OneDirve from the taskbar.
Step 2: Click Pause syncing from the context menu.
Step 3: Select 2 hours from the drop-down options. You don’t need to choose other options to pause it for a longer time, as 2 hours is enough for you to repeat and complete the speed test.
Fix 3: Add an Exception for SpeedTest in Your Antivirus
In some cases, your security software like Avast and the built-in Windows Defender may over-protect your computer. As a result, they may regard the speed test as suspicious activity and block the communication between your PC and SpeedTest server, ending up with this annoying upload test error.
To fix the problem, you can add an exception for SpeedTest in the installed antivirus. Take Avast as an example, you just need to:
Step 1: Open your Avast client, click Menu on the top right corner, and choose Settings.
Step 2: In the General section, switch to Exceptions and click ADD EXCEPTION.
Step 3: In the pop-up window, type the URL of SpeedTest https://www.speedtest.net/ and click ADD EXCEPTION to save changes.
Fix 4: Disable or Uninstall Your Third-Party Antivirus
If adding an exception in antivirus doesn’t solve the socket error, perhaps the problem lies in your security application itself and you might need to disable or uninstall it.
To disable avast, you can simply right-click its taskbar icon and choose Avast shields control. Then, choose an option to disable its read-time protection as your needs. To disable the built-in Windows Defender Antivirus, you can refer to this article.
Can you run the speed test smoothly now? If not, you might need to uninstall the third-party security software or try another online speed test tool.
About The Author
Position: Columnist
Amanda has been working as English editor for the MiniTool team since she was graduated from university. She enjoys sharing effective solutions and her own experience to help readers fix various issues with computers, dedicated to make their tech life easier and more enjoyable.
She has published many articles, covering fields of data recovery, partition management, disk backup, and etc. In order to provide more useful tips and information, she is still committed to expand her technical knowledge.
Some Windows users are trying to run a speed test on their Internet connection, but every online tool that they try to use will end up displaying the ‘Socket Error‘ message. In most cases, this issue is reported to occur with SpeedTest.
As it turns out, one of the most common instances that will produce the Socket Error is an outbound rule (Connected Devices Platform – Wi-Fi Direct Transport (TCP-Out)) belonging to Windows Firewall. If it’s disabled, you AV might not allow connections with speed test utilities. In this case, you can resolve the problem by enabling the outbound rule from the Advanced settings of the Windows Firewall.
But if you’re using a 3rd party AV or Firewall, you might need to whitelist the domain of the SpeedTest tool that you’re using in order to allow the test to complete. Additionally, you should look to disable the real-time protection or uninstall the 3rd party suite altogether.
However, cloud solutions like Onedrive or Google Drive are also reported to trigger the ‘Socket Error‘. If this scenario is applicable, disable the real-time syncing feature of your cloud solution and see if the issue is resolved.
If all else fails, you should consider using a different speed testing tool that is more permissive with your Internet connection.
Method 1: Enabling Connected Device Platform rule in Windows Firewall
As it turns out, the ‘socket error’ when running an Internet speed test with your browser can be caused by your firewall – even if you’re using the built-in firewall (Windows Firewall). This scenario is most encountered on a Wi-Fi connection.
According to some affected users, this particular issue can occur due to an Outbound rule called ‘Connected Devices Platform – Wi-Fi Direct Transport (TCP-Out)‘.
Some affected users have managed to fix the issue by accessing the Advanced Security suites of Windows Firewall and enabling the problematic outbound rule. But keep in mind that the outbound rule that needs to be enabled will be different if you’re encountering the issue with an ethernet connection.
Here’s a quick step by step guide that will allow you to access the Advanced built-in Firewall settings and enabling the correct outbound rule:
- Press Windows key + R to open up a Run dialog box. Next, type ‘firewall.cpl’ inside the text box and press Enter to open up the Windows Firewall settings window.
- Once you’re inside the Windows Defender Firewall settings, click on the Advanced settings menu from the left-hand side menu bar.
- After you manage to land inside the Windows Defender Firewall and Advanced Security, click on Outbound Rules from the menu on the left.
- With the Outbound Rules menu selected, move down to the right-hand section and scroll down through the list of available Outbound Rules and locate ‘Connected Devices Platform – Wi-Fi Direct Transport (TCP-OUT)‘. Once you see it, double-click on it.
Note: If you’re encountering the issue with an ethernet connection, access the Connected Devices Platform (TCP-Out) outbound rule instead. - Inside the Properties screen of the outbound rule that you want to modify, select the General tab from the menu at the top, then ensure that the box associated with Enabled is checked.
- Click on Apply to save the changes, then close every window and restart your computer.
- Once the next startup is complete, repeat the speed test once again and see if the issue is now resolved.
Enabling the problematic outbound rule
In case the same ‘Socket Error‘ is still occurring, move down to the next potential fix below.
Method 2: Pause OneDrive or Drive Syncing (if applicable)
If you’re using OneDrive or the desktop version of Google Drive as the primary cloud solution, keep in mind that these two can be huge Internet bandwidth hoggers if you’re they are actively syncing files while you are trying to run a speed test.
Several affected users have reported that they got this error consistently until they realized that their cloud solution (Onedrive or Google drive) was uploading files in the background, effectively taking up all the available bandwidth.
If this scenario is applicable, you can fix this issue by pausing the syncing sequence of Ondrive or Google Drive – depending on the tool that you’re using.
Since we don’t discriminate, we created two separate guides that will help you disable active syncing regardless of the cloud application that you’re using.
Pausing Active Syncing on OneDrive
- Right-click on the taskbar icon associated with OneDrive (an icon resembling a cloud).
- Next, from the OneDrive context menu, click on More, select Pause Syncing and select 2 Hours from the list of available options.
Pausing Syncing on OneDrive Note: Two hours is more than enough to complete the speed test – no need to stop the active syncing feature indefinitely.
- Once the OneDrive syncing feature is disabled, repeat the speed test and see if the ‘Socket Error‘ has been resolved.
Pausing Active Syncing on Google Drive
- Go to your taskbar and look for the icon associated with Google Drive.
- If you see that the utility is actively syncing files, click on the action button (top-right corner) and click on Pause from the newly appeared cotext menu.
Pausing Google Drive Sync - Now that the active syncing is disabled, repeat the speed test and see if the problem is resolved.
- Once the operation is completed, return to the same Google Drive menu and click on Resume to reestablish real-time syncing.
In case you’ve already done this with no success or this scenario was not applicable, move down to the next potential fix below.
Method 3: Whitelist Speedtest domain (if using 3rd party AV)
As it turns out, there are some overprotective suites that will simply flag the speed test as a suspicious activity – which will end up triggering the ‘Socket Error‘. Avast Antivirus, Kaspersky and Comodo AV are commonly signaled out for blocking communications between computer and Speedtest server.
If this scenario is applicable, you should be able to resolve the issue by whitelisting the domain in order to allow the speed test to run. But keep in mind that this operation will be different depending on the AV suite that you’re using.
In Avast, you can establish a whitelisting rule by going to Settings > General > Exclusions > URL. Once you get there, simply paste ‘https://www.speedtest.net/‘ and save the modifications.
Note: Keep in mind that these steps will be different depending across multiple 3rd party suites.
Additionally, you can simply disable the real-time protection while you perform the speed test. In most cases, you can do this directly from the taskbar menu. Simply right-click on the icon associated with your AV and look for an option that will disable the real-time protection.
In case the same problem is persisting and you’re using a 3rd party security suite, move down to the next potential fix below.
Method 4: Uninstalling 3rd party suite (along with remnant files)
If the method above didn’t resolve the issue but you are using a 3rd party suite that you suspect might be causing this problem, the only way to test the theory out is to uninstall the 3rd party suite and ensure that you’re not leaving behind any leftover files that might still cause the same type of behavior.
In case you suspect that a false positive triggered by your 3rd party AV is causing the issue, here’s a quick step-by-step guide on uninstalling the 3rd party suite or firewall and ensuring that you’re not leaving behind any remnant files that might still produce the error:
- Press Windows key + R to open up a Run dialog box. Next, type ‘appwiz.cpl’ and press Enter to open up the Programs and Features menu.
Type appwiz.cpl and Press Enter to Open Installed Programs List - Once you manage to get inside the Programs and Features menu, scroll down through the list of installed applications. Do so until you locate the 3rd party A/V or firewall that you suspect might be causing the issue.
- When you see it, right-click on it and choose Uninstall from the newly appeared context menu.
Uninstalling Avast Firewall - Inside the uninstallation wizard, follow the on-screen prompts to complete the process of uninstalling the 3rd party AV app.
- Once the uninstallation is complete, restart your computer and follow this article (here) once the next startup is complete in order to ensure that you also remove any leftover files that might still produce this type of behavior.
- Run the speed test again and see if the issue is still resolved.
In case the same problem is still occurring, move down to the next potential fix below.
Method 5: Using a Different Testing Tool
If none of the methods below have allowed you to fix the ‘Socket Error’ and perform a SpeedTest, it’s time to consider the alternatives. Keep in mind that SpeedTest.net is not the only reliable tools that will allow you to test your Internet connection.
We’ve created a list with 5 Alternatives that you can use in case Speedtest.Net is consistently showing the same error message:
- Fast.com
- Xfinity Speed Test
- Internet Health Test
- Cox Internet Speed Test
- SpeedOf.Me
Feel free to use any of the alternatives featured above. They are just as reliable as the most popular option (SpeedTest.Net) and will most likely not trigger the same ‘Socket Error’.
Сообщения без ответов | Активные темы
Автор | Сообщение | |||
---|---|---|---|---|
Заголовок сообщения: Re: Вопросы по работе сети
|
||||
|
Добрых выходных! Вроде все нормализовалось |
|||
Вернуться к началу |
|
|||
emzone |
Заголовок сообщения: Re: Вопросы по работе сети
|
|
Горького 62 в 10:12 пропал интернет. Даже до форума не достучаться. |
Вернуться к началу |
|
Джонни |
Заголовок сообщения: Re: Вопросы по работе сети
|
|
emzone писал(а): Горького 62 в 10:12 пропал интернет. Даже до форума не достучаться. Добрый день. |
Вернуться к началу |
|
dizzel |
Заголовок сообщения: Re: Вопросы по работе сети
|
|
Все ли в порядке на Ленина 110? |
Вернуться к началу |
|
dizzel |
Заголовок сообщения: Re: Вопросы по работе сети
|
|
Извините, кто-нибудь из работников Макснета может это как-то прокомментировать? Все ли в порядке с моим интернетом? |
Вернуться к началу |
|
Джонни |
Заголовок сообщения: Re: Вопросы по работе сети
|
|
dizzel писал(а): Извините, кто-нибудь из работников Макснета может это как-то прокомментировать? Все ли в порядке с моим интернетом? Добрый день. |
Вернуться к началу |
|
dizzel |
Заголовок сообщения: Re: Вопросы по работе сети
|
|
Стал копать дальше и выяснил, что не смотря на ошибки проверки скорости интернета на телефоне те же видео с него прекрасно заливаются на ютуб. Значит все-таки проблема у меня, решил почистить комп от возможного мусора (хотя за этим я пристально слежу и не допускаю установку ненужного и непроверенного софта) с помощью ADWcleaner. Нашлось несколько подозрительных ключей в реестре, после их удаления и перезагрузки компа все пришло в норму. |
Вернуться к началу |
|
Джонни |
Заголовок сообщения: Re: Вопросы по работе сети
|
|
dizzel писал(а): Стал копать дальше и выяснил, что не смотря на ошибки проверки скорости интернета на телефоне те же видео с него прекрасно заливаются на ютуб. Значит все-таки проблема у меня, решил почистить комп от возможного мусора (хотя за этим я пристально слежу и не допускаю установку ненужного и непроверенного софта) с помощью ADWcleaner. Нашлось несколько подозрительных ключей в реестре, после их удаления и перезагрузки компа все пришло в норму. Всегда пожалуйста , рад, что вы решили эту проблему. |
Вернуться к началу |
|
legawrique |
Заголовок сообщения: Re: Вопросы по работе сети
|
|
Привет, что с интернетом, с утра отключался на минут 15 полностью (даже форум), сейчас опять, но хоть форум работает. Ремонт или авария? Спасибо) Курчатова 43. UPD: Только отписал — всё снова заработало, не знаю как удалить сообщение. |
Вернуться к началу |
|
Джонни |
Заголовок сообщения: Re: Вопросы по работе сети
|
|
legawrique писал(а): Привет, что с интернетом, с утра отключался на минут 15 полностью (даже форум), сейчас опять, но хоть форум работает. Ремонт или авария? Спасибо) Курчатова 43. UPD: Только отписал — всё снова заработало, не знаю как удалить сообщение. Добрый день. |
Вернуться к началу |
|
legawrique |
Заголовок сообщения: Re: Вопросы по работе сети
|
|
Ок, спасибо за информацию! |
Вернуться к началу |
|
darthgrinder |
Заголовок сообщения: Re: Вопросы по работе сети
|
|
Почему заблокированы IP? http://blocklist.rkn.gov.ru/ и http://eais.rkn.gov.ru/ , хотя уже не работало. tracert 18.196.185.133 Трассировка маршрута к ec2-18-196-185-133.eu-central-1.compute.amazonaws.com [18.196.185.133] 1 2 ms 1 ms 1 ms KEENETIC_GIGA [192.168.1.1] tracert 18.195.21.227 Трассировка маршрута к ec2-18-195-21-227.eu-central-1.compute.amazonaws.com [18.195.21.227] 1 <1 мс <1 мс <1 мс KEENETIC_GIGA [192.168.1.1] |
Вернуться к началу |
|
Джонни |
Заголовок сообщения: Re: Вопросы по работе сети
|
|
darthgrinder писал(а): Почему заблокированы IP? http://blocklist.rkn.gov.ru/ и http://eais.rkn.gov.ru/ , хотя уже не работало. tracert 18.196.185.133 Трассировка маршрута к ec2-18-196-185-133.eu-central-1.compute.amazonaws.com [18.196.185.133] 1 2 ms 1 ms 1 ms KEENETIC_GIGA [192.168.1.1] tracert 18.195.21.227 Трассировка маршрута к ec2-18-195-21-227.eu-central-1.compute.amazonaws.com [18.195.21.227] 1 <1 мс <1 мс <1 мс KEENETIC_GIGA [192.168.1.1] Добрый день. Код: Подсети: По этой же причине не работает Viber. В данный момент портал выгрузок реестра РКН находится под ddos-атакой, в результате чего даже Реестр с трудом получается. Возможно в текущих выгрузках какие то подсети из вышеперечисленных уже убрали, но пока реестр не удастся получить, сервер фильтрации не уберет их из блока, к сожалению… |
Вернуться к началу |
|
darthgrinder |
Заголовок сообщения: Re: Вопросы по работе сети
|
|
Джонни писал(а): Код: Подсети: По этой же причине не работает Viber. В данный момент портал выгрузок реестра РКН находится под ddos-атакой, в результате чего даже Реестр с трудом получается. Возможно в текущих выгрузках какие то подсети из вышеперечисленных уже убрали, но пока реестр не удастся получить, сервер фильтрации не уберет их из блока, к сожалению… ОК, но 18.195.21.227 как туда попал? |
Вернуться к началу |
|
Джонни |
Заголовок сообщения: Re: Вопросы по работе сети
|
|
darthgrinder писал(а): Джонни писал(а): Код: Подсети: По этой же причине не работает Viber. В данный момент портал выгрузок реестра РКН находится под ddos-атакой, в результате чего даже Реестр с трудом получается. Возможно в текущих выгрузках какие то подсети из вышеперечисленных уже убрали, но пока реестр не удастся получить, сервер фильтрации не уберет их из блока, к сожалению… ОК, но 18.195.21.227 как туда попал? Вторая строка в моем списке: 18.194.0.0/15 |
Вернуться к началу |
|
Кто сейчас на конференции |
Сейчас этот форум просматривают: нет зарегистрированных пользователей и гости: 2 |
Вы не можете начинать темы Вы не можете отвечать на сообщения Вы не можете редактировать свои сообщения Вы не можете удалять свои сообщения |