Technical Support

Rp1 This is my docker-compose.yaml file services: nodebb: build: . restart: unless-stopped container_name: nodebb default: ports: - '4567:4567' # comment this out if you don't want to expose NodeBB to the host, or change the first number to any port you want volumes: - ./nodebb/nodebb-build:/usr/src/app/build - ./nodebb/nodebb-uploads:/usr/src/app/public/uploads - ./nodebb/nodebb-config:/opt/config - setup.json:/usr/src/app/setup.json postgres: image: postgres:17.5-alpine restart: unless-stopped environment: POSTGRES_USER: nodebb POSTGRES_PASSWORD: nodebb POSTGRES_DB: nodebb volumes: - ./postgres/postgres-data:/var/lib/postgresql/data This is my Dockerfile FROM ghcr.io/nodebb/nodebb:latest # Install NodeBB plugins # Add the plugins you want to use here RUN npm install \ nodebb-plugin-cards \ nodebb-plugin-link-preview \ nodebb-plugin-tenor-gif # Expose the default NodeBB port EXPOSE 4567 # The base image should already have the appropriate CMD/ENTRYPOINT Just run docker compose up -d and you should have the forum up and the entire data should be in the directory itself. You can then just share the directory itself with anybody and they will have the exact setup running. NOTE: You’ll have to manually create the file setup.json under ./nodebb/install/docker/ BEFORE starting it ,You can get the file from Github here

Ashutosh-Verma Thanks for your advice. Will save Time during Update. If you want add healthcheck to your nodebb Docker, visit: https://forum.its-egner.de/topic/4581/nodebb-healthcheck And here the Update Script with all of my Plugins for Ubuntu 24 git fetch git reset --hard origin/v4.x chown -R 1001:1001 .docker public docker-compose -f docker-compose-orgi.yml build docker-compose -f docker-compose-orgi.yml up -d docker exec -i nodebb-nodebb-1 npm install \ nodebb-plugin-embed \ nodebb-plugin-math-captcha \ nodebb-plugin-embed \ nodebb-plugin-emoji-android \ nodebb-plugin-google-analytics \ nodebb-plugin-sso-google \ nodebb-plugin-tenor-gif Greetings

With the Lemmy developers’ help, we figured it out! It was NodeBB’s spam protection mechanism. One of our configurable options is to limit the number of upvotes one can make per day. Someone (or someones) on Lemmy communities was sending lots of upvotes and running into this limitation when those activities were propagated to NodeBB. NodeBB dutifully noted this and sent back an HTTP 500. Lemmy dutifully noted this and retried sending the activity using an exponential backoff algorithm Eventually enough 500s were recorded that Lemmy decided that our server needed a time-out of sorts I updated the code to handle this case better, and now the activities are coming in at full speed. It’ll take awhile to get back up to sync though

phenomlab ah good to hear, thanks, and sorry about that! We’re not quite sure what happened with the eslint update that caused existing installs to complain so loudly.

malte@forum.fedi.dk sort of. Mastodon from a design standpoint doesn’t want to implement inline images, and I understand their point of view. The point of the Note preview is to provide an alternative format that Mastodon can better understand.

Okay, so disabling HSTS and flushing my browser cache again brought remote images back. It’s obvious that I need to crack into the ideal way to configure these things for the Fediverse, might have to replicate how some of my other Fediverse platforms are set up on the Nginx side.

M1hono you can create a new category and check the box to treat it as a section.

Teemberland thanks for letting me know!

baris Thank you, Changing this setting indeed solved the problem (I don’t understand what the purpose of this setting is and what it’s used for, in my opinion it’s completely unnecessary)

May 20 11:48:25 its-egner.de systemd[1]: var-lib-docker-overlay2-d16b141610897bf49aa9efaa03c501d004a532c7030698d06435f1feaf240f6a-merged.mount: Deactivated successfully. May 20 11:48:25 its-egner.de dockerd[380014]: time="2025-05-20T11:48:25.487585934+02:00" level=error msg="Handler for POST /v1.42/containers/create returned error: failed to populate volume: error while mounting volume '/var/lib/docker/volumes/nodebb_nodebb-build/_data': failed to mount local volume: mount ./.docker/build:/var/lib/docker/volumes/nodebb_nodebb-build/_data, flags: 0x1000: no such file or directory" services: nodebb: build: . # image: ghcr.io/nodebb/nodebb:latest restart: unless-stopped ports: - '4568:4567' # comment this out if you don't want to expose NodeBB to the host, or change the first number to any port you want volumes: - nodebb-build:/usr/src/app/build - nodebb-uploads:/usr/src/app/public/uploads - nodebb-config:/opt/config - ./install/docker/setup.json:/usr/src/app/setup.json volumes: nodebb-build: driver: local driver_opts: o: bind type: none device: /root/nodebb/.docker/build nodebb-uploads: driver: local driver_opts: o: bind type: none device: /root/nodebb/.docker/public/uploads nodebb-config: driver: local driver_opts: o: bind type: none device: /root/nodebb/.docker/config

@julian @support @trwnh @thisismissem @puppygirlhornypost2 No, metadata is a free-form object, according to the spec, so people put random stuff there. I originally discovered metadata.federation.enabled via Pleroma, which famously has rich NodeInfo: https://lain.com/nodeinfo/2.1.json

[image: 1746617929686-5d23ad8d-c0db-49f6-b067-957474ebcaa4-image.png] In general, I did not find a solution, so I stupidly changed the original template (by the way, after updating the Harmony theme, my topic.tpl file was not updated).

Im running Node 23 on my production install

Since we are using https://github.com/Psifi-Solutions/csrf-sync it creates a session whenever a guest loads the forum to set config.csrf_token. Although we used that in 3.7.0 as well so not sure if that’s your issue or not. Sessions are also created for guests if you turn on “Allow guests to increase topic view counts”, to track which topics they’ve viewed.

@malte@forum.fedi.dk yes, because you are using NodeBB. It will send the activity to as many people as it possibly can, who have any relation to the topic.