Is there an official 'Solved' option?

NodeHam

Nothing in the logs, no errors anywhere, rebooted the server, restarted nodebb, no matter what we do, cannot get in. This is happening from multiple sites and now we see it's also happening from our Linux desktops and Windows too.

No idea what's going on and wish I could provide more info but not sure what to look for.

<baris>

What is the url of your forum?

NodeHam

I'd rather not post is publicly but would share it with a moderator/admin.

NodeHam

I was able to see some information in the inspection window. Maybe this helps.

Chromeum;

Refused to apply style from 'https://my.domain.com.com/assets/plugins/nodebb-plugin-emoji/emoji/styles.css?v=458fane8fda' because its MIME type ('text/html') is not a supported stylesheet MIME type, and strict MIME checking is enabled.
VM105:10 Uncaught ReferenceError: require is not defined
    at HTMLDocument.prepareFooter (VM105:10:9)
nodebb.min.js?v=458fane8fda:9 ServiceWorker registration succeeded.
6post-queue.282afa2be9a276fbee08.min.js:1 Uncaught TypeError: Cannot read properties of null (reading 'getAttribute')
    at HTMLDivElement.<anonymous> (post-queue.282afa2be9a276fbee08.min.js:1:2176)
topic-1683141428639:1 Refused to apply style from 'https://my.domain.com/assets/plugins/nodebb-plugin-emoji/emoji/styles.css?v=458fane8fda' because its MIME type ('text/html') is not a supported stylesheet MIME type, and strict MIME checking is enabled.
3post-queue.282afa2be9a276fbee08.min.js:1 Uncaught TypeError: Cannot read properties of null (reading 'getAttribute')
    at HTMLDivElement.<anonymous> (post-queue.282afa2be9a276fbee08.min.js:1:2176)
(

Firefox;
GET
https://my.domain.com/assets/plugins/nodebb-plugin-emoji/emoji/styles.css?v=458fane8fda
The resource from “https://my.domain.com/assets/plugins/nodebb-plugin-emoji/emoji/styles.css?v=458fane8fda” was blocked due to MIME type (“text/html”) mismatch (X-Content-Type-Options: nosniff).
Uncaught ReferenceError: require is not defined
    prepareFooter https://my.domain.com/post-queue/topic-1683141428639:632
    EventListener.handleEvent* https://my.domain.com/post-queue/topic-1683141428639:625
topic-1683141428639:632:9

So this looks like it could be fixed by changing some directives in nginx but before I do that, it is nodebb being bad or the config 'suddenly' being bad since it's been fine for something like two years now.

phenomlab

@NodeHam Can you explain the below line in your nginx.conf? have you tried to remove that?

location /viewtopic.php { return 410; }

NodeHam

If I recall, that's a redirection of 410 because the boards used to be phpbb and had those links. This option lets search engines know that those no longer exist.
That would not cause this problem but I tested, removed it and it's the same.

NodeHam

BTW, the board also shows that someone registered and is waiting to be approved but when I go there, there is no one waiting to be approved. It's like it's slowly breaking or something.

<baris>

VM105:10 Uncaught ReferenceError: require is not defined
    at HTMLDocument.prepareFooter (VM105:10:9)

What's in your custom JS tab? Looks like you have some js errors as well.

NodeHam

This, which was given to me in another post;

.categories .category-children, .category .category-children, .subcategory .category-children {
display: grid;
}

PitaJ

@NodeHam that's custom CSS, not custom js

NodeHam

Oops, sorry, too many things at once.

require(['hooks'], function (hooks) {
hooks.on('action:search.quick.start', function (params) {
params.searchOptions.in = 'titlesposts';
});
hooks.on('action:search.submit', function (params) {
params.searchOptions.in = 'titlesposts';
});
});

PitaJ

@NodeHam yeah you'll need to update that js eventually but for now, just disable custom JS and see if that helps.

NodeHam

Been trying to 10 minutes and getting 'forbidden'. Once I get in, I'll disable that and see what happens.

NodeHam

Got it disabled but no change. The very odd thing is I can see the post needing to be accepted as a mod but as the admin, it's not there.

NodeHam

BTW, I cleared the cache after disabling the code.

When I click on that as an admin;

Reg type is already set to admin approval.

NodeHam

Days now and still cannot accept a post we needed to respond to. Not sure what to do about this. Very much at a loss if the problem is something on my end or with the nodebb software corrupting.

phenomlab

@NodeHam Feel free to contact me on sudonix.com if you'd like me to take a look at this issue to see if we can get it resolved. Obviously, I'll need site details etc, but you can share that over PM.

NodeHam

Are you with nodebb? I mean, I don't want to take up your time if this is a nodebb problem.

The board worked fine for a long time and this slowly started to happen. I noticed many months ago that sometimes I could not log in and thought it might only be a multi-session issue, cache or other browser issue but as you know, it's gotten to this after I recently updated.

phenomlab

@NodeHam I'm not, no - I'm independent. However, seeing as nobody else seems to have this issue, I don't think it's a NodeBB issue, but more than happy to help.

NodeHam

That's truly kind of you. If we can solve it, maybe we can update the post to let anyone else that comes across this know how it was fixed. I'll PM you shortly.