[nodebb-plugin-storj-upload] Storj Upload
-
So to install this [nodebb-plugin-storj-upload] I can do it via dashboard?
-
-
Just to be clear,. it's this index.js file located here right?
And only those 4 lines that are marked with "your ..."
This is what I have done so far,
- npm install ferumdev/nodebb-plugin-storj-upload
- modifiy index.js and fill my details
- On my Admin panel, Find the plugin, activate it, rebuild and restart.
And got it working, turned out there was something wrong with my access grant, I retry and make a new one, it works.
Now just to be safe, before I apply it on my remote server, that remote server already have the old
nodebb-plugin-imgur
that I install it through Admin panel. I just need to Deactivate -> Uninstall ->Rebuild, then do the exact method to install storj? -
@cat said in [nodebb-plugin-storj-upload] Storj Upload:
Just to be clear,. it's this index.js file located here right?
And only those 4 lines that are marked with "your ..."
This is what I have done so far,
- npm install ferumdev/nodebb-plugin-storj-upload
- modifiy index.js and fill my details
- On my Admin panel, Find the plugin, activate it, rebuild and restart.
Yes
And got it working, turned out there was something wrong with my access grant, I retry and make a new one, it works.
It's seems a bug from Storj, on the official Storj community you can found recommendation use a last browser version, when you create new bucket, change api key or when you set grant access for you're key (read/remove/directory listing and etc)
Now just to be safe, before I apply it on my remote server, that remote server already have the old
nodebb-plugin-imgur
that I install it through Admin panel. I just need to Deactivate -> Uninstall ->Rebuild, then do the exact method to install storj?You can only disable
imgur
plugin and nextrebuild
forum -
Anyone know what caused this?
Didn't happen before, it's just a png picture
-
What IS this screen ?
I know malwarebytes have considered Storj as domain malware because a person used Storj to host malware.
I contacted them and warned them and they resolved the problem on the malwarebytes forum. I will find the link tomorrow.but if the file is hosted on your Storj account, it is problematic and it would be better to contact them directly
-
@cat Yes, the Storj have this problem with anti-malware filters The temporary solution a manually add Storj link to whitelist on youre program or like alternative use proxy domain (mirror) for Storj link.
https://forums.malwarebytes.com/topic/298561-gatewaystorjshareio-blocked/
https://forums.malwarebytes.com/topic/301050-linkstorjshareio-blocked/ -
-
I don't know if I'm in the right place @brazzerstop @baris
My apologies in advanceI'm trying to upload a gif file to NodeBB using this plugin.
Spec file : 1622 x 1011px - 3.03 MoI enabled the gif extension in ACP and raised the size limits but I still got a 413 error when uploading
If you have suggestion, I take it
Thanks
-
I'll try to look in that direction in the meantime.
-
Ok better now with nginx directive. Thanks @baris
not error directly : This time, I have uploaded 100% popup display and this error popup after few times with 500 error in browser console :
NodeBB Log :
2023-09-13T20:46:04.018Z [4567/1483037] - [31merror[39m: nodebb-plugin-storj-upload :: read ECONNRESET 2023-09-13T20:46:49.745Z [4567/1483037] - [31merror[39m: nodebb-plugin-storj-upload :: read ECONNRESET 2023-09-13T20:48:19.859Z [4567/1483037] - [31merror[39m: nodebb-plugin-storj-upload :: read ECONNRESET
-
Yes @brazzerstop , it works with a gif which is a smaller size, but that's not really what I'm looking for.
I wanted to specifically upload a larger gif because I couldn't make it smaller. Which doesn't seem to work.
I have currently hosted this gif on IMGBB without problems but it's a shame to not take advantage of the plugin and StorJ.
-
@DownPW said in [nodebb-plugin-storj-upload] Storj Upload:
Yes @brazzerstop , it works with a gif which is a smaller size, but that's not really what I'm looking for.
If you can upload GIF with small size, this is a problem with you're default config nginx, I mean limit size like
client_max_body_size
(don't forget restart nginx after change config)If you need allow file size 100000 KB - 100 MB, try set
client_max_body_size
to150M
or200M
-
Baris already tell me to add this, see post above
client_max_body_size 6M;
And of course reload/restart