-
Notifications
You must be signed in to change notification settings - Fork 56
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
TypeError: Cannot read properties of undefined (reading 'hasher') #488
Comments
Seems to be a relatively old commit, try updating |
Ok. |
It's likely due to chunks temporary data timing out The default timeout in config is 30 minutes If you can confirm it isn't something else, a temporary workaround is to simply increase the timeout |
I'm on a VPN so the IP doesn't matter if your worrying! |
I think you probably misconfigured that domain in your nginx config For some reason nginx thinks If it was lolisafe itself that was having a file permission issue, you basically wouldn't be seeing that on your nginx logs (at most you'd see it reporting that the request ended with http error code 500 or equivalent), since nginx is simply routing the requests from clients to/from lolisafe Meaning it's likely unrelated with the undefined hasher errors |
Keep in mind this is only for files 2gb> all the other files that are like 900mb or 1gb work perfectly fine. |
Update: No more hasher errors after updating. Its failing to send the last POST request to api/uploads/finishchunks. Maybe you could try to upload something 1GB and see if it works. |
Hmm, I will just re-install/ redo all my configs and lolisafe you can close this. |
Can you help me with this error.
`[2022-05-06 22:20:52] TypeError: Cannot read properties of undefined (reading 'hasher')
at /root/lolisafe/controllers/uploadController.js:575:42
at async Promise.all (index 0)
at async Object.self.actuallyFinishChunks (/root/lolisafe/controllers/uploadController.js:529:5)
at async Object.self.finishChunks (/root/lolisafe/controllers/uploadController.js:511:5)
The text was updated successfully, but these errors were encountered: