@julian Thank you , this is helpful.

I tried a reckless approach.
First, I migrated the database (mongodb).
Then, I directly copy all the files on the original server to the new server
Finally, modify the uri variable in config.json.
So far it looks successful. . .
Hahaha

I have a question. Does nodebb have a website migration scheme? If I want to move my website from one server to another, what should I do?

@baris

Thank you. I will try and feed back new information.

@baris
ubuntu@VM-0-9-ubuntu:~/app/NodeBB$ ./nodebb plugins
2022-02-05T02:09:46.453Z [4567/1782233] - verbose: [minifier] utilizing a maximum of 1 additional threads
Active plugins:
* [email protected] (installed, disabled)
* [email protected] (installed, enabled)
* [email protected] (installed, enabled)
* [email protected] (installed, enabled)
* [email protected] (installed, enabled)
* [email protected] (installed, enabled)
* [email protected] (installed, enabled)
* [email protected] (installed, disabled)
* [email protected] (installed, disabled)
* [email protected] (installed, disabled)
* [email protected] (installed, disabled)
* [email protected] (installed, disabled)
* [email protected] (installed, disabled)
* [email protected] (installed, disabled)
* [email protected] (installed, enabled)
* [email protected] (installed, disabled)
* [email protected] (installed, disabled)
* [email protected] (installed, enabled)

I successfully installed nodebb a week ago and it has been working well. However, I just found an error while looking at the log file.
This seems to be a database related error. The database I use is mongodb.
The following is the output:

2022-02-03T04:23:26.872Z [4567/1383602] - error: GET /topic/53/windows%E4%B8%8B%E5%AE%89%E8%A3%85mysql8
TypeError: Cannot read properties of undefined (reading 'length')
at /home/ubuntu/app/NodeBB/src/database/index.js:17:24
at Array.forEach (<anonymous>)
at Object.primaryDB.parseIntFields (/home/ubuntu/app/NodeBB/src/database/index.js:16:12)
at /home/ubuntu/app/NodeBB/src/user/data.js:184:7
at Array.map (<anonymous>)
at modifyUserData (/home/ubuntu/app/NodeBB/src/user/data.js:179:27)
at User.getUsersFields (/home/ubuntu/app/NodeBB/src/user/data.js:82:9)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at async User.getUsersData (/home/ubuntu/app/NodeBB/src/user/data.js:145:10)
at async User.getUserData (/home/ubuntu/app/NodeBB/src/user/data.js:140:17)
(node:1383602) PromiseRejectionHandledWarning: Promise rejection was handled asynchronously (rejection id: 2)
(Use node --trace-warnings ... to show where the warning was created)
2022-02-03T04:23:26.876Z [4567/1383602] - warn: [plugins] filter:user.whitelistFields already resolved in plugin nodebb-plugin-sso-beer-qq
2022-02-03T04:23:26.876Z [4567/1383602] - info: [app] Live analytics saved.
2022-02-03T04:23:26.881Z [4567/1383602] - error: uncaughtException: Cannot read properties of undefined (reading 'length')
TypeError: Cannot read properties of undefined (reading 'length')
at /home/ubuntu/app/NodeBB/src/database/index.js:17:24
at Array.forEach (<anonymous>)
at Object.primaryDB.parseIntFields (/home/ubuntu/app/NodeBB/src/database/index.js:16:12)
at /home/ubuntu/app/NodeBB/src/user/data.js:184:7
at Array.map (<anonymous>)
at modifyUserData (/home/ubuntu/app/NodeBB/src/user/data.js:179:27)
at User.getUsersFields (/home/ubuntu/app/NodeBB/src/user/data.js:82:9)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at async User.getUsersData (/home/ubuntu/app/NodeBB/src/user/data.js:145:10)
at async User.getUserData (/home/ubuntu/app/NodeBB/src/user/data.js:140:17) {"date":"Thu Feb 03 2022 12:23:26 GMT+0800 (China Standard Time)","error":{},"exception":true,"os"

After install "nodebb-plugin-sso-beer-qq", my server crashed and nginx return code 502.

After reset all plugins, my server is back to normal again.

Finally, to make a summary, I met a strange problem when building nodebb: when I write a post, the uploaded pictures can be displayed normally, but the picture links cannot be displayed.
The solution is to set "cross origin embed policy" to the state shown in the following figure:

However, there is another strange problem. When you use "www.domain. Org" to access, you can display pictures normally, but when you use "domain. org", you still can't display pictures.
You can configure nginx to make "domain. org" jump to "www.domain. Org" through 301。

Welcome to my station, ahoh.club，Thank nodebb, thank Mr. cat(baris).

I know why the picture won't show.

If I enter my domain name in the address bar of the browser: "ahoh. club", the picture disappears.

However, if I enter "www.ahoh. Club" in the address bar of the browser, the picture can be displayed normally.

Thank you very much for your guidance！
@baris

I I followed @baris 's instructions and modified the setting of Cross-origin-Embedder-Policy. Now I can browse pictures with my mobile phone and tablet.
However, the edge and chrome browsers on my computer still can't use image links.
At the same time, I have an interesting discovery. When I delete the edge cookie, the picture can be displayed.
However, when I refresh the page, the picture disappears again.
In other words, as long as there is a cookie, the picture cannot be displayed normally in chrome. Why?
I think I'm close to the truth.

@baris It works in my tablet, but doesn’t appear in my computer. Is it caused by different browsers。

@baris I disabled this option and restart nodebb, but it doesn't work too.

@baris I tried this method and restart nodebb in dashboard, but it doesn't work,Should I change other options?

@baris I am in the latest version 1.19.1, there is no errors when I compile source code .

When I try to insert an image link in a post, the image cannot be displayed. As shown in the figure below:

I'm sure that the picture link is accessible, and there are some errors in the browser.

What should I do to fix these bugs？

Thanks.

I successfully installed nodebb on the server yesterday. It's great.

Welcome to my forum.
ahoh.club