-
-
Notifications
You must be signed in to change notification settings - Fork 148
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
Bug: I can't get very specific files to upload #628
Comments
What do you mean by uploading but not doing anything? Do you get a response from the server when you send the POST request? Zipline should be able to handle any sort of file so I'm not sure what the problem is yet, but you can try to enable debug logs by adding the |
Hey diced. I turned on the debugging and found that the server just straight up doesnt receive a POST request for the files i mentioned that I cannot upload. Logs below. Uploading an image: Uploading a .zip file: |
Sorry about the late response, but if you are still having this problem I'd check the browser logs next, and another thing that may be the issue is your reverse proxy somehow blocking certain files? I'm not sure though. |
What happened?
I setup this server 2 days ago so bare with me. Zipline is running on a proxmox xubuntu vm currently with docker. I've finally managed to set it up with an nginx reverse proxy, and am able to get on the site itself to upload very specific things. By that I mean that I can upload jpg, xlsx and mp4 files, but not zip, pptx or exes. I find this quite odd as I've setup zipline to not block any extensions what so ever in the docker-compose.yml file. Also, it's not that it denies it outright, its more like it says that its uploading whilst its not actually doing anything. Logs show that the files that never upload aren't creating any errors and normally receiving requests.
Version
latest (ghcr.io/diced/zipline or ghcr.io/diced/zipline:latest)
What browser(s) are you seeing the problem on?
No response
Zipline Logs
Browser Logs
No response
Additional Info
No response
The text was updated successfully, but these errors were encountered: