You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 2, 2021. It is now read-only.
The retreiving process fail with 404 when requesting encrypted files with certain size (trying to retreive from the same node or other node) but not with other size
It failed with these size
16 154 ko
16 236 ko,
16 254 ko
16 354 ko
However, it work with all other size (even 16 054 ko and 16 454 ko)
--> An encrypted zip with size from 16.1M to 16.4M diseappear instantly ?
Notes:
The whole uploading + encrypting process succeed (I have a hash and no errors)
I don't have this problem when I don't use encryption.
I tested it on 2 different private network, same result
I haven't tested with other file format
System information
Version: 0.5.7-stable
Go Version: go1.13.3
OS: linux Ubuntu 18 server
full node (not tested on lightnode)
Expected behaviour
Retreiving the content when sending a request to the localhost api
Actual behaviour
Geting a 404 error when getting file (even instantly after uploading it on the same node)
Steps to reproduce the behaviour
truncate -s 16254k test.zip (to create the file)
swarm up --encrypt test.zip
(enc the hash with access new act --grant-keys), also fails with the hash+key from the cmd above
curl localhost:8500/bzz:/$hash/ -o result.zip
Backtrace
Code: 404
Message: file not found bzz:/... (hash) .../: no suitable peer
The text was updated successfully, but these errors were encountered:
After another issue today, we have the same problem with 49 136 Ko files but not 49 236 ko files
NicolasKritter
changed the title
Can't retreive 16.1Mo - 16.3 Mo files after encryption
Files from specific sizes instantly disappear after encryption
Jul 9, 2020
The retreiving process fail with 404 when requesting encrypted files with certain size (trying to retreive from the same node or other node) but not with other size
It failed with these size
However, it work with all other size (even 16 054 ko and 16 454 ko)
--> An encrypted zip with size from 16.1M to 16.4M diseappear instantly ?
Notes:
The whole uploading + encrypting process succeed (I have a hash and no errors)
I don't have this problem when I don't use encryption.
I tested it on 2 different private network, same result
I haven't tested with other file format
System information
Version: 0.5.7-stable
Go Version: go1.13.3
OS: linux Ubuntu 18 server
full node (not tested on lightnode)
Expected behaviour
Retreiving the content when sending a request to the localhost api
Actual behaviour
Geting a 404 error when getting file (even instantly after uploading it on the same node)
Steps to reproduce the behaviour
curl localhost:8500/bzz:/$hash/ -o result.zip
Backtrace
The text was updated successfully, but these errors were encountered: