1.19.3 Support Thread

kurulumu.Net

@phenomlab After Hetzner made the switch, interesting things started to happen. For example, port 465 is closed for security by default Standard update commands didn't work for me. It's really weird.

phenomlab

@kurulumu-Net Very odd indeed. As you know, I'm a Hetzner customer myself, and am not experiencing these issues. Admittedly, I do not use port 465, but 587

Aleksei

I have a similar problem with upgrade. Performing it as usual:

git reset --hard origin/v1.19.3
fatal: ambiguous argument 'origin/v1.19.3': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'

PitaJ

@Aleksei you're supposed to do literally

git reset --hard origin/v1.19.x

Aleksei

@PitaJ I was following the offical guide:

So in this case the brach name is origin/v1.19.3 or origin/v1.19.x ?

volanar

@Aleksei git reset --hard origin/v1.19.x

julian

@Aleksei The branch name is v1.19.x, the remote is origin (that's the default, unless you've changed it)

So git reset origin/v1.19.x says "git, please change my working directory to match the latest commits on the v1.19.x branch"

If you want to reset to a specific VERSION, then you don't need the remote. git reset --hard v1.19.3 should work fine.

Aleksei

Thank you for the detailed reply! I was confused by the examples in the documentation.

Andrey

Hello! Broken links and hints (1.19.3)

I have replaced one icon in the menu. After that, unformatted template text appeared in the title, tooltips, and links. The category names also have a strange display of some characters.

Updating the markdown plugin to version 9.0.8 didn't help. Rebuilding the frontend didn't help either.

Please tell me how to fix

Andrey

@Andrey

The problem is global

julian

@Andrey Try replacing all of the [ to [ and ] to ]

Those are language keys, they shouldn't be escaped into html entities.

Andrey

@julian I changed "popular" to [[global:header.popular]] and it works! Thanks!

But when I re-enter this section of the settings, all the fields again take the form:

&lsqb;&lsqb;global:header.popular&rsqb;&rsqb;

I'm also not sure that this can't affect service addresses, including

Andrey

@julian Also I see the problem from this thread

crazycells

our update to 1.19.3 from 1.18.6 failed...

forum has language problems... and this is the log:


Clustering enabled: Spinning up 3 process(es).

2022-02-27T03:30:48.522Z [4567/2929] - [32minfo[39m: Initializing NodeBB v1.19.3 https://yesilkartforum.com/forum
2022-02-27T03:30:52.524Z [4568/2935] - [32minfo[39m: [socket.io] Restricting access to origin: https://yesilkartforum.com:*
2022-02-27T03:30:52.740Z [4569/2936] - [32minfo[39m: [socket.io] Restricting access to origin: https://yesilkartforum.com:*
2022-02-27T03:30:53.071Z [4567/2929] - [32minfo[39m: [socket.io] Restricting access to origin: https://yesilkartforum.com:*
2022-02-27T03:30:53.585Z [4568/2935] - [32minfo[39m: [plugins/spam-be-gone] Settings loaded
2022-02-27T03:30:53.633Z [4568/2935] - [32minfo[39m: [api] Adding 0 route(s) to `api/v3/plugins`
2022-02-27T03:30:53.737Z [4568/2935] - [32minfo[39m: [router] Routes added
2022-02-27T03:30:53.741Z [4569/2936] - [32minfo[39m: [plugins/spam-be-gone] Settings loaded
2022-02-27T03:30:53.800Z [4568/2935] - [32minfo[39m: NodeBB Ready
2022-02-27T03:30:53.817Z [4568/2935] - [32minfo[39m: Enabling 'trust proxy'
2022-02-27T03:30:53.828Z [4568/2935] - [32minfo[39m: NodeBB is now listening on: 0.0.0.0:4568
2022-02-27T03:30:53.916Z [4569/2936] - [32minfo[39m: [api] Adding 0 route(s) to `api/v3/plugins`
2022-02-27T03:30:53.957Z [4569/2936] - [32minfo[39m: [router] Routes added
2022-02-27T03:30:53.965Z [4569/2936] - [32minfo[39m: NodeBB Ready
2022-02-27T03:30:53.967Z [4569/2936] - [32minfo[39m: Enabling 'trust proxy'
2022-02-27T03:30:53.970Z [4569/2936] - [32minfo[39m: NodeBB is now listening on: 0.0.0.0:4569

2022-02-27T03:30:54.072Z [4567/2929] - [33mwarn[39m: [plugins/load] The following plugins may not be compatible with your version of NodeBB. This may cause unintended behaviour or crashing. In the event of an unresponsive NodeBB caused by this plugin, run `./nodebb reset -p PLUGINNAME` to disable it.
  * nodebb-plugin-calendar
  * nodebb-plugin-twitter

2022-02-27T03:30:54.203Z [4567/2929] - [32minfo[39m: [plugins/spam-be-gone] Settings loaded
2022-02-27T03:30:54.283Z [4567/2929] - [32minfo[39m: [api] Adding 0 route(s) to `api/v3/plugins`
2022-02-27T03:30:54.296Z [4567/2929] - [32minfo[39m: [router] Routes added
2022-02-27T03:30:54.307Z [4567/2929] - [32minfo[39m: NodeBB Ready
2022-02-27T03:30:54.310Z [4567/2929] - [32minfo[39m: Enabling 'trust proxy'
2022-02-27T03:30:54.312Z [4567/2929] - [32minfo[39m: NodeBB is now listening on: 0.0.0.0:4567
  started
2022-02-27T03:31:26.286Z [4568/2935] - [32minfo[39m: [build] Building in series mode
2022-02-27T03:31:26.287Z [4568/2935] - [32minfo[39m: [build]         plugin static dirs  build started
2022-02-27T03:31:26.304Z [4568/2935] - [32minfo[39m: [build]         plugin static dirs  build completed in 0.017sec
2022-02-27T03:31:26.304Z [4568/2935] - [32minfo[39m: [build]          requirejs modules  build started
2022-02-27T03:31:33.553Z [4568/2935] - [32minfo[39m: [build]          requirejs modules  build completed in 7.248sec
2022-02-27T03:31:33.553Z [4568/2935] - [32minfo[39m: [build]           client js bundle  build started
2022-02-27T03:31:36.274Z [4568/2935] - [32minfo[39m: [build]           client js bundle  build completed in 2.721sec
2022-02-27T03:31:36.282Z [4568/2935] - [32minfo[39m: [build]            admin js bundle  build started
2022-02-27T03:31:39.209Z [4568/2935] - [32minfo[39m: [build]            admin js bundle  build completed in 2.927sec
2022-02-27T03:31:39.209Z [4568/2935] - [32minfo[39m: [build]         client side styles  build started
2022-02-27T03:31:44.383Z [4568/2935] - [32minfo[39m: [build]         client side styles  build completed in 5.174sec
2022-02-27T03:31:44.383Z [4568/2935] - [32minfo[39m: [build] admin control panel styles  build started
2022-02-27T03:31:47.562Z [4568/2935] - [32minfo[39m: [build] admin control panel styles  build completed in 3.179sec
2022-02-27T03:31:47.562Z [4568/2935] - [32minfo[39m: [build]                  templates  build started
[benchpress] warning: output bloat due to ambiguous inner BEGIN
     --> admin/plugins/canned-responses.tpl:44:17
      |
   44 | 						<!-- BEGIN responses -->
      | 						           ^^^^^^^^^ `responses` could refer to the top-level value `responses` or the `.responses` property of the current element, so compiler must emit code for both cases
      | note: Migrate to modern syntax to avoid the ambiguity. This will become an error in the future.

2022-02-27T03:31:48.434Z [4568/2935] - [32minfo[39m: [build]                  templates  build completed in 0.872sec
2022-02-27T03:31:48.434Z [4568/2935] - [32minfo[39m: [build]                  languages  build started
2022-02-27T03:31:49.055Z [4568/2935] - [31merror[39m: [build]                  languages  build failed
2022-02-27T03:31:49.055Z [4568/2935] - [31merror[39m: [build] Encountered error during build step
Error: EMFILE: too many open files, open '/home/fsuzer/nodebb/public/language/sc/admin/manage/tags.json'
2022-02-27T03:31:49.055Z [4568/2935] - [31merror[39m: admin.reload
Error: EMFILE: too many open files, open '/home/fsuzer/nodebb/public/language/sc/admin/manage/tags.json'
Missing translation "language:dir" for language "en-GB"
Missing translation "global:500.title" for language "en-GB"
Missing translation "global:500.message" for language "en-GB"
Missing translation "error:goback" for language "en-GB"
Missing translation "global:guest" for language "en-GB"
Missing translation "global:guest" for language "en-GB"
Missing translation "global:guest" for language "en-GB"
Missing translation "global:header.search" for language "en-GB"
Missing translation "global:search" for language "en-GB"
Missing translation "global:login" for language "en-GB"
Missing translation "language:dir" for language "en-GB"
Missing translation "global:500.title" for language "en-GB"
Missing translation "global:500.message" for language "en-GB"
Missing translation "error:goback" for language "en-GB"
Missing translation "global:guest" for language "en-GB"
Missing translation "global:guest" for language "en-GB"
Missing translation "global:guest" for language "en-GB"
Missing translation "global:header.search" for language "en-GB"
Missing translation "global:search" for language "en-GB"
Missing translation "global:login" for language "en-GB"
Missing translation "language:dir" for language "en-GB"
Missing translation "global:500.title" for language "en-GB"
Missing translation "global:500.message" for language "en-GB"
Missing translation "error:goback" for language "en-GB"
Missing translation "global:guest" for language "en-GB"
Missing translation "global:guest" for language "en-GB"
Missing translation "global:guest" for language "en-GB"
Missing translation "global:header.search" for language "en-GB"
Missing translation "global:search" for language "en-GB"
Missing translation "global:login" for language "en-GB"
Missing translation "language:dir" for language "en-GB"
Missing translation "pages:maintenance.text" for language "en-GB"
Missing translation "pages:maintenance.messageIntro" for language "en-GB"
Missing translation "global:500.title" for language "en-GB"
Missing translation "global:500.message" for language "en-GB"
Missing translation "error:goback" for language "en-GB"
Missing translation "global:guest" for language "en-GB"
Missing translation "global:guest" for language "en-GB"
Missing translation "global:guest" for language "en-GB"
Missing translation "global:header.search" for language "en-GB"
Missing translation "global:search" for language "en-GB"
Missing translation "global:login" for language "en-GB"
Missing translation "language:dir" for language "en-GB"

crazycells

additionally, we are having this problem while trying to install extended-markdown plugin...

2022-02-27T05:50:26.207Z [4568/1274] - [31merror[39m: admin.plugins.toggleInstall
Error: Command failed: npm install [email protected] --save
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/nodebb-plugin-markdown
npm ERR!   nodebb-plugin-markdown@"9.0.8" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer nodebb-plugin-markdown@"8.x" from [email protected]
npm ERR! node_modules/nodebb-plugin-extended-markdown
npm ERR!   nodebb-plugin-extended-markdown@"1.5.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /home/fsuzer/.npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/fsuzer/.npm/_logs/2022-02-27T05_50_23_241Z-debug-0.log

    at ChildProcess.exithandler (node:child_process:399:12)
    at ChildProcess.emit (node:events:520:28)
    at maybeClose (node:internal/child_process:1092:16)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:302:5)
    at Process.callbackTrampoline (node:internal/async_hooks:130:17)

Logs Control Panel

<baris>

@crazycells said in 1.19.3 Support Thread:

2022-02-27T03:31:49.055Z [4568/2935] - [31merror[39m: [build] Encountered error during build step
Error: EMFILE: too many open files, open '/home/fsuzer/nodebb/public/language/sc/admin/manage/tags.json'
2022-02-27T03:31:49.055Z [4568/2935] - [31merror[39m: admin.reload
Error: EMFILE: too many open files, open '/home/fsuzer/nodebb/public/language/sc/admin/manage/tags.json'

This error happens because of limits in the OS, check the open file limit with ulimit -Hn & ulimit -Sn and increase it if its too low. https://linuxhint.com/increase-open-file-limit-ubuntu/

crazycells

@baris thanks.

any idea how to install the extended-markdown plugin without error? we had to remove all of them to prevent errors, all but this one was OK to re-install...

crazycells

after upgrading to 1.19.3 , we have many of this "Error: revalidate-failure" errors in the log...

is this temporary?

2022-02-28T00:23:56.361Z [4569/1454] - [31merror[39m: plugins.browsingUsers.getBrowsingUsers
Error: revalidate-failure
    at validateSession (/home/fsuzer/nodebb/src/socket.io/index.js:209:9)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at onMessage (/home/fsuzer/nodebb/src/socket.io/index.js:153:3)
2022-02-28T00:23:57.806Z [4569/1454] - [31merror[39m: plugins.browsingUsers.getBrowsingUsers
Error: revalidate-failure
    at validateSession (/home/fsuzer/nodebb/src/socket.io/index.js:209:9)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at onMessage (/home/fsuzer/nodebb/src/socket.io/index.js:153:3)
2022-02-28T00:24:00.932Z [4569/1454] - [31merror[39m: plugins.browsingUsers.getBrowsingUsers
Error: revalidate-failure
    at validateSession (/home/fsuzer/nodebb/src/socket.io/index.js:209:9)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at onMessage (/home/fsuzer/nodebb/src/socket.io/index.js:153:3)
2022-02-28T00:26:40.360Z [4569/1454] - [31merror[39m: notifications.getCount
Error: revalidate-failure
    at validateSession (/home/fsuzer/nodebb/src/socket.io/index.js:209:9)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at onMessage (/home/fsuzer/nodebb/src/socket.io/index.js:153:3)
2022-02-28T00:26:40.393Z [4569/1454] - [31merror[39m: notifications.getCount
Error: revalidate-failure
    at validateSession (/home/fsuzer/nodebb/src/socket.io/index.js:209:9)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at onMessage (/home/fsuzer/nodebb/src/socket.io/index.js:153:3)
2022-02-28T00:26:41.431Z [4569/1454] - [31merror[39m: notifications.getCount
Error: revalidate-failure
    at validateSession (/home/fsuzer/nodebb/src/socket.io/index.js:209:9)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at onMessage (/home/fsuzer/nodebb/src/socket.io/index.js:153:3)
2022-02-28T00:26:41.433Z [4569/1454] - [31merror[39m: notifications.getCount
Error: revalidate-failure
    at validateSession (/home/fsuzer/nodebb/src/socket.io/index.js:209:9)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at onMessage (/home/fsuzer/nodebb/src/socket.io/index.js:153:3)
2022-02-28T00:26:41.434Z [4569/1454] - [31merror[39m: notifications.getCount
Error: revalidate-failure
    at validateSession (/home/fsuzer/nodebb/src/socket.io/index.js:209:9)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at onMessage (/home/fsuzer/nodebb/src/socket.io/index.js:153:3)
2022-02-28T00:26:41.435Z [4569/1454] - [31merror[39m: notifications.getCount
Error: revalidate-failure
    at validateSession (/home/fsuzer/nodebb/src/socket.io/index.js:209:9)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at onMessage (/home/fsuzer/nodebb/src/socket.io/index.js:153:3)
2022-02-28T00:26:41.435Z [4569/1454] - [31merror[39m: notifications.getCount
Error: revalidate-failure
    at validateSession (/home/fsuzer/nodebb/src/socket.io/index.js:209:9)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at onMessage (/home/fsuzer/nodebb/src/socket.io/index.js:153:3)
2022-02-28T00:26:41.437Z [4569/1454] - [31merror[39m: notifications.getCount
Error: revalidate-failure
    at validateSession (/home/fsuzer/nodebb/src/socket.io/index.js:209:9)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at onMessage (/home/fsuzer/nodebb/src/socket.io/index.js:153:3)
2022-02-28T00:26:41.437Z [4569/1454] - [31merror[39m: notifications.getCount
Error: revalidate-failure
    at validateSession (/home/fsuzer/nodebb/src/socket.io/index.js:209:9)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at onMessage (/home/fsuzer/nodebb/src/socket.io/index.js:153:3)

julian

@crazycells That depends... the revalidate-failure error suggests that a server-side session was not found. Could happen if the redis server was flushed or something, and existing browser tabs attempt to use the site.

As long as your users aren't reporting errors, it's likely temporary.

jminer

@baris We've got an issue that on mobile a 99+ notifications will show on the hamburger menu on mobile even though notifications should be on the right side now. A refresh makes it go away, but it comes back.

Right now I'm just suppressing the notification with custom CSS.

/*Disable 99+ on mobile*/
.navbar-toggle#mobile-menu .unread-count::after {
    display: none;
}

Also any way to change the default selection on the right swipe out? It would make more sense for it to go to notifications first instead of the user profile.