-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OSError: [Errno 10013] - BlenderKit might get blocked by antivirus (Commodo, McAffee, Norton360) #259
Comments
Same thing happens to me. Here's more info: Traceback (most recent call last): in loop, freezing Blender at every single attempt of connection |
I am not a software developer, just a user. I find out a problem and report it. |
Hi @Poduhvat, thank you for your report. Also thank you @MicheleGiunto for the logs, it seems the problems are the same: the add-on starts a background server which downloads the assets and in your cases the server is not responding - meaning it probably did not start for some reason. If you want to debug, there is a file located at: If you paste us the log, we will find a solution for you. It could be an antivirus, we had cases like that before... or something else. In all cases we recently created a fix for better handling of this situation so the Blender does not lag, even though the search will not work, and the add-on will print out the messages to GUI, so it is more understandable what is going on, right now it can be quite hidden if one does not dig into the console. |
Thank you for the answer agajdosi. I had solved the problem by installing older version of Blenderkit 3.0.5 which works perfectly. So in order to find what is problem maybe you just need to compare changes which are made in 3.1.7 version relative to 3.0.5. version. |
@Poduhvat I am glad 3.0.5 works fine for you. For the requests on models, images etc. it uses threads, which were announced by Blender devs as not completely safe to us. At the moment of 3.0.5 we had several reports of Blender just randomly crashing which is quite annoying from the perspective of the user and also developer of the software - as basically both cannot do much more than just hoping... We investigated and tested several proposals for the solution and one which we evaluated as the best was to move the threading outside of the Blender into separate program running in the background - the daemon server which is part of the add-on since 3.1.0. For most users it fixed the problems and we are pretty happy with the overall results (and so we move more and more computing and tasks from the add-on to the daemon server). However the downside is... that on some systems (mostly Windows with some strange antiviruses) the daemon might not start which then leads to the error @MicheleGiunto posted. There the add-on tries to communicate with the local daemon server, but the requests fails as the daemon is not running and action is required to find out and fix. It does not happen often at least from out data. But that does not mean we are not working on fixing it. I fully understand how frustrating it can be that something just does not work out of the box. So we recently pushed a PR which improves the error message to the users and also prevents the add-on from lags when daemon is not running - the add-on will not search and basically not work, but at least the Blender will not be affected. And now we are working on making the start more robust. But one thing is our side and another are the hundreds of antiviruses which sometimes might block the daemon - we slowly need to cover all of those and that will require some feedback from users and also some time. We already covered some, but it is a long run unfortunately. |
@agajdosi this is the daemon log unhandled exception during asyncio.run() shutdown |
Thanks @MicheleGiunto! It could that the port is already used by another application, in the Blender preferences for the BlenderKit add-on, there is an option called |
@Poduhvat That's all folks! bye |
@J-ester93 Thank you for your logs and all the information! I am glad it works for you now. I have created a follow up issue #271 in which we will catch the OSError: [Errno 10013] and will print an information how to get over it - the solution you have provided. Previously we have added a catch for another OS/Win Error connected to Commodo, but it seems it can block in various ways with various errors as results. 😿 |
An FYI for McAffee users. Trying to open the default 62485 port didn't work for me. Maybe I'm doing it wrong. Changing the port in BK prefs to 1234 works, and needs no firewall rule. Blender is back to being buttery smooth. |
Thank you for sharing the information @sboddy! 🥇 |
Thank you for the detailed explanation Andreas.
I am using Kaspersky antivirus so maybe you can test is that the problem.
Also I have a firewall. I turned off Kaspersky in order to work when the
3.1.7 version was installed but it did not help. I do not remember that I
had turned off the firewall at that time.
Best regards,
Nenad
пет, 2. сеп 2022. у 11:14 Andreas Gajdosik ***@***.***> је
написао/ла:
… @Poduhvat <https://github.com/Poduhvat> I am glad 3.0.5 works fine for
you. For the requests on models, images etc. it uses threads, which were
announced by Blender devs as not completely safe to us. At the moment of
3.0.5 we had several reports of Blender just randomly crashing which is
quite annoying from the perspective of the user and also developer of the
software - as basically both cannot do much more than just hoping...
We investigated and tested several proposals for the solution and one
which we evaluated as the best was to move the threading outside of the
Blender into separate program running in the background - the daemon server
which is part of the add-on since 3.1.0. For most users it fixed the
problems and we are pretty happy with the overall results (and so we move
more and more computing and tasks from the add-on to the daemon server).
However the downside is... that on some systems (mostly Windows with some
strange antiviruses) the daemon might not start which then leads to the
error @MicheleGiunto <https://github.com/MicheleGiunto> posted. There the
add-on tries to communicate with the local daemon server, but the requests
fails as the daemon is not running and action is required to find out and
fix.
It does not happen often at least from out data. But that does not mean we
are not working on fixing it. I fully understand how frustrating it can be
that something just does not work out of the box. So we recently pushed a
PR which improves the error message to the users and also prevents the
add-on from lags when daemon is not running - the add-on will not search
and basically not work, but at least the Blender will not be affected. And
now we are working on making the start more robust. But one thing is our
side and another are the hundreds of antiviruses which sometimes might
block the daemon - we slowly need to cover all of those and that will
require some feedback from users and also some time. We already covered
some, but it is a long run unfortunately.
—
Reply to this email directly, view it on GitHub
<#259 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A2Y6PRIJLBDKVNLDMBKTRTDV4HANVANCNFSM5725NHBA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
Nenad Paunovic
co-owner
Poduhvat Ltd.
|
Hi @Xerisz, could you please try to change the port in the configuration settings of the add-on? It is possible that some process on your system already uses the port 62485 which blocks the add-on from starting a daemon process using this port. |
There is a new version comming which could help with the problems, you can try it in here: |
In rare cases the port can be in the ranges excluded by Windows, to check the excluded ranges, you can run in PowerShell:
If the BlenderKit's daemon's port (default port number: 62485) is in the range, please choose different port in the add-on preferences. Trying with different port number is a good idea even though the port is not in the excluded ranges. |
Hi all, we have just recently released a new public pre-release of the add-on. Could you please try it and let us know if this problem is still present or was fixed in this new version? To install this pre-release you can:
|
Ok, thank you
…On Sun, Dec 18, 2022, 19:47 Andreas Gajdosik ***@***.***> wrote:
Hi @Xerisz <https://github.com/Xerisz>, could you please try to change
the port in the configuration settings of the add-on? It is possible that
some process on your system already uses the port 62485 which blocks the
add-on from starting a daemon process using this port.
—
Reply to this email directly, view it on GitHub
<#259 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ATLCQG2I6WFL6AECLUGOZ3DWN4BXXANCNFSM5725NHBA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Recently problem with daemon being blocked was also reported with Norton360: #534 (comment). |
Please update to https://github.com/BlenderKit/BlenderKit/releases/tag/v3.12.0.240423, this release contains code-signed Client binaries (doing what was previously doing Client). Code-signed binaries tells the OS and antiviruses, that BlenderKit has produced and signed the code which should increase their trust. If you still face trouble, please report the BlenderKit Client binary as false positive, once they scan the binary, they should move it to whitelist and no longer block that version or future versions signed with same certificate. |
Describe the bug
When installed or activated within Blender 3.2.2 at windows 10 makes Blender bugging i.e. working extremely slow, with 15 to 20 seconds reaction to even simplest commands like rotating or moving default cube. When deactivated or removed Blender works normally.
Expected behavior
Should react in a moment like Blender works without this kit or with previous version of Blender kit.
Screenshots/video
No response
Logs
Environment
Additional information
No response
The text was updated successfully, but these errors were encountered: