I don't get it to work. I have checked the source code. The fix from @julian Commit 55ab85a is in my code. I have rebuild & restart NodeBB several times.

I think i don't have understand how it works. What i must do exactly to mentioned a category. In settings i has three servers and i have checked Use this as an Allow List instead.

Now i will post from my account @[email protected] to my forum https://radforum-duesseldorf.de/world. That works all fine. But i need that when i mentioned a category that my NodeBB Forum will send it to this category. How i must mentioned it? I have test it in all possible options.

When i mentioned it

@[email protected] 

it won't work. Same with only

@radfahren 

So, what i am doing wrong. Please help.

Where is your 443 server block?

 server {
     listen               443 ssl http2;

I do my first steps with activity pub. It looks like a really interesting piece of software.

Now i can follow some user and so on. Works fine.

Next i will, when i post on the Fediverse that this post landed in an category (NodeBB).

In documentation i find this.

Whether a remote user can create a topic in that category by mentioning it

So i send this post.

#ActivityPub Testing

@Radfahren

Now i think that this post will be move to the category Radfahren

The post will only be landed in /world.

What i do wrong?

I don't find the setup very intuitive. I wasn't aware that I had to follow someone—that wasn't clear to me. Maybe this could be mentioned somewhere in the settings. Otherwise, it works now, and I'll take a closer look at it. I'll be happy to share my thoughts on it in the coming days.

Thank you @julian First try is working.

Do we have a documentation how to use #activitypub on my own nodebb instance?

Same here, problem solved. Thank you @julian

For me it looks like a misconfiguration certificate

~/nodebb$ openssl s_client -connect packages.nodebb.org:443
CONNECTED(00000003)
depth=2 C = US, O = Internet Security Research Group, CN = ISRG Root X1
verify return:1
depth=1 C = US, O = Let's Encrypt, CN = R11
verify return:1
depth=0 CN = otherhome.ca
verify return:1
---
Certificate chain
 0 s:CN = otherhome.ca
   i:C = US, O = Let's Encrypt, CN = R11
   a:PKEY: rsaEncryption, 2048 (bit); sigalg: RSA-SHA256
   v:NotBefore: Sep 30 11:40:17 2024 GMT; NotAfter: Dec 29 11:40:16 2024 GMT
 1 s:C = US, O = Let's Encrypt, CN = R11
   i:C = US, O = Internet Security Research Group, CN = ISRG Root X1
   a:PKEY: rsaEncryption, 2048 (bit); sigalg: RSA-SHA256
   v:NotBefore: Mar 13 00:00:00 2024 GMT; NotAfter: Mar 12 23:59:59 2027 GMT
---
Server certificate
-----BEGIN CERTIFICATE-----
MIIE+TCCA+GgAwIBAgISBKFrGq/uYt1x2fT4nxpBycwnMA0GCSqGSIb3DQEBCwUA
MDMxCzAJBgNVBAYTAlVTMRYwFAYDVQQKEw1MZXQncyBFbmNyeXB0MQwwCgYDVQQD
EwNSMTEwHhcNMjQwOTMwMTE0MDE3WhcNMjQxMjI5MTE0MDE2WjAXMRUwEwYDVQQD
EwxvdGhlcmhvbWUuY2EwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCx
QM9xk/KQ/V60FHRXJywIpVnbmH8PNDSHMGx5XIEHdiw035J+DFySEkuXYdlgV8tH
fENKbIMz+Ydy2sr9aniOZ469QrU/IS2pQn+qM51rvMLrgG7Jj4rqT0DHPTWg+bPK
hyDHSipG7OfI2MeSL5FCJ8reZJHgidU3M+TE7oEaS6vbtIzAgR96SNtv5HQHzjkp
3f7iLtoY9Dg2O4aSEwqqz6GhwlgVwQTOok43YWR0IP99ZKm1xplh7Zaa8rwybD3u
jEE7MjxDz3A7Dz9nNOXlZz37qywh4Z3SUD4T/FPT0vxqiHoqZ/sn+arKiWHmL2Rq
RNGqu3SdXUQ/V4kg/euhAgMBAAGjggIhMIICHTAOBgNVHQ8BAf8EBAMCBaAwHQYD
VR0lBBYwFAYIKwYBBQUHAwEGCCsGAQUFBwMCMAwGA1UdEwEB/wQCMAAwHQYDVR0O
BBYEFNK/bs9ALNV6hDhxJuBzFuPOiN7WMB8GA1UdIwQYMBaAFMXPRqTq9MPAemyV
xC2wXpIvJuO5MFcGCCsGAQUFBwEBBEswSTAiBggrBgEFBQcwAYYWaHR0cDovL3Ix
MS5vLmxlbmNyLm9yZzAjBggrBgEFBQcwAoYXaHR0cDovL3IxMS5pLmxlbmNyLm9y
Zy8wKQYDVR0RBCIwIIIMb3RoZXJob21lLmNhghB3d3cub3RoZXJob21lLmNhMBMG
A1UdIAQMMAowCAYGZ4EMAQIBMIIBAwYKKwYBBAHWeQIEAgSB9ASB8QDvAHYAPxdL
T9ciR1iUHWUchL4NEu2QN38fhWrrwb8ohez4ZG4AAAGSQvDDVgAABAMARzBFAiEA
4mux6bwlRhkod0w2lpnEDzptWExR/w/edW/E5KqdHxsCIE+eSuU0VZ0BJScxH/a1
XVjRbSXVv1mh7es6d8MAZQ0KAHUA7s3QZNXbGs7FXLedtM0TojKHRny87N7DUUhZ
RnEftZsAAAGSQvDDYAAABAMARjBEAiBitznteh8jOf0ouYy+0zGgb2Ertk+sqZBv
cakVejJdrQIgbDdaOcdeCL0CBAWtqlyTSlZ5WMuAag7CZz+Gd4+s4zgwDQYJKoZI
hvcNAQELBQADggEBAFtg1wIruQmPeWYoLZsFu1AXci01qCMWkIsYnXydayz9zZkn
2T1BO3e6UJUK4N96hQx0zOjAAnNf9o7Ky87ZX/ttImFNKwuJyzy7cxvrtNC5NFn2
0bt6R6ui4fFSO4px2h/7W6WBTnpoILYGpAxbi/7U8lOC8wSrROw/YCiy33sCqiqk
xi8GBQv7kod1lVTdG/f3X6EgHT4T+yXhP+KXMecoqXUl7j8Z+ELdqC1ogW1hDDNR
2usRzqAzxToavls5+zgeFosck9TqaehFLRSBgpZTlb824DjdXOaGg3+YOWtg/Ic5
gjdW9XlAYHsckwD0FErnr1EGEGWt/XFm2KMGHRM=
-----END CERTIFICATE-----
subject=CN = otherhome.ca
issuer=C = US, O = Let's Encrypt, CN = R11
---
No client certificate CA names sent
Peer signing digest: SHA256
Peer signature type: RSA-PSS
Server Temp Key: X25519, 253 bits
---
SSL handshake has read 3132 bytes and written 405 bytes
Verification: OK
---
New, TLSv1.3, Cipher is TLS_AES_256_GCM_SHA384
Server public key is 2048 bit
Secure Renegotiation IS NOT supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
Early data was not sent
Verify return code: 0 (ok)
---
---
Post-Handshake New Session Ticket arrived:
SSL-Session:
    Protocol  : TLSv1.3
    Cipher    : TLS_AES_256_GCM_SHA384
    Session-ID: 0BAEE2E2596998FC051D88FA1D1A25EC671CC10D574E024DDE532762AF16A452
    Session-ID-ctx: 
    Resumption PSK: 5D8F0A9B82234EE41941D62904135FD72E4CBE4B7F0A8840504ACF7AFD1C452BDEBFB92FC5C3516C5E7582644D470DD5
    PSK identity: None
    PSK identity hint: None
    SRP username: None
    TLS session ticket lifetime hint: 86400 (seconds)
    TLS session ticket:
    0000 - c7 21 33 b9 cb a3 fb 39-3f 07 98 90 16 a1 dd 8f   .!3....9?.......
    0010 - ed bd 1a 29 fb dc 9e 46-56 ee 48 f8 f7 b6 24 00   ...)...FV.H...$.

    Start Time: 1728584237
    Timeout   : 7200 (sec)
    Verify return code: 0 (ok)
    Extended master secret: no
    Max Early Data: 0
---
read R BLOCK
---
Post-Handshake New Session Ticket arrived:
SSL-Session:
    Protocol  : TLSv1.3
    Cipher    : TLS_AES_256_GCM_SHA384
    Session-ID: 983BC3E889B11EFEB5782F6868276B49BBD14DF3B2C34EE453DCB79D0CBBC687
    Session-ID-ctx: 
    Resumption PSK: 0863E2FBD0E12E927F148560BC426747A03996188C8E0FE3F03AD6C7F8722BD53346145A27630C3B981CC58010B860EB
    PSK identity: None
    PSK identity hint: None
    SRP username: None
    TLS session ticket lifetime hint: 86400 (seconds)
    TLS session ticket:
    0000 - 91 78 a8 cc 5e a5 a5 fd-f4 44 d2 cb ed 75 d1 05   .x..^....D...u..
    0010 - 7c 8b f3 1a 38 78 a1 25-94 e0 1a a9 27 3d 47 cd   |...8x.%....'=G.

    Start Time: 1728584237
    Timeout   : 7200 (sec)
    Verify return code: 0 (ok)
    Extended master secret: no
    Max Early Data: 0
---
read R BLOCK
closed

This certificate is owned by bolded textsubject=CN = otherhome.ca

@julian Yes i do. My location is germany.

I got

~/nodebb$ dig packages.nodebb.org

; <<>> DiG 9.18.28-1~deb12u2-Debian <<>> packages.nodebb.org
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 50858
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;packages.nodebb.org.           IN      A

;; ANSWER SECTION:
packages.nodebb.org.    300     IN      A       138.197.166.38

;; Query time: 12 msec
;; SERVER: 185.12.64.2#53(185.12.64.2) (UDP)
;; WHEN: Wed Oct 09 21:42:10 CEST 2024
;; MSG SIZE  rcvd: 64

Same problem.

3. Checking installed plugins for updates...Checking installed plugins and themes for updates... Warning: An unexpected error occured when attempting to verify plugin upgradability
Error occurred during upgrade: TypeError: fetch failed
    at node:internal/deps/undici/undici:13185:13
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async call (/home/user_radforum/nodebb/src/request.js:37:19)
    at async getSuggestedModules (/home/user_radforum/nodebb/src/cli/upgrade-plugins.js:78:27)
    at async checkPlugins (/home/user_radforum/nodebb/src/cli/upgrade-plugins.js:101:27)
    at async upgradePlugins (/home/user_radforum/nodebb/src/cli/upgrade-plugins.js:125:17)
    at async Object.handler (/home/user_radforum/nodebb/src/cli/upgrade.js:29:4)
    at async runSteps (/home/user_radforum/nodebb/src/cli/upgrade.js:55:5)
    at async Object.runUpgrade [as upgrade] (/home/user_radforum/nodebb/src/cli/upgrade.js:98:3)
2024-10-09T19:00:50.732Z [4568/271155] - error: uncaughtException: fetch failed
TypeError: fetch failed
    at node:internal/deps/undici/undici:13185:13
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async call (/home/user_radforum/nodebb/src/request.js:37:19)
    at async getSuggestedModules (/home/user_radforum/nodebb/src/cli/upgrade-plugins.js:78:27)
    at async checkPlugins (/home/user_radforum/nodebb/src/cli/upgrade-plugins.js:101:27)
    at async upgradePlugins (/home/user_radforum/nodebb/src/cli/upgrade-plugins.js:125:17)
    at async Object.handler (/home/user_radforum/nodebb/src/cli/upgrade.js:29:4)
    at async runSteps (/home/user_radforum/nodebb/src/cli/upgrade.js:55:5)

My nodebb version is 3.9 and i try to update to 3.10.1

Thank you. Nice work.

@Jakub-Urbanowicz

This works for me on Debian 12.

/etc/systemd/system/nodebb.service

[Unit]
Description=NodeBB
Documentation=https://docs.nodebb.org
After=system.slice multi-user.target mongod.service

[Service]
Type=forking
User=<USER>

StandardOutput=syslog
StandardError=syslog
SyslogIdentifier=nodebb

WorkingDirectory=/home/<USER>/nodebb
PIDFile=/home/<USER>/nodebb/pidfile
ExecStart=/usr/bin/node loader.js
Restart=always

[Install]
WantedBy=multi-user.target

I use redis for a long time.

In redis.conf

 ################################ SNAPSHOTTING  ################################
 save 900 1
 save 300 10
 save 60 10000
 
dbfilename dump.rdb

# The working directory.
#
# The DB will be written inside this directory, with the filename specified
# above using the 'dbfilename' configuration directive.
#
# The Append Only File will also be created inside this directory.
#
# Note that you must specify a directory here, not a file name.
dir /var/lib/redis

And be sure to start the server with the correct config. The correct user rights are also important!

In newer Redis versions something might have changed in the configuration file, please read carefully. This is excellently documented.

ExecStart=/usr/bin/redis-server /etc/redis/redis.conf --supervised systemd --daemonize no

I somehow got it to v3.3.5 now. Please do not ask how I'm thinking about reinstalling to start cleanly.

Ok, git pull works

~/nodebb$ git pull
remote: Enumerating objects: 475, done.
remote: Counting objects: 100% (475/475), done.
remote: Compressing objects: 100% (231/231), done.
remote: Total 475 (delta 248), reused 469 (delta 244), pack-reused 0
Receiving objects: 100% (475/475), 417.93 KiB | 13.06 MiB/s, done.
Resolving deltas: 100% (248/248), completed with 54 local objects.
From https://github.com/NodeBB/NodeBB
   7d9ff9bf4e..d36140eb5f  develop    -> origin/develop
   c44ddb10e7..055762e69e  master     -> origin/master
   638e098f30..dc14d6a8d1  v2.x       -> origin/v2.x
 * [new tag]               v2.8.17    -> v2.8.17
 * [new tag]               v3.3.5     -> v3.3.5

My other forum show this

~/nodebb$ git pull
hint: You have divergent branches and need to specify how to reconcile them.
hint: You can do so by running one of the following commands sometime before
hint: your next pull:
hint: 
hint:   git config pull.rebase false  # merge
hint:   git config pull.rebase true   # rebase
hint:   git config pull.ff only       # fast-forward only
hint: 
hint: You can replace "git config" with "git config --global" to set a default
hint: preference for all repositories. You can also pass --rebase, --no-rebase,
hint: or --ff-only on the command line to override the configured default per
hint: invocation.
fatal: Need to specify how to reconcile divergent branches.

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

On another forum, i got nothing when i do

git fetch

~/nodebb$ git fetch
remote: Enumerating objects: 9, done.
remote: Counting objects: 100% (9/9), done.
remote: Compressing objects: 100% (3/3), done.
remote: Total 9 (delta 6), reused 9 (delta 6), pack-reused 0
Unpacking objects: 100% (9/9), 904 bytes | 75.00 KiB/s, done.
From https://github.com/NodeBB/NodeBB
   05a7c7610d..d36140eb5f  develop    -> origin/develop
   fb43f9ae10..dc14d6a8d1  v2.x       -> origin/v2.x
~/nodebb$ git reset --hard origin/v3.x
HEAD is now at a67f84ea5b chore: incrementing version number - v3.3.4

Ok, i think you are working.

@baris Works. Thank you!