"Download and import texture brush pack" doesn't work with the Grease Pencil Tools Add-on #115336
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
9 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#115336
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Operating system: Windows 10 Enterprise
Graphics card: NVIDIA GeForce RTX 3070
Blender Version
Broken: 4.0.1
Worked: 3.6 LTS (maybe 4.0)
Short description of error
Blender gives an error message that the internet connection is off, though that is false, when i click on "Download and import texture brush pack". My theory is an error due to the DDoS-attack, but don't really know.
error message is: Check your internet connection, impossible to connect to url: https://download.blender.org/demo/bundles/bundles-3.0/grease-pencil-brush-pack.zip
When i paste the url in my browser the brush pack downloads fine, but then you have to append it manually.
Exact steps for others to reproduce the error
"Download and import texture brush pack" doesn't work with the Grease Pencil Tolls Add-onto "Download and import texture brush pack" doesn't work with the Grease Pencil Tools Add-oncc @Pullup
Website is up and packages are available there.
Maybe, yes.
Past versions also throwing same error
Hi @PratikPB2123 @markus.hanson
I investigated the problem and I think it's a direct consequence of the attack.
The accessibility rules of the server seem to have changed (to enhance protection from bots and DDoS I presume).
(so it's independent of the Blender versions)
To download the pack from the addon I've just set a basic python urllib request to check the page and download the file. It has always worked, but when accessed now using this method, it returns a 403 error.
Sadly, my knowledge of web scraping is very limited, and I don't know how to work around this.
It's possible the server policy changes are only temporary to mitigate the server attacks.
Maybe @pablovasquez knows if the server state will roll back to previous external access rule ?
I have also had this issue. I can certainly understand if this is a protection against future DDoS attacks; but now that I have it on my machine via my browser, is there another means of appending these brushes automatically?
I am aware that I can simply append them from the blend file each time, which is what I'm doing in the interim; but it would be very convenient if there was an easy way to have them load at start for a 2D animation file.
I have the same issue too and try to import these brush set. It doesn't work too...
cc @ThomasDinges
@Arnd Can you check please?
There's a code workaround available -- seems that we need to set at least the User-Agent on the request, otherwise we'll get back 403's. I'm unsure "which" user-agent to use that would be most appropriate and it's weird that this is all it takes to bypass the issue...
@deadpin I've tested the same thing (with the same user agent ^^). Not sure if it's a good and durable solution, at least it works.
But it means people using previous versions of Blender will still be denied access to the brush pack.
If we have a confirmation that the server parameter changes are definitive, then let's go for this.
I'm not sure how CloudFlare operates, but to make this work without upgrading blender (the browser agent solution is not accepted yet anyways), would it not be possible to set a redirect to a less secure server there?
@Arnd Can you please check?
I've gone and tried a few things.
I have found a way to except particular downloads from certain checks (not listing them here to not give attackers any ideas).
This should now affect the given URL and other paths that concern the demo-bundles.
I have repeatedly been able to fetch the file correctly on my instance now; but am waiting for feedback from someone helping me test the issue.
Initial feedback seems to indicate that the changes have solved the issue.
Closing the issue; please re-open if any incidents around this pop up after this date.