That makes sense, and I support the idea. The error message points the blame to the API and not the DNS. Modifying the error message to check the DNS first definitely saves time on the troubleshooting end and on yours.

Even if it's the exception the it's worth considering how much time it takes to check for each step during the process. Anyways thanks for the help. You can close this thread 🙂

@girish Thank you for checking. I will look into other options in cloudron to do this.

@julian Brilliant! I am certain it is both destined and necessary for the future of free speech, decentralisation, and creator-owned content. Thank for your vision and taking on these things. It gives me hope 🙂

Its right in there? 😕 ?

Quote:

cd /app/code /usr/local/bin/gosu cloudron:cloudron yarn add nodebb-theme-timuu

I mean you even try to install the same theme as in in the docs ❓
Did you try it?

Looks like something changed recently. It installs just fine now:

image.png

@girish Thank you 🙂

@nebulon Thanks for letting me know. Getting to know the provided infrastructure more and more on 🙂

@nebulon said in How much 'work' is it to support a nodebb install?:

We have a couple of plugins enabled

Would you mind to tell?

@girish Thanks for the help.

The plugin does work fine but does not meet my expectations. I thought that, after installing the plugin, somewhere nodebb would have a page dedicated to events in a calendar. What happens is the events appear in a post OK, but there is not dedicated page where all the events happening appear. I mean that I still cannot see this:

alt text

Also, though the notification was set to happen, no notification occured. This might perhaps be because the default setting for checking new events is a long period of time.

I thought there might be a calendar icon or something to click here:

brave_GGN5dfEARQ.jpg

@sixfold_distract if you suppress the healthcheck, Cloudron thinks the app is not responding which can have negative side effects. Nothing to worry about just leave it like it is 🙂

This is fixed in the latest package.

We use the persona theme https://github.com/NodeBB/nodebb-theme-persona with its defaults as far as I can tell. That theme is already the default though.

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

Thank you.

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

@smokeyfro I've just released a new app package which fixes yarn usage, can you see if this also fixed your problem? You may have to refresh your browser though.

@girish looks like nodebb self healed. The 'broken' state it was in is not broken anymore. This is good news 🙂

@briankb-0 said in Stop Forum Spam:

one for Discourse in development?

In my (admittedly relatively limited) experience Discourse does a pretty good a preventing spam all by itself (e.g. newly reg'd users can't post links etc)

And doing a curl does return the ghost.js file:

$ curl -L https://forum.cloudron.space/plugins/nodebb-plugin-blog-comments/lib/ghost.js (function() { "use strict"; var articlePath = window.location.protocol + '//' + window.location.host + window.location.pathname; var pluginURL = nbb.url + '/plugins/nodebb-plugin-blog-comments', savedText, nodebbDiv, contentDiv, commentsDiv, commentsCounter, commentsAuthor, commentsCategory; var stylesheet = document.createElement("link"); stylesheet.setAttribute("rel", "stylesheet"); stylesheet.setAttribute("type", "text/css"); stylesheet.setAttribute("href", pluginURL + '/css/comments.css'); ...

The version of the plugin installed is 0.8.6