mirror of
https://github.com/prasathmani/tinyfilemanager.git
synced 2026-04-27 11:25:54 +03:00
[GH-ISSUE #999] Some Hosting do not allow this tinyfilemanager #645
Labels
No labels
Feature
Feature
Is It Really an Issue?
Need More Info
Request
Security
bug
duplicate
enhancement
enhancement
help wanted
invalid
pull-request
question
suggestion
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/tinyfilemanager#645
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Originally created by @azharul787 on GitHub (Mar 25, 2023).
Original GitHub issue: https://github.com/prasathmani/tinyfilemanager/issues/999
I am using this tinyfilemanager to manage file in cPanel. But some hosting do not allowing this file when I upload this file in cPanel hosting then it has been deleting suddenly. What can I do now please help me. and why this is happening, when I contacting to them they are saying this file is acting as a malicious type so that the hosting security system detect this take action.
@smalos commented on GitHub (Mar 25, 2023):
Check out
https://github.com/prasathmani/tinyfilemanager/issues/995
@prasathmani commented on GitHub (Mar 25, 2023):
https://github.com/prasathmani/tinyfilemanager/issues/759
https://github.com/prasathmani/tinyfilemanager/issues/581
@ner00 commented on GitHub (May 27, 2023):
I think this is bound to happen no matter how much stuff is tweaked; it's a file manager and hosting companies do not like custom file managers which may be used by hackers to access, edit or download sensitive data. This must be resolved directly with the hosting company because eventually a new malware signature will blacklist TFM again.
You either have access to the hosting service and a whitelist for TFM or take it up with the hosting admins.
This issue should be closed.