Replies: 3 comments
|
@mthsmb out of curiosity, have you tried sftp over zero trust? I believe there are still issues with node to node transfers the team is going to work on. |
0 replies
|
I noticed that the problem with Cloudflare will disappear when the target server will download the transfer files, and currently it is the source server that pushes them, Cloudflare has no limit when downloading files (when the files are downloaded from the target server) |
0 replies
|
Closing as a duplicate of #846, please continue the conversation there. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
The feature I would like to see.
I've been dealing with a frustrating issue that's been around since Pterodactyl (issue #4696 - closed but never actually fixed). For those of us running infrastructure behind Cloudflare Zero Trust, transferring large files is basically impossible right now.
The main problems I'm hitting:
This makes working with any substantial files a nightmare, and the workarounds either don't work reliably or defeat the whole purpose of using Zero Trust in the first place.
How I'd like to see it work.
I'd love to see a proper chunked upload system that actually works with Cloudflare's limitations. Here's what I think would make this work:
Chunk Management:
Configuration options I'd want:
Recovery system:
UI improvements:
Why this matters to me.
This has been plaguing the community for years. The original Pterodactyl issue acknowledged the problem but never shipped a fix before closing it. For anyone serious about security and using Zero Trust, this is a daily headache.
What would make Pelican stand out here:
Since Pelican is positioning itself as the next evolution of Pterodactyl, solving this would be huge for the community - especially those of us running production deployments where security isn't optional.
All reactions