-
-
Notifications
You must be signed in to change notification settings - Fork 266
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 Report: Upload fails with ZIP or bulk files #750
Comments
Could you share the full logs please? |
Hello @stonith404 Many thanks for your fast response! I'm not sure what you mean exactly, this is all the log I got from the Pingvin-Container in Docker (sorry, log was to big to paste here: Many thanks for your efforts! |
Thanks for providing the logs. It's a bit hard to find the error in this lengthy log file. Could you remove the container, start it again, trigger the error and then share the full logs?
|
Sorry for the long logs, here's the fresh one with the error:
|
Great thanks. It seems like the backend gets killed. I have no clue why. Can you inspect the memory usage while uploading? with |
Hello again, sorry for the delay of my answer! I did as you said, here's my docker container mem usage: And here's the output of docker stats, there's significant jump in used resources while try to upload a big file (around 2GB): BTW: It seem that there are sllightly different logs? The log from yesterday was directly from Docker Desktop, now I've seen that "Dozzle" gives me another error when trying to upload a big file. Maybe this helps? Could my reverse Proxy (Synology NAS) be an issue? On second thought it did not work either locally without the reverse proxy... Odd...
EDIT: I had to change the "outside" port because I have many containers and your standard port was used from another container. I left the "inside" port as is but there are other containers which use the same port (8080) internally, could this be an issue and the reason for the error above? EDIT 2: Changed back to standard ports 3000:3000 now, unfortunately the issue stays the same but I think there's a new error (i tried to upload something over my internal network now instead of the ddns-domain...) [Nest] 53 - 01/17/2025, 1:32:45 PM ERROR [ExceptionsHandler] request aborted Sorry for that many information and many thanks again for your efforts and for looking into this! |
👟 Reproduction steps
I'm on MacOS Monterey with latest Docker Desktop.
When I try to upload multiple large files (e.g. biggest around 400MB) or a ZIP, Pingvin throws an error. If I upload 1 large file it usually works.
👍 Expected behavior
It should upload multiple large files and ZIP-Files without error.
👎 Actual Behavior
Pingvin throws an error and gets unresponsive, if I try to refresh the page I get an "internal Server error" and I have to restart the Docker Container with Pingvin.
📜 Logs
level=errorts=1737043143.8860402logger=http.log.errormsg=dial tcp [::1]:8080: connect: connection refusedrequest.client_ip=172.22.0.1request.headers.Accept=["application/json, text/plain, /"]request.headers.Accept-Encoding=["gzip, deflate, br, zstd"]request.headers.Accept-Language=["de,en-US;q=0.7,en;q=0.3"]request.headers.Connection=["close"]request.headers.Content-Length=["454674112"]request.headers.Content-Type=["application/octet-stream"]request.headers.Cookie=["REDACTED"]request.headers.Dnt=["1"]request.headers.Origin=["https://mydomain.com"]request.headers.Referer=["https://mydomain.com/upload"]request.headers.Sec-Fetch-Dest=["empty"]request.headers.Sec-Fetch-Mode=["cors"]request.headers.Sec-Fetch-Site=["same-origin"]request.headers.Sec-Gpc=["1"]request.headers.User-Agent=["Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:134.0) Gecko/20100101 Firefox/134.0"]request.headers.X-Forwarded-For=["myIP"]request.headers.X-Forwarded-Proto=["https"]request.headers.X-Real-Ip=["myIP"]request.host=mydomain.comrequest.method=POSTrequest.proto=HTTP/1.1request.remote_ip=172.22.0.1request.remote_port=64610request.uri=/api/shares/sr0vOnzu/files?name=Extraordinary+-+S02E01+-+The+Void.mkv&chunkIndex=0&totalChunks=1duration=0.002192416status=502err_id=5eir3ge5eerr_trace=reverseproxy.statusError (reverseproxy.go:1269)
The text was updated successfully, but these errors were encountered: