Solved Strange problem after installing some plugins
I have a problem after installing a few plugins, namely:
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:
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.
Uninstall one by one to see which is left causing the issue.
Or remove all and install one by one and test.
@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.
@sqlik check the dates, as those plugins may not be compatible then.
NodeBB is pretty stable out of the box on Cloudron, however the plugins can interfere and may need testing on a cloned app of your forum with a restart/rebuild in between each install of a plugin to make sure it works as expected.
It's not something we can fix here, as it's the way NodeBB implemented plugins.
@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.
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.
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.
Can you find errors in the nodebb app logs?
Check right after install, then after rebuild too.
You can also email support@ if you care to enable remote access support.
@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.
jdaviescoates last edited by
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...
This smells a bit like a node package manager issue. Our package uses
yarndue to some change how
npmstarted to deal with symlinks. However
yarnbehaves slightly differently than
npmin dependency resolution, which causes issues with how
webpackin turn works. This is one blocking port to get the latest nodebb version out there. I am trying to figure out a solution for that.
For some more background https://github.com/NodeBB/NodeBB/issues/10877