Cloudron Forum

That's just how life goes - either a dry spell or a lot of good things all at once
Yeah, I posted it on the NodeBB forum too - maybe someone will find it useful

Hey everyone,

I just published a fresh take on offloading NodeBB uploads to Backblaze B2 — built from scratch on the modern AWS SDK v3 because the existing S3 plugins haven't been touched in years.

npm: https://www.npmjs.com/package/nodebb-plugin-backblaze-b2-s3-uploads
GitHub: https://github.com/sqlik/nodebb-plugin-backblaze-b2-s3-uploads

What it does

• Intercepts filter:uploadFile and filter:uploadImage, streams files to a private B2 bucket via the S3-compatible API
• Stores only an opaque proxy URL in post content: /uploads/b2/<key>
• On every download, a permission-aware proxy checks privileges.categories.can('topics:read', cid, uid) and 302-redirects to a fresh presigned URL — so the same setup serves both public categories (anonymous visitors get the redirect) and private categories (403 if no access)
• All settings in ACP, including key ID/secret, presigned TTL, allowed extensions, max file size, max video size

Why another S3 plugin

The existing nodebb-plugin-s3-uploads family is on AWS SDK v2 (deprecated since 2024) and assumes much older NodeBB. This one targets NodeBB v3+ and v4+, AWS SDK v3 (modular, smaller bundle), ESM admin module, and a permission model that respects category privileges instead of just public-or-not. Tested in production on a live v4.x forum.

Optional Bunny CDN delivery

If you already use Bunny, flip a toggle in ACP and the proxy redirects to a Bunny token URL instead of a B2 presigned URL. Bunny pulls from B2 once (free, Bandwidth Alliance) and caches at the edge. Permission checks stay authoritative on every request — only the bytes go through Bunny.

Other features

• Background orphan cleanup — uploads dropped into the composer but never used in a saved post are tracked and pruned on a configurable schedule
• i18n — English and Polish included, more welcome
• MIT license

Roadmap

• Migration command for existing local uploads (with dry-run)
• Per-user / per-group upload quotas
• Optional IP-bound Bunny tokens

This is a 0.1.1 release — running on a small private forum, but I'd love feedback, edge cases, and PRs from anyone willing to try it on a different NodeBB setup. Issues and ideas welcome on the GitHub repo.

Thanks for taking a look!

@girish Hi. I checked, it works.
Thank you

Hi.
Similar problem for /pdf-to-html module>

Thanks

@nebulon Confirm. After update to the new app package everything works brilliant.

Thank you.

@nebulon /user/{uid}/consent
have a look at the updated github entry

Hi guys. Can you take a look at this topic? Is the problem somewhere else on the side of installing the Cloudron package?

https://community.nodebb.org/topic/16689/data-export-in-your-rights-consent-not-working-is-a-bug/2?_=1663704317180

@nebulon Many, many thanks. This solved my problem.
What a beautiful day

@jdaviescoates said in Strange problem after installing some plugins:

It'd be better if @staff could work out what the issue was

I definetly agree. I did what I could. As for me, the problem is in this particular installation via Cloudron. But what's the problem - I don't know, my knowledge is too little to debug it.

And I regret it, because Cloudron is a really great service and I would like to use it.

PS. Sorry for my English...

@robi I sent a ticket to support - I got a laconic answer that does not solve my problem.

To be honest - I tested everything several times - I installed cloudron on several VPS from different vendors and it worked the same each time - after installing any plugin from the repository it resulted in the same error.

Finally, I installed nodebb without cloudron - everything works as it should. All plugins work (the ones I tested on the cloudron installation).

You can close this thread. Elsewhere, I'll pay more, but at least everything works for me.

@robi - thank you - at least you tried to help.

One more series of tests - I tested every plugin that is available in the nodebb admin panel (marked as 2.4.5 compatible).
The effect is the same every time. Installing, activating and rebuilding... and I get the problem described at the beginning of this thread.

I did additional tests. On the new droplet in DigitalOcean, I launched a new Cloudron instance and a new nodebb installation, without any additional customization.
Then I installed nodebb-plugin-question-and-answer.
Effect - exactly the same problem as I described in the first post.

I have no idea where to look for the reason, I don't know enough to do it.

@robi Of course I understand it all. Nevertheless, many of those here are using these plugins with success. Even this forum uses the nodebb-plugin-question-and-answer plugin - for me, installing this plugin causes exactly the same problems as I described.

That's why I will write again - I understand that plugins can cause problems, but some people can deal with it somehow - I hope someone will tell me how.

@robi I've already done it. Regardless of which plug-in I install (apart from the standard set delivered with nodebb at the beginning) the problem appears.
I have reinstalled everything several times.
Moreover, uninstalling these plugins now does not fix the problem. In order to remove the error, I have to restore the installation from a backup before installing any of the plugins.

Hi everyone.
I have a problem after installing a few plugins, namely:
1.nodebb-plugin-customize
2. nodebb-plugin-poll
3.nodebb-plugin-iframely

I installed numbers 1 and 2 from the nodebb admin panel. Number 3 I installed through the cloudron console with the command

/usr/local/bin/gosu cloudron:cloudron yarn add nodebb-plugin-iframely

For clarity - before installation, everything worked fine.
I also installed plugins independently (individually) - installing any of them causes the same errors.

What are these errors?
Entering any page on the forum does not load that page. Only after refreshing the page, the content is loaded.
It is also not possible to reply to a post - clicking 'reply' has no effect.
The following video shows what it looks like:
https://drops.sqlik.com/Z4uDzd2K

Additional information:
The iFramely plugin works fine.
I tested on macOS on Safari and Edge

Can anyone tell me where to look for the cause, what could be wrong?
I will be grateful for any help and hints.