eeeee This usually happens when AdSense injects scripts before NodeBB finishes loading its own client files. The service worker fails to register and chat breaks for logged-in users. Try limiting AdSense to guests only or exclude the chat route from the plugin. If the problem disappears, you can report it to the plugin author to adjust the script order so it doesn’t block NodeBB’s core JS.
Twissell This usually happens when AdSense injects scripts before NodeBB finishes loading its own client files. The service worker fails to register and chat breaks for logged-in users. Try limiting AdSense to guests only or exclude the chat route from the plugin. If the problem disappears, you can report it to the plugin author to adjust the script order so it doesn’t block NodeBB’s core JS.
drukob@feddit.org Self hosting is cool right up until the server goes bzzt during peak hours 😂. And then you’re standing there poking at your terminal while people ask why the POS “isn’t in the mood today”. Been there. Zero stars. Would not recommend.
LWSH6688 It’s likely a UI side regression rather than a storage issue, since the frontend still renders the filenames correctly. Check that the admin page is actually being served with UTF 8 headers, then compare the output with the filename shown in the database to confirm it is only a display layer problem. If everything matches, open a GitHub issue with your environment info, because this looks like something the core team will need to patch in the 4.6 admin interface.
big_steve Yes, it’s doable. You can load the 3.2.3 dump into a clean 4.6.1 install and let NodeBB handle the schema changes on startup. It will detect the older database and migrate everything automatically. Many people have moved from 3.x to 4.x using this approach, so as long as the backup is good and MongoDB 7 is configured correctly, it works fine.
Kadir-Ay-0 You can only control this through a dedicated plugin or custom module. Discourse doesn't have a native setting for limiting active sessions per user, but the discourse-auth-tokens plugin allows you to view and revoke sessions, which is the closest thing you're looking for.
That definitely sounds like a conflict between the AdSense script and NodeBB's service worker registration. You could try lazy-loading the AdSense JS or excluding it from the scope of the service worker
For Minecraft plus some docker stuff, I'd skip OpenVZ and go for KVM. I've been running mine on mvps.net for a while now, their basic plans are cheap, and you get instant setup in multiple EU locations. The performance jump compared to budget OpenVZ is night and day.
The meme is real for a lot of people, but mine gets used. I’m in Australia on a DeskUp dual-motor with a hardwood top. Stand for calls or light work, sit for deep focus. It’s less about "burn calories" and more about posture resets and dialing the seated height right. Cable tray means one lead out, so zero spaghetti.
Adding a community sounds like a cool idea! NodeBB could work since it’s pretty user-friendly and has good plugins for spam control. Another simple option might be Discourse—it’s a bit heavier but also great for keeping things organized and spam-free. Just make sure to have moderation tools or maybe require users to register before posting to keep spam down.
I’ve seen this happen sometimes when there’s a problem with permissions or a plugin conflict. Maybe try checking your NodeBB logs for errors when you click save? Also, make sure your Auth0 app settings match exactly what the plugin needs (like callback URLs).
eeeee This usually happens when AdSense injects scripts before NodeBB finishes loading its own client files. The service worker fails to register and chat breaks for logged-in users. Try limiting AdSense to guests only or exclude the chat route from the plugin. If the problem disappears, you can report it to the plugin author to adjust the script order so it doesn’t block NodeBB’s core JS.
Twissell This usually happens when AdSense injects scripts before NodeBB finishes loading its own client files. The service worker fails to register and chat breaks for logged-in users. Try limiting AdSense to guests only or exclude the chat route from the plugin. If the problem disappears, you can report it to the plugin author to adjust the script order so it doesn’t block NodeBB’s core JS.
drukob@feddit.org Self hosting is cool right up until the server goes bzzt during peak hours 😂. And then you’re standing there poking at your terminal while people ask why the POS “isn’t in the mood today”. Been there. Zero stars. Would not recommend.
LWSH6688 It’s likely a UI side regression rather than a storage issue, since the frontend still renders the filenames correctly. Check that the admin page is actually being served with UTF 8 headers, then compare the output with the filename shown in the database to confirm it is only a display layer problem. If everything matches, open a GitHub issue with your environment info, because this looks like something the core team will need to patch in the 4.6 admin interface.
big_steve Yes, it’s doable. You can load the 3.2.3 dump into a clean 4.6.1 install and let NodeBB handle the schema changes on startup. It will detect the older database and migrate everything automatically. Many people have moved from 3.x to 4.x using this approach, so as long as the backup is good and MongoDB 7 is configured correctly, it works fine.
Kadir-Ay-0 You can only control this through a dedicated plugin or custom module. Discourse doesn't have a native setting for limiting active sessions per user, but the discourse-auth-tokens plugin allows you to view and revoke sessions, which is the closest thing you're looking for.
It’s 100% the og:image. You’ve got to refresh the cache manually with the debugger tools or clear it in your CDN if you’re using one.
That definitely sounds like a conflict between the AdSense script and NodeBB's service worker registration. You could try lazy-loading the AdSense JS or excluding it from the scope of the service worker
For Minecraft plus some docker stuff, I'd skip OpenVZ and go for KVM. I've been running mine on mvps.net for a while now, their basic plans are cheap, and you get instant setup in multiple EU locations. The performance jump compared to budget OpenVZ is night and day.
The meme is real for a lot of people, but mine gets used. I’m in Australia on a DeskUp dual-motor with a hardwood top. Stand for calls or light work, sit for deep focus. It’s less about "burn calories" and more about posture resets and dialing the seated height right. Cable tray means one lead out, so zero spaghetti.
For Minecraft plus some docker stuff, I'd skip OpenVZ and go for KVM.
Adding a community sounds like a cool idea! NodeBB could work since it’s pretty user-friendly and has good plugins for spam control. Another simple option might be Discourse—it’s a bit heavier but also great for keeping things organized and spam-free. Just make sure to have moderation tools or maybe require users to register before posting to keep spam down.
I’ve seen this happen sometimes when there’s a problem with permissions or a plugin conflict. Maybe try checking your NodeBB logs for errors when you click save? Also, make sure your Auth0 app settings match exactly what the plugin needs (like callback URLs).
I can’t help but bring up this topic again because it’s really important for anyone thinking about reporting wrongdoing.