Error errno 10013

I'm trying to create a custom TCP stack using Python 2.6.5 on Windows 7 to serve valid http page requests on port 80 locally. But, I've run into a snag with what seems like Windows 7 tightened up

I’m trying to create a custom TCP stack using Python 2.6.5 on Windows 7 to serve valid http page requests on port 80 locally. But, I’ve run into a snag with what seems like Windows 7 tightened up security. This code worked on Vista.

Here’s my sample code:

import SocketServer
import struct

class MyTCPHandler(SocketServer.BaseRequestHandler):
    def handle(self):
        headerText = """HTTP/1.0 200 OK
                        Date: Fri, 31 Dec 1999 23:59:59 GMT
                        Content-Type: text/html
                        Content-Length: 1354"""
        bodyText = "<html><body>some page</body></html>"
        self.request.send(headerText + "n" + bodyText)

if __name__ == "__main__":
    HOST, PORT = "localhost", 80
    server = SocketServer.TCPServer((HOST, PORT), MyTCPHandler)
    server.serve_forever()

C:python>python TestServer.py
Traceback (most recent call last):
File «TestServer.py», line 19, in

server = SocketServer.TCPServer((HOST, PORT),
MyTCPHandler) File
«C:Python26libSocketServer.py»,
line 400, in init
self.server_bind() File «C:Python26libSocketServer.py»,
line 411, in server_bind
self.socket.bind(self.server_address)
File «», line 1, in bind

socket.error: [Errno 10013] An attempt
was made to access a socket in a way
forbidden by its access permissions

How exactly do I get this to work on Windows 7?

[Edit on 5/5/2010 @ 2344 PDT] This answer explains that the error is caused by the need for elevated / superuser privileges when accessing ports lower than 1024. I’m going to try using a higher port number to see if that works. However, I still would like to know why my local admin account can’t access port 80.

Источник

Содержание

  1. Ошибка 10013 (WSAEACCES) возвращается при сбое второй привязки к исключенным портам в Windows
  2. Симптомы
  3. Причина
  4. Обходной путь
  5. Состояние
  6. Руководство по быстрому исправлению ошибки 10013
  7. Ошибка 10013 — Что это?
  8. Решения
  9. Причины ошибок
  10. Дополнительная информация и ручной ремонт
  11. 1. Отключить межсетевой экран
  12. 2. Отключите антивирусное программное обеспечение
  13. 3. Обновление драйверов
  14. 4. Проблемы с реестром
  15. How to Fix Socket Error 10013
  16. Socket Error 10013 — What is it?
  17. Solution
  18. Error Causes
  19. Further Information and Manual Repair
  20. Method 1 — Turn off Firewall
  21. Method 2 — Check the Permissions section of the Firewall Program
  22. Method 3 — Update Drivers
  23. Method 4 — Scan for Viruses and Malware
  24. Advanced System Repair Pro
  25. Share this article:
  26. You might also like
  27. When you are in the PowerShell window, enter the command below:
  28. Missing Dciman32.dll Error – What is it?
  29. Solution
  30. Error Causes
  31. Further Information and Manual Repair
  32. Method 1 — Restore Dciman32 dll file Back on your PC
  33. Method 2 — Update Drivers for Hardware Devices
  34. Method 3 — Reinstall the Program that Uses Dciman32.dll File
  35. Method 4 — Scan your PC for Registry Issues and Viruses
  36. Restoro
  37. Option 1 – Delete the folder where msrtn32.exe is located
  38. Option 2 – Try scanning your computer using Windows Defender
  39. Iskur Specifications
  40. Features
  41. Conclusion
  42. About Browser Hijackers
  43. Symptoms of browser hijack
  44. How they infect computer systems
  45. The best ways to remove a browser hijacker
  46. Virus Blocking Internet And All Antivirus Software? Do This!
  47. Install antivirus in Safe Mode with Networking
  48. Obtain the anti-malware software in a different internet browser
  49. Run antivirus from a pen drive
  50. Protect Your PC & Privacy With SafeBytes Anti-Malware
  51. Technical Details and Manual Removal (Advanced Users)
  52. The following files, folders, and registry entries are created or modified by SpeedItUp
  53. What is Error code 8007002c?
  54. Solution
  55. Error Causes
  56. Further Information and Manual Repair
  57. Method One: Force Windows Update
  58. Method Two: Diagnose RAM Issues
  59. Method Three: Use Selective Startup
  60. Adobe Stock free collection
  61. Unsplash
  62. Pixabay
  63. Pexels
  64. Pikwizard Stock
  65. Gratisography Stock photos
  66. Conclusion
  67. Check your game page and your DirectX
  68. Update or reinstall GPU drivers
  69. Set custom scaling to 100
  70. Delete registry key
  71. Use dedicated error fix tool
  72. Error Code 0x8007007e – What is it?
  73. Solution
  74. Error Causes
  75. Further Information and Manual Repair
  76. Method One: System File Checker
  77. Method Two: Run System Restore Tool
  78. Method Three: Download Automated Software

Ошибка 10013 (WSAEACCES) возвращается при сбое второй привязки к исключенным портам в Windows

Эта статья поможет устранить проблему, из-за которой невозможно снова привязать исключенный порт, даже если SO_REUSEADDR задан.

Применяется к: Windows Server 2012 R2
Исходный номер базы знаний: 3039044

Симптомы

Предположим, что вы исключили порт, выполнив следующую команду на компьютере под управлением Windows Server 2012 R2, Windows Server 2012 или Windows Server 2008 R2:

Кроме того, предположим, что вы привязываете SO_REUSEADDR к определенному TCP-порту на компьютере. In this situation, when you try to bind the SO_REUSEADDR socket to the TCP port again, the bind fails, and you receive the «WSAEACCES (10013)» error.

Таким образом, если вы используете приложение, которое вызывает две привязки в Windows Server 2012 R2, Windows Server 2012 или Windows Server 2008 R2, оно не может работать правильно.

  • По умолчанию Windows Server 2008 R2 не может использовать команду netsh для исключения портов. Однако после применения исправлений 2665809 операционная система поддерживает эту функцию.
  • Эта проблема не возникает в Windows Server 2008 или Windows Server 2003.

Причина

Эта проблема возникает из-за проблемы в tcpip.sys драйвере. В частности, флаг REUSE был перезаписан флагом RESERVED, когда драйвер tcpip.sys привязывает исключенный порт.

Обходной путь

Чтобы обойти эту проблему, воспользуйтесь одним из описанных ниже методов.

  • Используйте порт, не включенный в диапазон динамических портов по умолчанию (от 49 152 до 65 535), netsh и не указывайте порт как исключенный порт, выполнив команду.
  • Используйте функции CreatePersistentTcpPortReservation и LookupPersistentTcpPortReservation , чтобы зарезервировать порт.

Состояние

Данное поведение является подтвержденной ошибкой продуктов Майкрософт, перечисленных в разделе «Применимо к».

Источник

Руководство по быстрому исправлению ошибки 10013

Ошибка 10013 — Что это?

Ошибка 10013 — это ошибка ПК с сокетом Windows. Ошибка сокета 10013 возникает, когда попытка доступа к серверу запрещена. Это указывает на то, что необходимое соединение сокета отклонено, что также означает, что порт заблокирован или недоступен.

Решения

Причины ошибок

Ошибка сокета 10013 может возникнуть по нескольким причинам:

  • Антивирус или брандмауэр
  • Несовместимые драйверы
  • Повреждение реестра
  • Неверно сконфигурированные файлы

Дополнительная информация и ручной ремонт

Чтобы устранить ошибку сокета 10013 на вашем компьютере, вот несколько способов, которые вы можете попробовать:

1. Отключить межсетевой экран

Чтобы решить эту проблему на вашем компьютере, вам может потребоваться временно отключить брандмауэр. Иногда брандмауэр может помешать вам подключиться к серверу. Попробуйте сделать это; это наиболее вероятно, чтобы устранить ошибку. Если брандмауэр является причиной отказа в доступе, его отключение наверняка поможет.

2. Отключите антивирусное программное обеспечение

Если отключение брандмауэра не решает проблему, попробуйте временно отключить антивирусное программное обеспечение. Если ошибка не исчезла, попробуйте другие решения, перечисленные ниже.

3. Обновление драйверов

Несовместимые драйверы также могут быть причиной отказа в доступе к серверу.

Возможно, ваш сервер больше не использует драйверы, установленные на вашем ПК, поэтому вы можете не получить разрешение на доступ к нему. Если это причина, то лучший способ устранить ее — обновить драйверы. Чтобы узнать о новых драйверах, посетите веб-сайт производителя программного обеспечения для новых драйверов, а затем загрузите их на свой компьютер.

4. Проблемы с реестром

Иногда основной причиной ошибки могут быть проблемы с реестром и неправильно настроенные файлы.

Если вы не удалите ненужные и устаревшие файлы из своих систем, такие как ненужные файлы, файлы cookie, история Интернета, временные файлы и другие файлы с вашего компьютера, это может повредить реестр и неправильно настроенные файлы, что приведет к ошибке сокета 10013 на вашем система.

Чтобы решить проблемы с реестром и восстановить компьютер, загрузите Restoro. Это продвинутая, простая в использовании и высокофункциональная программа для ремонта ПК, в которую встроено множество утилит, включая мощный очиститель реестра. Он развернут с помощью интуитивно понятного алгоритма, который сканирует и обнаруживает все проблемы реестра за секунды.

Он удаляет все ненужные и устаревшие файлы, хранящиеся на вашем компьютере, перегружая ваш реестра. Этот очиститель реестра ремонтирует поврежденные и неправильно настроенные файлы и восстанавливает реестр, тем самым сразу же устраняя ошибку сокета 10013 в вашей системе.

Он имеет простую навигацию и удобный интерфейс, который позволяет пользователям любого уровня легко работать и использовать его с максимальной выгодой. Кроме того, его можно установить на любой ПК с Windows.

Restoro совместим со всеми версиями Windows.

В дополнение к этому, он также включает несколько других дополнительных функций, таких как антивирус, оптимизатор системы, а также элементы управления Active X и сканер классов. Эти утилиты можно использовать для устранения множества других ошибок, связанных с ПК.

Открыть чтобы загрузить Restoro сегодня и сразу же устранить ошибку сокета 10013 на вашем компьютере.

Источник

How to Fix Socket Error 10013

Socket Error 10013 — What is it?

Socket error 10013 is an error code that often pops on the screen when you try to access the server. This error code restricts your permission to access. It shows that your permission request was denied.

The error message is displayed in the following format:

“Socket.error: [Errno 10013] an attempt was made to access a socket in a way forbidden by its access permissions”

Solution

Error Causes

Narrowing down a particular reason for the cause of socket error 10013 is difficult, typically because this error code can be generated due to several reasons. Here are some of the common reasons for its occurrence on your PC:

  • High-security set up- Firewall or an antivirus program
  • Too many functions tied to the same driver confuses the socket
  • Outdated drivers
  • Malware

The good news is that the socket error 10013 is not fatal. However, it is advisable to fix and resolve the issue to avoid inconvenience.

Further Information and Manual Repair

Here are some of the best, quickest and easiest methods to work around the problem and resolve socket error 10013 without any hassle or delay.

Method 1 — Turn off Firewall

Believe it or not, a high level of internet security measures like Firewalls and anti-virus programs are a common cause of socket error 10013.

Firewalls are made to protect a computer from harmful connections but sometimes it may also restrict server connections, considering them as a threat to your system security.

Due to this, permission access is adamantly denied. To resolve this issue on your PC, the best way to go about is to turn off your Firewall or any other anti-virus programs installed on your system.

Once you turn off these programs, try accessing the server again. The majority of the time the issue is resolved by carrying this step. Nonetheless, if the error still persists, try the methods given below.

Method 2 — Check the Permissions section of the Firewall Program

Another way to resolve this is to check the permission section of the Firewall program and check for the server. If the server is not listed, contact the Internet Service Provider (ISP) and ask for help in adding the server to the list.

Method 3 — Update Drivers

The outdated driver may sometimes be the reason for the socket error 10013. The socket may no longer use the drivers installed on your PC which is why permission to access the server is not granted.

When this is the reason, try updating the drivers to resolve. For new drivers, visit the software manufacturers’ website, download, and install.

Method 4 — Scan for Viruses and Malware

Another alternative is to scan for viruses and malware. Sometimes the cause for the error is a viral infection. Therefore, remove them to resolve.

The best way is to download Restoro. This is a user-friendly and next-generation PC Fixer embedded with 6 scanners including a powerful anti-virus. It scans your entire PC and removes all types of viruses including malware, adware, spyware, and Trojans in seconds.

Click here to download Restoro.

Advanced System Repair Pro

You might also like

When you are in the PowerShell window, enter the command below:

Missing Dciman32.dll Error – What is it?

Solution

Error Causes

Further Information and Manual Repair

Method 1 — Restore Dciman32 dll file Back on your PC

Method 2 — Update Drivers for Hardware Devices

Method 3 — Reinstall the Program that Uses Dciman32.dll File

Method 4 — Scan your PC for Registry Issues and Viruses

Restoro

C:/Program Files(x86)msrtn32

Option 1 – Delete the folder where msrtn32.exe is located

Option 2 – Try scanning your computer using Windows Defender

Iskur Specifications

Features

Conclusion

SpeedItUp is a potentially unwanted application made by MicroSmarts LLC. The program claims to optimize RAM, clean the registry, and boost internet connection speed. It is designed to speed up your computer by removing some background processes. While not malicious itself, SpeedItUp Free and its variations are often installed via third-party installer bundles, causing many users to unwittingly install the program. Aliases of the program include CheckMeUp, SpeedCheck, SpeedChecker, SpeedItUp Free, Speeditup-Checkup, and Speeditup-Nova. While intended to speed up the performance, its background processes and startup tasks may actually slow PCs down in some cases. Some versions of SpeedItUp also include a browser extension.

About Browser Hijackers

Symptoms of browser hijack

How they infect computer systems

The best ways to remove a browser hijacker

Virus Blocking Internet And All Antivirus Software? Do This!

Install antivirus in Safe Mode with Networking

Obtain the anti-malware software in a different internet browser

Run antivirus from a pen drive

Protect Your PC & Privacy With SafeBytes Anti-Malware

Technical Details and Manual Removal (Advanced Users)

The following files, folders, and registry entries are created or modified by SpeedItUp

What is Error code 8007002c?

Users when upgrading to Windows 10 operating system from Windows 8/8.1 or Windows 7, often encounter error code 8007002c. This error occurs when there’s an attempt made in performing an overall clean boot procedure. During the installation process, it will reach a certain maximum limit, for instance, 75%, and then reverts to its original state. Sometimes, after installation, users will encounter a black screen issue and there is no cursor visible.

Solution

Error Causes

Misconfigured system files that create registry errors within your operating system normally cause error code 8007002c in Windows 10. This registry error happens when there are new programs being installed over old ones without the old programs uninstalled entirely. Another possible cause could be from some malicious software like spyware, adware, and viruses.

Further Information and Manual Repair

Caution: The following steps are complicated. The risk of being in a no-boot situation or data loss might be encountered. It would be best to be supervised by an experienced user, especially in using the command line.

In order to fix Error code 8007002c occurring in Windows 10 upgrade, you can follow this step-by-step manual repair method. Once the repair method is correctly executed, users will most likely quickly resolve issues such as the Error code 8007002c and be able to upgrade to Windows 10 operating system smoothly.

However, in such cases where there are complex instructions and thus need an expert, seek help from a Windows professional. You may also want to consider making use of an automated tool whenever needed.

There are several ways to fix Error code 8007002c, but here are the most effective and efficient methods:

Method One: Force Windows Update

To be able to download and install the necessary updates, you may use the force Windows Update tool. See below for the steps:

  1. Browse to C:WindowsSoftwareDistributionDownload. Afterward, delete all the files found in that folder.
  2. Press Windows key + X then click on the Command Prompt (Admin). Type exe /updatenow once the Command Prompt window appears then press Enter.
  3. Open the Control Panel. Select Windows Update. At this point, Windows 10 should now start downloading.
  4. Press again on Windows key + X to open the Command Prompt window. In the Command Prompt, Type or Copy and Paste the following commands one at a time:

NOTE: Don’t forget to hit Enter after every command.

Dism /Online /Cleanup-Image /CheckHealth

Dism /Online /Cleanup-Image /ScanHealth Dism /Online /Cleanup-Image /RestoreHealth

  1. Input a machine name for your computer. Make sure to use a simple name, having at least 8 characters.

Here’s how you can input a machine name:

  • Click on Start and then right-click on Computer. Afterward, select For users with Windows 8 operating system, press on Windows key + X then click on System.
  • Click on Change settings under the Computer name, domain, and workgroup settings.

Method Two: Diagnose RAM Issues

Another reason why Error code 8007002c occurs is when there’s a defective and wrongly installed memory chip. Try using the Windows Memory Diagnostic to diagnose if there are RAM Issues.

  1. Press on the Windows Key + X then select
  2. Type
  3. Select Windows Memory Diagnostic, from that window, selectRestart now, and check for problems

Method Three: Use Selective Startup

One more possible cause why Error code 8007002c occurs is due to third-party software. To fix this error, you can try booting up your device with Selective Startup — a boot type where you can load a limited set of startups and services.

  1. Open the System Configuration tool. On your Taskbar, type MSCONFIG in the Search Box then hit Enter.
  2. Select the General
  3. Select Selective startup option then tick on the Load system services
  4. Ensure that Load startup items check box is unchecked.
  5. Click Apply and

Can’t seem to put up with the long and technical manual repair process? You can still fix this error by downloading and installing a powerful automated tool that will surely get the job done in a jiffy!

Adobe Stock free collection

Unsplash

Pixabay

Pexels

Pikwizard Stock

Gratisography Stock photos

Conclusion

Check your game page and your DirectX

Update or reinstall GPU drivers

Set custom scaling to 100

Delete registry key

Use dedicated error fix tool

Error Code 0x8007007e – What is it?

Solution

Error Causes

Once this error code is encountered, it’s a clear indication that your Operating System has malfunctioned. This could be a consequence of an incorrect or failed installation of software. The software might leave invalid entries in the Windows registry. Improper shut down of your system and a malware attack are also causes of error code 0x8007007e. Additionally, someone with little or no technical knowledge might have deleted a system file by accident. Missing system files can also equate to other error codes such as registry error code 19 .

You may not always be able to prevent issues from affecting your computer, but proper measures can be taken to limit your risk of experiencing problems like error code 0x8007007e. See the following suggestions below:

  • Ensure proper system maintenance by regularly using your automated tool. This will ensure your system is in good shape and error-free. It will also clean your system regularly leading to a boost in PC performance
  • Keep antivirus software up-to-date. Antivirus software if crucial for the proper functioning of your computer. Keeping your antivirus updated is one of the best ways you can avoid problems with your PC.

Further Information and Manual Repair

Method One: System File Checker

System File Checker is a Windows tool that allows users to check their system for corrupt or bad system files. The utility scans for corrupt files and repairs them as well as files that may have gone missing.

Depending on the type of Windows operating system on your computer, you may need to follow varying instructions. However, note that Windows operating systems including Windows 10 and Windows 8 or 8.1 and Windows Vista all provide access to System File Checker via Command Prompt.

Once you run System File Checker, the tool should be able to repair and replace corrupted files. However, in cases where the repair process does not take place, you can attempt a manual repair by replacing the corrupt file the tool identifies with a good file. The process may require technical knowledge of Command Prompt so consider help from a Windows repair technician or consider contacting Windows for instructions based on your computer’s operating system.

Method Two: Run System Restore Tool

The System Recovery Options menu in Windows contains many tools which can enable users to resolve serious errors. In the case of Error Code 0x8007007e , one of the best tools in this menu is System Restore.

When an error occurs which inhibits users from accessing key functions on their system, System Restore enables the user to restores the computer to an earlier period without causing harm to files, photos, or documents.

However, once you run this tool, you will only be able to access files available within the period to which your computer is restored. For this reason, carefully consider which period is best suited to your purposes. Also, ensure you restore the system to a time when error code 0x8007007e was not present on your machine.

If System Restore does not resolve the error, you may undo the restoration changes. Ensure you have sufficient free space on your machine hard disk before you proceed (300 MB at least for hard drives above 500MB or at least 50 MB for smaller sized disks).

Method Three: Download Automated Software

When it comes to resolving error codes, it can often be a frustrating and tricky venture, especially when you are attempting to fix the problem manually. The Internet is awash with bits and pieces of instruction, some misleading at best with uncertain success rates.

But what if there was a one-stop-shop or better yet a tool that offered solutions for error codes including 0x8007007e? Download a powerful automated tool that offers easy and effective, user-friendly solutions for users with varying error code problems.

Источник

Источник

@agajdosi Could you help me with this, i tried reinstall both the addon and blender but nothing work, doesn’t seem to be firewall either
Starting with Namespace(port=’62485′, server=’https://www.blenderkit.com’, proxy_which=’SYSTEM’, proxy_address=», proxy_ca_certs=», ip_version=’BOTH’, system_id=’88974384510753′, version=’3.3.1.221122′)
02:58:16.567 ERROR: unhandled exception during asyncio.run() shutdown
task: <Task finished name=’Task-1′ coro=<_run_app() done, defined at C:UsersAdminblenderkit_datadaemondependencies3-3-1preinstalledaiohttpweb.py:287> exception=SystemExit(0)> [base_events.py:1729]
Traceback (most recent call last):
File «C:UsersAdminblenderkit_datadaemondependencies3-3-1preinstalledaiohttpweb.py», line 413, in _run_app
await site.start()
File «C:UsersAdminblenderkit_datadaemondependencies3-3-1preinstalledaiohttpweb_runner.py», line 121, in start
self._server = await loop.create_server(
File «C:Program FilesBlender FoundationBlender 3.33.3pythonlibasynciobase_events.py», line 1493, in create_server
raise OSError(err.errno, ‘error while attempting ‘
OSError: [Errno 10013] error while attempting to bind on address (‘127.0.0.1’, 62485): an attempt was made to access a socket in a way forbidden by its access permissions

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File «C:UsersAdminblenderkit_datadaemondependencies3-3-1preinstalledaiohttpweb.py», line 514, in run_app
loop.run_until_complete(main_task)
File «C:Program FilesBlender FoundationBlender 3.33.3pythonlibasynciobase_events.py», line 628, in run_until_complete
self.run_forever()
File «C:Program FilesBlender FoundationBlender 3.33.3pythonlibasynciowindows_events.py», line 321, in run_forever
super().run_forever()
File «C:Program FilesBlender FoundationBlender 3.33.3pythonlibasynciobase_events.py», line 595, in run_forever
self._run_once()
File «C:Program FilesBlender FoundationBlender 3.33.3pythonlibasynciobase_events.py», line 1881, in _run_once
handle._run()
File «C:Program FilesBlender FoundationBlender 3.33.3pythonlibasyncioevents.py», line 80, in _run
self._context.run(self._callback, *self._args)
File «C:UsersAdminblenderkit_datadaemondependencies3-3-1preinstalledaiohttpweb.py», line 433, in _run_app
await runner.cleanup()
File «C:UsersAdminblenderkit_datadaemondependencies3-3-1preinstalledaiohttpweb_runner.py», line 294, in cleanup
await self._cleanup_server()
File «C:UsersAdminblenderkit_datadaemondependencies3-3-1preinstalledaiohttpweb_runner.py», line 381, in _cleanup_server
await self.app.cleanup()
File «C:UsersAdminblenderkit_datadaemondependencies3-3-1preinstalledaiohttpweb_app.py», line 432, in cleanup
await self.on_cleanup.send(self)
File «C:UsersAdminblenderkit_datadaemondependencies3-3-1preinstalledaiosignal_init.py», line 36, in send
await receiver(*args, **kwargs) # type: ignore
File «C:UsersAdminAppDataRoamingBlender FoundationBlender3.3scriptsaddonsblenderkitdaemondaemon.py», line 218, in cleanup_background_tasks
exit(0)
File «C:Program FilesBlender FoundationBlender 3.33.3pythonlib_sitebuiltins.py», line 26, in call
raise SystemExit(code)
SystemExit: 0
02:58:16.580 ERROR: Task exception was never retrieved
future: <Task finished name=’Task-3′ coro=<online_status_check() done, defined at C:UsersAdminAppDataRoamingBlender FoundationBlender3.3scriptsaddonsblenderkitdaemondaemon.py:187> exception=UnboundLocalError(«local variable ‘resp’ referenced before assignment»)> [base_events.py:1729]
Traceback (most recent call last):
File «C:UsersAdminblenderkit_datadaemondependencies3-3-1preinstalledaiohttpweb.py», line 413, in _run_app
await site.start()
File «C:UsersAdminblenderkit_datadaemondependencies3-3-1preinstalledaiohttpweb_runner.py», line 121, in start
self._server = await loop.create_server(
File «C:Program FilesBlender FoundationBlender 3.33.3pythonlibasynciobase_events.py», line 1493, in create_server
raise OSError(err.errno, ‘error while attempting ‘
OSError: [Errno 10013] error while attempting to bind on address (‘127.0.0.1’, 62485): an attempt was made to access a socket in a way forbidden by its access permissions

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File «C:UsersAdminAppDataRoamingBlender FoundationBlender3.3scriptsaddonsblenderkitdaemondaemon.py», line 324, in
web.run_app(server, host=’127.0.0.1′, port=args.port)
File «C:UsersAdminblenderkit_datadaemondependencies3-3-1preinstalledaiohttpweb.py», line 514, in run_app
loop.run_until_complete(main_task)
File «C:Program FilesBlender FoundationBlender 3.33.3pythonlibasynciobase_events.py», line 628, in run_until_complete
self.run_forever()
File «C:Program FilesBlender FoundationBlender 3.33.3pythonlibasynciowindows_events.py», line 321, in run_forever
super().run_forever()
File «C:Program FilesBlender FoundationBlender 3.33.3pythonlibasynciobase_events.py», line 595, in run_forever
self._run_once()
File «C:Program FilesBlender FoundationBlender 3.33.3pythonlibasynciobase_events.py», line 1881, in _run_once
handle._run()
File «C:Program FilesBlender FoundationBlender 3.33.3pythonlibasyncioevents.py», line 80, in _run
self._context.run(self._callback, *self._args)
File «C:UsersAdminblenderkit_datadaemondependencies3-3-1preinstalledaiohttpweb.py», line 433, in _run_app
await runner.cleanup()
File «C:UsersAdminblenderkit_datadaemondependencies3-3-1preinstalledaiohttpweb_runner.py», line 294, in cleanup
await self._cleanup_server()
File «C:UsersAdminblenderkit_datadaemondependencies3-3-1preinstalledaiohttpweb_runner.py», line 381, in _cleanup_server
await self.app.cleanup()
File «C:UsersAdminblenderkit_datadaemondependencies3-3-1preinstalledaiohttpweb_app.py», line 432, in cleanup
await self.on_cleanup.send(self)
File «C:UsersAdminblenderkit_datadaemondependencies3-3-1preinstalledaiosignal_init.py», line 36, in send
await receiver(*args, **kwargs) # type: ignore
File «C:UsersAdminAppDataRoamingBlender FoundationBlender3.3scriptsaddonsblenderkitdaemondaemon.py», line 218, in cleanup_background_tasks
exit(0)
File «C:Program FilesBlender FoundationBlender 3.33.3pythonlib_sitebuiltins.py», line 26, in call
raise SystemExit(code)
SystemExit: 0

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File «C:UsersAdminAppDataRoamingBlender FoundationBlender3.3scriptsaddonsblenderkitdaemondaemon.py», line 191, in online_status_check
resp = await app[‘SESSION_API_REQUESTS’].head(url, timeout=3)
File «C:UsersAdminblenderkit_datadaemondependencies3-3-1preinstalledaiohttpclient.py», line 535, in _request
conn = await self._connector.connect(
File «C:UsersAdminblenderkit_datadaemondependencies3-3-1preinstalledaiohttpconnector.py», line 542, in connect
proto = await self._create_connection(req, traces, timeout)
File «C:UsersAdminblenderkit_datadaemondependencies3-3-1preinstalledaiohttpconnector.py», line 907, in _create_connection
_, proto = await self._create_direct_connection(req, traces, timeout)
File «C:UsersAdminblenderkit_datadaemondependencies3-3-1preinstalledaiohttpconnector.py», line 1154, in _create_direct_connection
hosts = await asyncio.shield(host_resolved)
asyncio.exceptions.CancelledError

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File «C:UsersAdminAppDataRoamingBlender FoundationBlender3.3scriptsaddonsblenderkitdaemondaemon.py», line 199, in online_status_check
resp.close()
UnboundLocalError: local variable ‘resp’ referenced before assignment

Источник

Понравилась статья? Поделить с друзьями:
  • Error erofs read only file system
  • Error erasing flash with vflasherase packet stm32
  • Error erasing disk error number 69888 0 ошибка
  • Error erasing disk error number 69888 0 an error occurred erasing the disk
  • Error erasing disk error number 69832 0