FYI: I have already created the account and made API key (I wrote it down). I downloaded the Uplink CLI from the GitHub release page too. My Satellite is Asia-East-1 and I don’t add my credit card or STORJ on my accout yet. I have never used Amazon S3 so I actually am not familiar with its concept or usage.
But be aware that currently there is a bug preventing you from succesfully uploading files >64MB to nextcloud. We’ll have to wait until that one is fixed. Smaller files work fine and all other operations too.
But because of rate limiting, doing many uploads/downloads/deletes will only make parts of them succeed… Also have to wait for a proper rate limiting implementation here too.
So my advice currently is to only use it for testing and “proof-of-concept” but nothing else until those bugs are fixed.
I then tried to upload a small file (“Hello world.txt”) from a browser, and it failed soon due to the error below.
An exception occurred while completing a multipart upload: Error executing “CompleteMultipartUpload” on “http://localhost:7777/sample/Hello%20world.txt?uploadId=Upload2”; AWS HTTP error: Server error: POST http://localhost:7777/sample/Hello%20world.txt?uploadId=Upload2 resulted in a 500 Internal Server Error response: <?xml version="1.0" encoding="UTF-8"?> InternalErrorWe encountered an internal error, pleas (truncated…) InternalError (server): We encountered an internal error, please try again. - <?xml version="1.0" encoding="UTF-8"?> InternalErrorWe encountered an internal error, please try again./sample/Hello world.txt3L1373L137
Would you please let me know how to solve the issue?
Please don’t. Storjlabs seems to be basing their decisions on this rate limit on who requests an increase and encourages you to request that. So pleas go to support.tardigrade.io and click the new request button to ask for your rate limit to be increased if you run into this. They will need your feedback in order to determine the correct setting for everyone. If you wait for them to fix it, they also don’t get the signal that the current limit is too low. Don’t hesitate to ask for this increase on your account.
Seems your gateway is down or inaccessible. Please, verify that either by a minio browser http://localhost:7777/ , or aws s3 CLI.
I think your gateway could be running on other PC rather than the PC with Nextcloud
Ah yes I can reproduce this if you try to upload multiple files. Never tried that before. Guess I can add that to my already open github issue about Nextcloud.
Yeah this new connector and how-to is quite a mystery to me too…
So the “old way” is: set up the gateway on the machine where your nextcloud is running. Then in nextcloud set up an external aws3 storage, the config should look like the picture I posted a month ago: How to add Storj to Nextcloud "as external storages"?
Note that uploading files >64MB is still not working but everything else seems to be fine.