NodeBB Assets - Object Storage

phenomlab

@baris Tried those, and landed up hosing my DEV environment have had to remove this plugin. I'll try it again at some point, but it's way more complex than it should be in my view sadly.

PitaJ

The CDN plugin uses redirects. It doesn't need the nginx stuff, that's just optimization. (nginx is much better at a simple redirect rule than nodejs) I'm not sure exactly what you're doing in the browser console but it's likely you will still get initial requests to your NodeBB domain, especially if your cache is disabled like the browser tools often does when open.

phenomlab

@PitaJ thanks, but the "redirects" don't seem to work. After making changes to nginx it completely skewered my forum and I had to use the cli to disable.

PitaJ

@phenomlab yeah I'd get it working without nginx first. What exactly do you see in your browser network tab?

phenomlab

@PitaJ the origin URL which is odd as I'd expect the redirect to show up.

phenomlab

@baris Any ideas to to how I can remove the entries for this plugin or at least remove the tick that enables the redirect? I've uninstalled and reinstalled it, but the forum crashes and I can't make any changes.

PitaJ

@phenomlab try clearing your cache. You can deactivate the plugin with ./nodebb reset -p @nodebb/nodebb-plugin-cdn

phenomlab

@PitaJ thanks. I've used that command on the cli to disable which seems to work fine but removing and reinstalling seems to retain the existing values.

phenomlab

@PitaJ clearing the cache doesn't work - neither does an incognito tab. Looks like the value has to be removed from the database, or perhaps a way of leaving the plugin active but disabling the redirect

<baris>

You can delete this key from the database 'plugin_cdn:settings'

phenomlab

@baris is there a specific command in MongoDB to remove this?

<baris>

db.objects.remove({_key: "plugin_cdn:settings"});

phenomlab

@baris thanks

phenomlab

@baris @PitaJ even stripping my Dev config back to just NodeBB with no nginx, it still doesn't work. All that happens is that the plugin crashes the admin console. Can't see any real reason for this in the logs either

PitaJ

@phenomlab what does crashing the admin console look like? And if you had any CDN stuff in your nginx config you'll need to clear you're cache again. Try a different browser if you haven't already.

The CDN plugin doesn't store anything in the database except for the settings key you've already deleted. You will need to restart NodeBB after deleting the key in order for that to take effect.

phenomlab

@PitaJ It looks like this

6Fetch finished loading: GET "<URL>".
admin:46          GET https://sudonix.dev/assets/plugins/nodebb-plugin-markdown/styles/obsidian.css net::ERR_ABORTED 404
18Fetch failed loading: GET "<URL>".
admin:45          GET https://sudonix.dev/assets/plugins/nodebb-plugin-emoji/emoji/styles.css?v=kccgr37fq3g net::ERR_ABORTED 404
admin:49          GET https://sudonix.dev/assets/admin.css?v=kccgr37fq3g net::ERR_ABORTED 404
admin:61          GET https://sudonix.dev/assets/admin.min.js?v=kccgr37fq3g net::ERR_ABORTED 404
admin:987 Uncaught ReferenceError: $ is not defined
    at HTMLDocument.prepareFooter (admin:987:4)
prepareFooter @ admin:987
13The FetchEvent for "<URL>" resulted in a network error response: the promise was rejected.
service-worker.js:14          Uncaught (in promise) TypeError: Failed to fetch
    at service-worker.js:14:11
(anonymous) @ service-worker.js:14
service-worker.js:14          Uncaught (in promise) TypeError: Failed to fetch
    at service-worker.js:14:11
(anonymous) @ service-worker.js:14
service-worker.js:14          Uncaught (in promise) TypeError: Failed to fetch
    at service-worker.js:14:11
(anonymous) @ service-worker.js:14
service-worker.js:14          Uncaught (in promise) TypeError: Failed to fetch
    at service-worker.js:14:11
(anonymous) @ service-worker.js:14
service-worker.js:14          Uncaught (in promise) TypeError: Failed to fetch
    at service-worker.js:14:11
(anonymous) @ service-worker.js:14
service-worker.js:14          Uncaught (in promise) TypeError: Failed to fetch
    at service-worker.js:14:11
(anonymous) @ service-worker.js:14
service-worker.js:14          Uncaught (in promise) TypeError: Failed to fetch
    at service-worker.js:14:11
(anonymous) @ service-worker.js:14
service-worker.js:14          Uncaught (in promise) TypeError: Failed to fetch
    at service-worker.js:14:11
(anonymous) @ service-worker.js:14
service-worker.js:14          Uncaught (in promise) TypeError: Failed to fetch
    at service-worker.js:14:11
(anonymous) @ service-worker.js:14
service-worker.js:14          Uncaught (in promise) TypeError: Failed to fetch
    at service-worker.js:14:11
(anonymous) @ service-worker.js:14
service-worker.js:14          Uncaught (in promise) TypeError: Failed to fetch
    at service-worker.js:14:11
(anonymous) @ service-worker.js:14
service-worker.js:14          Uncaught (in promise) TypeError: Failed to fetch
    at service-worker.js:14:11
(anonymous) @ service-worker.js:14
service-worker.js:14          Uncaught (in promise) TypeError: Failed to fetch
    at service-worker.js:14:11
(anonymous) @ service-worker.js:14
admin:34          GET https://sudonix.dev/assets/src/modules/composer.js?v=kccgr37fq3g net::ERR_FAILED
admin:35          GET https://sudonix.dev/assets/src/modules/composer/uploads.js?v=kccgr37fq3g net::ERR_FAILED
admin:36          GET https://sudonix.dev/assets/src/modules/composer/drafts.js?v=kccgr37fq3g net::ERR_FAILED
admin:37          GET https://sudonix.dev/assets/src/modules/composer/tags.js?v=kccgr37fq3g net::ERR_FAILED
admin:38          GET https://sudonix.dev/assets/src/modules/composer/categoryList.js?v=kccgr37fq3g net::ERR_FAILED
admin:39          GET https://sudonix.dev/assets/src/modules/composer/resize.js?v=kccgr37fq3g net::ERR_FAILED
admin:40          GET https://sudonix.dev/assets/src/modules/composer/autocomplete.js?v=kccgr37fq3g net::ERR_FAILED
admin:41          GET https://sudonix.dev/assets/templates/composer.tpl?v=kccgr37fq3g net::ERR_FAILED
admin:42          GET https://sudonix.dev/assets/language/en-GB/topic.json?v=kccgr37fq3g net::ERR_FAILED
admin:46          GET https://sudonix.dev/assets/plugins/nodebb-plugin-markdown/styles/obsidian.css net::ERR_FAILED
admin:44          GET https://sudonix.dev/assets/language/en-GB/tags.json?v=kccgr37fq3g net::ERR_FAILED
admin:43          GET https://sudonix.dev/assets/language/en-GB/modules.json?v=kccgr37fq3g net::ERR_FAILED
admin:47          GET https://sudonix.dev/assets/language/en-GB/markdown.json?v=kccgr37fq3g net::ERR_FAILED
touchicon-144.png:1          GET https://sudonix.dev/assets/uploads/system/touchicon-144.png 404
admin:1 Error while trying to use the following icon from the Manifest: https://sudonix.dev/assets/uploads/system/touchicon-144.png (Download error or resource isn't a valid image)

The site can no longer be loaded. I see traffic building on the CDN, but even with removing NGINX and just using NodeJS to serve the site, it's the same. The site is not rendered correctly, and I see a stack of errors in the console

One of particular interest is this

(blocked:NotSameOrigin)

The odd thing is that I'm pretty sure I enabled this in terms of CORS settings.

I've tried 5 different browsers and they all do the same thing.

phenomlab

What's more odd here is that the critical js files NodeBB needs are not being redirected to the CDN - see

Whereas others are

More concerning is that the assets still pointing to the origin server are now serving a 404

I think there is an issue with this plugin which prevents it from working correctly.

PitaJ

Yeah looks like I'll need to take another look at it in action. Maybe the upgrade Baris did changed something it wasn't supposed to. Unfortunately I'm away on vacation at the moment.

phenomlab

@PitaJ no problem at all. Thanks

phenomlab

@baris @PitaJ any plans to look into why this plugin does not work ?