Hello! How can I change default category watch state to watching for specific administrator? Is it possible to do with plugin? [image: 1710754317243-firefox_screenshot_2024-03-18t09-21-36.411z.png]

Not sure when exactly this started to happen, but I now get broken images on my site - for example [image: 1720021017180-7aaa6a6c-0331-4a4e-81cd-2f3d4cb06bff-image.png] According to the console, the original attachment is suffixed with -resized but I do not see a corresponding file, so the render fails. /assets/uploads/files/1656084919400-blurred-resized.png does not exist, but /assets/uploads/files/1656084919400-blurred.png does. Any ideas? Currently running 3.8.3. Whilst not the same topic, there seems to be a relationship in the form of resized with this topic https://community.nodebb.org/topic/12052/resized-images-are-sometimes-larger-than-before?_=1719996905071

You know what they say about standards... https://xkcd.com/927/ Very soon after NodeBB started, we built in support for some of the major SSO providers through plugins like nodebb-plugin-sso-facebook and nodebb-plugin-sso-google. For all other SSO providers, the ecosystem grew over time with the addition of other NodeBB plugins like nodebb-plugin-oidc-connect or various other bespoke implementations. Outside of those, our recommendation was to fork out the sso-oauth plugin and make your own changes. I ended up making this template repository because each individual SSO implementation, despite being some variant of OAuth2, had its own intricacies that made it impossible to create a single plugin to cover all cases. Since then... A number of things have changed in the past ten years, namely the rise of hosted CRM services with built-in SSO/IAM components, the solidification of OpenID as the de facto standard for SSO, and the decline of OAuth in favour of OAuth2. We've reached a point where it is safe to assume that a user attempting to implement an SSO bridge with NodeBB would be: Using OAuth2. Not rolling out their own OAuth2 compatible provider, but instead using a hosted service or common library ... and to that end, we're able to build a plugin that encompasses most of the common configuration cases. https://github.com/NodeBB/nodebb-plugin-sso-oauth2-multiple/ From within this plugin, you are able to configure the details for each OAuth2 provider: [image: configure.png?raw=true] If your OAuth2 provider supports the .well-known configuration route, you can simply populate the "domain" field and some of the remaining fields will be automatically filled out. Due to an additional client ask, this plugin has even been updated so that you are able to add multiple OAuth2 providers, should you want to! Testing This plugin has been tested against both Auth0 and Okta.

Agenda preparation for the November ForumWG meeting can be found at this public link (anyone can make comments for review.) Monthly meetings are held on the first Thursday of each month, at 1700 to 1800 UTC. You can find them listed in the SocialCG Calendar. The next meeting will be held on 7 November 2024. We will be continuing onwards with: discussions regarding context resolution. Multiple FEPs touch on the subject and there is an opportunity for potential convergence towards a single (or pair) of FEPs that share enough commonalities to allow for interoperability. updates by WG members re: non-as:Note support in Mastodon and the Social CG report draft whether a resolvable context collection containing plain objects should also contain activities (like an outbox) As always — time permitting — if you'd like to speak or inquire about a certain topic, comment in the agenda or reply here, the floor is open!

NodeBB Hover Cards I made a little thing. This plugin adds a little feature to the mentions plugin. With this enabled, you can hover over a mention and view some information about the mentioned user. Screenshot [image: wdBOeLY.png] Install npm install nodebb-plugin-cards Source https://github.com/Schamper/nodebb-plugin-cards

Hello there, I am late to the party finally upgrading from 1.19 to 3.x. My board is using a custom OAuth2 login and needs syncing username and email changes into NodeBB. So far I was using the write-api plugin (PUT /api/v2/users/<id>) which is deprecated now. The API docs don´t show that username or email can be changed. But via testing I figured out that username change is working fine. But I had no success on changing the email. Is there any way to do so? (Additional info: I am using the master token and impersonate the board admin with user id 1) Might also relate to an earlier unanswered question here.

Related to the ForumWG topic of resolvable context collections, there are four FEPs that are currently in consideration: FEP-7888: Demystifying the context property FEP-400e: Publicly-appendable ActivityPub collections Draft FEP-171b: Conversation Containers, an evolution of Conversation Containers FEP-76ea: Conversation Threads @[email protected] made a suggestion last month to hopefully reduce the number of moving parts: Both FEP-400e and FEP-1b12 implementations: support FEP-7888 (context collection) FEP-400e implementations: upgrade to Conversation Containers FEP-1b12 implementations: add target property to Announce activity that points to context collection. This takes FEP 400e out of the running (potentially). But the day after that last meeting, @[email protected] put together FEP 76ea, and now we're back to three. My concern is that all three FEPs (7888, 171b, and 76ea) all share these distinct qualities: They establish a conversational context for a given object They federate out an Add on collection addition. (76ea also sends Remove) They contain some concept of a context owner (attributedTo) They differ on the following qualities: 7888/171b use context whereas 76ea uses a new property thr:thread 171b specifies a new object type Context Collection items: 7888 sends objects in chronological order 171b sends activities in chronological order 76ea sends objects in reverse chronological order In the lead up to the November WG meeting I'd like to address those differences. All three FEPs are in pre-draft or draft stages, and so I am hoping we can find some common ground and compromise. Pinging interested parties (who were not already mentioned above) for comment: @[email protected] @[email protected] @[email protected] @[email protected]

I've read the NodeBB API documentation, and I'd like to use the 'https://community.nodebb.org/api/post/upload' route to upload images for creating or replying to posts. However, I've been encountering failures, sometimes it's a 403 error, and sometimes it's an 'invalid-files' error. I'm using Python to write this script. Can someone provide a simple example? Thank you very much!

Hi, I have been having a nightmare updating mongod and nodebb. My developer had successfully migrated nodebb to a new server with latest mongod and nodebb version , we migrated old data from old server to new server, all was good till yesterday but today there seems to be few issues. Site not loading for users. Yesterday users were complaining that imagemagick was not working so he disabled it. as users were unable to upload profile pics and i was not able to save admin changes. now whenever i run nodebb, on live site i get socket io 403 forbidden. I have read your posts here so its not origin url error since its happening on main url too https://chatrooms.talkwithstranger.com but i m temporarily redirecting to another page as users r having bad experience seeing broken site, you can see nodebb on this url i have read ur posts here https://github.com/NodeBB/NodeBB/issues/5472 so its not this issue. its something else. @baris @julian I did so many things but nothing worked, below i m providing you details. root@Himalaya-New:/var/www/community# cat package.json | grep version "version": "3.10.0", "compare-versions": "6.1.1", root@Himalaya-New:/var/www/community# root@Himalaya-New:/var/www/community# mongod --version db version v6.0.17 Build Info: { "version": "6.0.17", "gitVersion": "1b0ca02043c6d35d5cfdc91e21fc00a05d901539", "openSSLVersion": "OpenSSL 3.0.13 30 Jan 2024", "modules": [], "allocator": "tcmalloc", "environment": { "distmod": "ubuntu2204", "distarch": "x86_64", "target_arch": "x86_64" } } Live url was https://chatrooms.talkwithstranger.com but because its down i am redirecting users to another page temporarily. 403 forbidden coming on socket io. yes i am using cloudflare but IP don't go through CF, right then why 403 forbidden? [image: 1728739819423-79d7151e-6b97-4dbd-97c2-25ef6a46fe5c-image-resized.png] Below are some history commands of what i tried so far but no luck. 1999 cd "/var/www/community" 2000 ./nodebb log 2001 sudo systemctl status mongod 2002 ./nodebb log 2003 ./nodebb restart 2004 ./nodebb log 2005 sudo systemctl restart mongod 2006 sudo systemctl status mongod 2007 ./nodebb log 2008 ./nodebb stop 2009 ./nodebb start 2010 ./nodebb log 2011 sudo tail -f /var/log/mongodb/mongod.log 2012 mongo 2013 mongod 2014 ps aux | grep mongod 2015 docker ps 2016 docker stop 86b913d8a821 2017 mongod 2018 sudo systemctl restart mongod 2019 mongo 2020 mongod 2021 ./nodebb log 2022 ./nodebb restart 2023 ./nodebb log 2024 sudo systemctl status mongod 2025 sudo systemctl stop mongod 2026* sudo systemctl start nongo 2027 sudo systemctl stop mongod 2028 sudo systemctl start mongod 2029 sudo systemctl status mongod 2030 sudo cat /var/log/mongodb/mongod.log 2031 df -h 2032 sudo systemctl start mongod 2033 sudo systemctl status mongod 2034* 2035 sudo systemctl status mongod 2036 sudo systemctl start mongod 2037 sudo systemctl status mongod 2038 sudo less /var/log/mongodb/mongod.log 2039 mongod 2040 sudo chown -R mongodb:mongodb /var/lib/mongodb 2041 sudo chown -R mongodb:mongodb /var/log/mongodb 2042 sudo systemctl start mongod 2043 sudo systemctl status mongod 2044 sudo systemctl stop mongod 2045 sudo systemctl start mongod 2046 sudo systemctl status mongod 2047 mongod 2048 sudo systemctl restart mongod 2049 sudo systemctl status mongod 2050 mongod 2051 ls -ld /var/lib/mongodb 2052 sudo chown -R mongodb:mongodb /var/lib/mongodb 2053 sudo systemctl start mongod 2054 sudo systemctl status mongod 2055 sudo less /var/log/mongodb/mongod.log 2056 sudo systemctl stop mongod 2057 sudo truncate -s 0 /var/log/mongodb/mongod.log 2058 sudo systemctl start mongod 2059 sudo systemctl status mongod 2060 sudo less /var/log/mongodb/mongod.log 2061 ps aux | grep mongod 2062 sudo kill 1126153 2063 ps aux | grep mongod 2064 sudo kill 1283446 2065 ps aux | grep mongod 2066 sudo pkill mongod 2067 ps aux | grep mongod 2068 ps aux | grep [m]ongod 2069 ./nodebb stop 2070 sudo kill -9 1283897 2071 sudo systemctl stop mongod 2072 ps aux | grep [m]ongod 2073 sudo less /var/log/mongodb/mongod.log 2074 ls -l /tmp/mongodb-27017.sock 2075 sudo rm /tmp/mongodb-27017.sock 2076 ls -ld /tmp 2077 sudo chown -R mongodb:mongodb /var/lib/mongodb 2078 sudo chown -R mongodb:mongodb /var/log/mongodb 2079 sudo systemctl start mongod 2080 sudo systemctl status mongod 2081 ./nodebb start 2082 ./nodebb log 2083 sudo systemctl status mongod 2084 ./nodebb log 2085 ./nodebb stop 2086 ./nodebb start 2087 ./nodebb stop 2088 ./nodebb start 2089 ./nodebb log 2090 mongo --host localhost --port 27017 2091 sudo less /var/log/mongodb/mongod.log 2092 sudo truncate -s 0 /var/log/mongodb/mongod.log 2093 sudo less /var/log/mongodb/mongod.log 2094 ./nodebb stop 2095 sudo less /var/log/mongodb/mongod.log 2096 sudo truncate -s 0 /var/log/mongodb/mongod.log 2097 sudo less /var/log/mongodb/mongod.log 2098 ./nodebb start 2099 sudo less /var/log/mongodb/mongod.log 2100 clear 2101 sudo less /var/log/mongodb/mongod.log 2102 ./nodebb log 2103 ./nodebb stop 2104 ./nodebb start 2105 ./nodebb log 2106 ./nodebb stop 2107 ls -l /tmp/mongodb-27017.sock 2108 ls -ld /tmp 2109 ./nodebb restart 2110 mongod 2111 history 2112 sudo systemctl status mongod 2113 sudo systemctl restart mongod 2114 sudo systemctl status mongod 2115 mongod 2116 sudo nano /lib/systemd/system/mongodb.service 2117 mongod --config /etc/mongod.conf 2118 systemctl status mongodb 2119 sudo nano /lib/systemd/system/mongodb.service 2120 sudo nano /etc/systemd/system/mongodb.service 2121 sudo systemctl stop mongodb 2122 sudo systemctl stop mongod 2123 sudo systemctl start mongod 2124 sudo systemctl statusmongod 2125 sudo systemctl status mongod 2126 mongod 2127 sudo chown -R mongodb:mongodb /var/lib/mongodb 2128 sudo systemctl start mongod 2129 sudo systemctl status mongod 2130 cat /var/log/mongodb/mongod.log 2131 sudo systemctl start mongod 2132 sudo systemctl status mongod 2133 sudo journalctl -u mongod.service -b 2134 mongod --config /etc/mongod.conf --syslog --fork 2135 sudo ls -l /var/log/mongodb/mongod.log 2136 sudo mongod --config /etc/mongod.conf --fork 2137 sudo systemctl start mongod 2138 sudo systemctl status mongod 2139 sudo tail -n 50 /var/log/mongodb/mongod.log 2140 sudo ls -l /tmp/mongodb-27017.sock 2141 ls -ld /tmp 2142 sudo rm /tmp/mongodb-27017.sock 2143 sudo systemctl start mongod 2144 sudo systemctl status mongod 2145 sudo tail -n 50 /var/log/mongodb/mongod.log 2146 ps aux | grep mongod 2147 sudo systemctl status mongod 2148 sudo systemctl restart mongod 2149 sudo systemctl status mongod 2150 [200~sudo killall mongod 2151 ~sudo pkill mongod 2152 sudo pkill mongod 2153 ps aux | grep mongod 2154 sudo killall mongod 2155 ps aux | grep mongod 2156 sudo systemctl start mongod 2157 sudo systemctl status mongod 2158 sudo less /var/log/mongodb/mongod.log 2159 sudo systemctl stop mongod 2160 sudo truncate -s 0 /var/log/mongodb/mongod.log 2161 sudo chown mongodb:mongodb /var/log/mongodb/mongod.log 2162 sudo systemctl start mongod 2163 sudo systemctl status mongod 2164 sudo less /var/log/mongodb/mongod.log 2165 ls -ld /var/lib/mongodb 2166 ls -l /var/lib/mongodb 2167 sudo chown mongodb:mongodb /var/lib/mongodb/WiredTiger.turtle 2168 sudo chown -R mongodb:mongodb /var/lib/mongodb 2169 sudo systemctl start mongod 2170 sudo systemctl status mongod 2171 ./nodebb status 2172 ./nodebb start 2173 ./nodebb log 2174 sudo systemctl status mongod 2175 mongod 2176 sudo lsof -i :27017 2177 ./nodebb log 2178 ./nodebb stop 2179 ./nodebb log 2180 docker ps 2181 Then check what is using 9001 using telnet and kill that processs 2182 sudo lsof -i :9001 2183 ./nodebb stop 2184 sudo systemctl status mongod 2185 sudo truncate -s 0 /var/log/mongodb/mongod.log 2186 sudo systemctl restart mongod 2187 sudo systemctl status mongod 2188 mongod 2189 ls -ld /tmp /var/lib/mongodb 2190 sudo rm -f /tmp/mongodb-27017.sock 2191 df -h 2192 mongod --config /etc/mongod.conf --verbose 2193 sudo systemctl status mongod 2194 sudo systemctl start mongod 2195 sudo systemctl status mongod 2196 sudo systemctl start mongod 2197 ls -ld /var/lib/mongodb 2198 sudo chown -R mongodb:mongodb /var/lib/mongodb 2199 sudo chmod 755 /var/lib/mongodb 2200 ps aux | grep mongod 2201 sudo systemctl start mongod 2202 sudo systemctl status mongod 2203 sudo systemctl restart mongod 2204 sudo systemctl status mongod 2205 ./nodebb log 2206 ./nodebb status 2207 ./nodebb start 2208 ./nodebb status 2209 ./nodebb log 2210 sudo systemctl status mongod 2211 sudo systemctl restart mongod 2212 sudo systemctl status mongod 2213 clear 2214 sudo systemctl status mongod 2215 ls -l logs/ 2216 ./nodebb log 2217 ./nodebb stop 2218 DEBUG=* ./nodebb start 2219 ./nodebb log 2220 ./nodebb stop 2221 ./nodebb log 2222 ./nodebb start 2223 ./nodebb log 2224 ls -la /var/www/community/logs/ 2225 ls 2226 whoami 2227 groups 2228 chown -R root:root /var/www/community/logs 2229 ./nodebb start 2230 ./nodebb log 2231 sudo systemctl status mongod 2232 nodebb version 2233 ./nodebb version 2234 cat package.json | grep version 2235 mongod --version 2236 history My config { "url": "https://chatrooms.talkwithstranger.com", "secret": "63c2f418-1e6f-4bbf-b3ed-22c30531318b", "database": "mongo", "port": [ ], "mongo": { "host": "", "port": "", "username": "", "password": "", "database": "" }, "redis": { "host": "", "port": "", "database": 0 }, "socket.io": { "cors": { "origin": ["https://talkwithstranger.com"], "credentials": true } }, "imagemagick": "/usr/bin/convert", "graphicsmagick": "/usr/bin/gm" } mongod.conf # mongod.conf # for documentation of all options, see: # http://docs.mongodb.org/manual/reference/configuration-options/ # Where and how to store data. storage: dbPath: /var/lib/mongodb # engine: # wiredTiger: # where to write logging data. systemLog: destination: file logAppend: true path: /var/log/mongodb/mongod.log # network interfaces net: port: # bindIp: 127.0.0.1 bindIp: 0.0.0.0 # how the process runs processManagement: timeZoneInfo: /usr/share/zoneinfo #security: #operationProfiling: #replication: #sharding: ## Enterprise-Only Options: #auditLog: #snmp: If u need logs, please tell me steps to truncate log file name and then repeat start or restart nodebb or mongo so i can give u correct logs as my log file is very huge for both so its hard to track what is the issue. I also tried to check on main url at chatrooms.talkwithstranger.com but still JS console shows nothing and site shows empty [image: 1728740511663-bc08b941-3024-4da0-a82e-97d180eae728-image-resized.png] [image: 1728740522526-2caedf25-888f-4f62-8f04-0db30ec44d82-image-resized.png] [image: 1728740607324-e2b38786-b5a5-4c9f-b91f-6d00c6bde2d2-image-resized.png] Mongod log [image: 1728740866768-3fd25439-4037-437e-be43-75f88f44aa2a-image-resized.png] {"t":{"$date":"2024-10-12T13:46:01.380+00:00"},"s":"I", "c":"NETWORK", "id":51800, "ctx":"conn203","msg":"client metadata","attr":{"remote":"127.0.0.1:47186","client":"conn203","negotiatedCompressors":[],"doc":{"driver":{"name":"nodejs","version":"6.9.0"},"platform":"Node.js v20.17.0, LE","os":{"name":"linux","architecture":"x64","version":"6.8.0-36-generic","type":"Linux"}}}} {"t":{"$date":"2024-10-12T13:46:01.399+00:00"},"s":"I", "c":"ACCESS", "id":20250, "ctx":"conn203","msg":"Authentication succeeded","attr":{"mechanism":"SCRAM-SHA-256","speculative":true,"principalName":"","authenticationDatabase":"","remote":"127.0.0.1:47186","extraInfo":{}}} {"t":{"$date":"2024-10-12T13:46:01.403+00:00"},"s":"I", "c":"NETWORK", "id":22943, "ctx":"listener","msg":"Connection accepted","attr":{"remote":"127.0.0.1:47202","uuid":"c7aca16d-cddf-4c35-a99a-69417ffd89e3","connectionId":204,"connectionCount":20}} {"t":{"$date":"2024-10-12T13:46:01.405+00:00"},"s":"I", "c":"NETWORK", "id":22943, "ctx":"listener","msg":"Connection accepted","attr":{"remote":"127.0.0.1:47216","uuid":"8142abbe-5256-4bae-a459-22d085d3ddbb","connectionId":205,"connectionCount":21}} {"t":{"$date":"2024-10-12T13:46:01.409+00:00"},"s":"I", "c":"NETWORK", "id":22943, "ctx":"listener","msg":"Connection accepted","attr":{"remote":"127.0.0.1:47218","uuid":"8946a9e8-4f17-41b2-929d-9dc8d6ac1bc2","connectionId":206,"connectionCount":22}} {"t":{"$date":"2024-10-12T13:46:01.412+00:00"},"s":"I", "c":"NETWORK", "id":51800, "ctx":"conn204","msg":"client metadata","attr":{"remote":"127.0.0.1:47202","client":"conn204","negotiatedCompressors":[],"doc":{"driver":{"name":"nodejs","version":"6.9.0"},"platform":"Node.js v20.17.0, LE","os":{"name":"linux","architecture":"x64","version":"6.8.0-36-generic","type":"Linux"}}}} {"t":{"$date":"2024-10-12T13:46:01.412+00:00"},"s":"I", "c":"ACCESS", "id":20250, "ctx":"conn200","msg":"Authentication succeeded","attr":{"mechanism":"SCRAM-SHA- {"t":{"$date":"2024-10-12T13:46:01.424+00:00"},"s":"I", "c":"NETWORK", "id":51800, "ctx":"conn206","msg":"client metadata","attr":{"remote":"127.0.0.1:47218","client":"conn206","negotiatedCompressors":[],"doc":{"driver":{"name":"nodejs","version":"6.9.0"},"platform":"Node.js v20.17.0, LE","os":{"name":"linux","architecture":"x64","version":"6.8.0-36-generic","type":"Linux"}}}} {"t":{"$date":"2024-10-12T13:46:01.425+00:00"},"s":"I", "c":"NETWORK", "id":51800, "ctx":"conn205","msg":"client metadata","attr":{"remote":"127.0.0.1:47216","client":"conn205","negotiatedCompressors":[],"doc":{"driver":{"name":"nodejs","version":"6.9.0"},"platform":"Node.js v20.17.0, LE","os":{"name":"linux","architecture":"x64","version":"6.8.0-36-generic","type":"Linux"}}}} {"t":{"$date":"2024-10-12T13:46:01.427+00:00"},"s":"I", "c":"NETWORK", "id":22943, "ctx":"listener","msg":"Connection accepted","attr":{"remote":"127.0.0.1:47226","uuid":"639f9dbf-f3b6-409c-9715-2b47c8ce4ca9","connectionId":207,"connectionCount":23}} {"t":{"$date":"2024-10-12T13:46:01.428+00:00"},"s":"I", "c":"NETWORK", "id":22943, "ctx":"listener","msg":"Connection accepted","attr":{"remote":"127.0.0.1:47236","uuid":"e637f2af-1d6b-40da-b560-b2f5ac12d121","connectionId":208,"connectionCount":24}} {"t":{"$date":"2024-10-12T13:46:01.438+00:00"},"s":"I", "c":"NETWORK", "id":22943, {"t":{"$date":"2024-10-12T13:46:01.486+00:00"},"s":"I", "c":"NETWORK", "id":51800, "ctx":"conn213","msg":"client metadata","attr":{"remote":"127.0.0.1:47274","client":"conn213","negotiatedCompressors":[],"doc":{"driver":{"name":"nodejs","version":"6.9.0"},"platform":"Node.js v20.17.0, LE","os":{"name":"linux","architecture":"x64","version":"6.8.0-36-generic","type":"Linux"}}}} {"t":{"$date":"2024-10-12T13:46:01.496+00:00"},"s":"I", "c":"ACCESS", "id":20250, "ctx":"conn212","msg":"Authentication succeeded","attr":{"mechanism":"SCRAM-SHA- {"t":{"$date":"2024-10-12T13:46:01.502+00:00"},"s":"I", "c":"NETWORK", "id":22943, "ctx":"listener","msg":"Connection accepted","attr":{"remote":"127.0.0.1:47278","uuid":"7cf721bf-9f1d-4865-8a92-6edf5cf6f538","connectionId":214,"connectionCount":30}} {"t":{"$date":"2024-10-12T13:46:01.503+00:00"},"s":"I", "c":"NETWORK", "id":22943, "ctx":"listener","msg":"Connection accepted","attr":{"remote":"127.0.0.1:47280","uuid":"1f6cf7b3-751d-4d45-8a96-2096012057b4","connectionId":215,"connectionCount":31}} {"t":{"$date":"2024-10-12T13:46:01.514+00:00"},"s":"I", "c":"NETWORK", "id":51800, "ctx":"conn214","msg":"client metadata","attr":{"remote":"127.0.0.1:47278","client":"conn214","negotiatedCompressors":[],"doc":{"driver":{"name":"nodejs","version":"6.9.0"},"platform":"Node.js v20.17.0, LE","os":{"name":"linux","architecture":"x64","version":"6.8.0-36-generic","type":"Linux"}}}} {"t":{"$date":"2024-10-12T13:46:01.515+00:00"},"s":"I", "c":"NETWORK", "id":51800, "ctx":"conn215","msg":"client metadata","attr":{"remote":"127.0.0.1:47280","client":"conn215","negotiatedCompressors":[],"doc":{"driver":{"name":"nodejs","version":"6.9.0"},"platform":"Node.js v20.17.0, LE","os":{"name":"linux","architecture":"x64","version":"6.8.0-36-generic","type":"Linux"}}}} {"t":{"$date":"2024-10-12T13:46:01.542+00:00"},"s":"I", "c":"ACCESS", "id":20250, {"t":{"$date":"2024-10-12T13:46:02.984+00:00"},"s":"I", "c":"NETWORK", "id":22943, "ctx":"listener","msg":"Connection accepted","attr":{"remote":"127.0.0.1:47282","uuid":"95ebe824-8617-4001-9db5-6a99cadd8157","connectionId":216,"connectionCount":32}} {"t":{"$date":"2024-10-12T13:46:02.993+00:00"},"s":"I", "c":"NETWORK", "id":22943, "ctx":"listener","msg":"Connection accepted","attr":{"remote":"127.0.0.1:47296","uuid":"5768f4d7-6941-4c84-ac3a-fe11e751361d","connectionId":217,"connectionCount":33}} {"t":{"$date":"2024-10-12T13:46:03.003+00:00"},"s":"I", "c":"NETWORK", "id":51800, "ctx":"conn216","msg":"client metadata","attr":{"remote":"127.0.0.1:47282","client":"conn216","negotiatedCompressors":[],"doc":{"driver":{"name":"nodejs","version":"6.9.0"},"platform":"Node.js v20.17.0, LE","os":{"name":"linux","architecture":"x64","version":"6.8.0-36-generic","type":"Linux"}}}} {"t":{"$date":"2024-10-12T13:46:03.013+00:00"},"s":"I", "c":"NETWORK", "id":51800, "ctx":"conn217","msg":"client metadata","attr":{"remote":"127.0.0.1:47296","client":"conn217","negotiatedCompressors":[],"doc":{"driver":{"name":"nodejs","version":"6.9.0"},"platform":"Node.js v20.17.0, LE","os":{"name":"linux","architecture":"x64","version":"6.8.0-36-generic","type":"Linux"}}}} {"t":{"$date":"2024-10-12T13:46:03.022+00:00"},"s":"I", "c":"ACCESS", "id":20250, {"t":{"$date":"2024-10-12T13:46:03.160+00:00"},"s":"I", "c":"NETWORK", "id":22943, "ctx":"listener","msg":"Connection accepted","attr":{"remote":"127.0.0.1:47304","uuid":"38571c02-5145-4727-97e3-2b755bc1481d","connectionId":218,"connectionCount":34}} {"t":{"$date":"2024-10-12T13:46:03.167+00:00"},"s":"I", "c":"NETWORK", "id":51800, "ctx":"conn218","msg":"client metadata","attr":{"remote":"127.0.0.1:47304","client":"conn218","negotiatedCompressors":[],"doc":{"driver":{"name":"nodejs","version":"6.9.0"},"platform":"Node.js v20.17.0, LE","os":{"name":"linux","architecture":"x64","version":"6.8.0-36-generic","type":"Linux"}}}} {"t":{"$date":"2024-10-12T13:46:03.168+00:00"},"s":"I", "c":"NETWORK", "id":22943, "ctx":"listener","msg":"Connection accepted","attr":{"remote":"127.0.0.1:47308","uuid":"4f54d0d2-fbd3-48d5-9c41-f8d6fb16e881","connectionId":219,"connectionCount":35}} {"t":{"$date":"2024-10-12T13:46:03.169+00:00"},"s":"I", "c":"NETWORK", "id":22943, "ctx":"listener","msg":"Connection accepted","attr":{"remote":"127.0.0.1:47314","uuid":"92cd8e96-f5ab-4243-b1fd-ffd5d3986f2d","connectionId":220,"connectionCount":36}} {"t":{"$date":"2024-10-12T13:46:03.170+00:00"},"s":"I", "c":"ACCESS", "id":20250, {"t":{"$date":"2024-10-12T13:46:03.187+00:00"},"s":"I", "c":"NETWORK", "id":51800, "ctx":"conn219","msg":"client metadata","attr":{"remote":"127.0.0.1:47308","client":"conn219","negotiatedCompressors":[],"doc":{"driver":{"name":"nodejs","version":"6.9.0"},"platform":"Node.js v20.17.0, LE","os":{"name":"linux","architecture":"x64","version":"6.8.0-36-generic","type":"Linux"}}}} {"t":{"$date":"2024-10-12T13:46:03.193+00:00"},"s":"I", "c":"NETWORK", "id":51800, "ctx":"conn220","msg":"client metadata","attr":{"remote":"127.0.0.1:47314","client":"conn220","negotiatedCompressors":[],"doc":{"driver":{"name":"nodejs","version":"6.9.0"},"platform":"Node.js v20.17.0, LE","os":{"name":"linux","architecture":"x64","version":"6.8.0-36-generic","type":"Linux"}}}} {"t":{"$date":"2024-10-12T13:46:03.197+00:00"},"s":"I", "c":"ACCESS", "id":20250, "ctx":"conn220","msg":"Authentication succeeded","attr":{"mechanism":"SCRAM-SHA-2 {"t":{"$date":"2024-10-12T13:46:03.289+00:00"},"s":"I", "c":"NETWORK", "id":22943, "ctx":"listener","msg":"Connection accepted","attr":{"remote":"127.0.0.1:47324","uuid":"d7d3f921-4285-489c-9b55-48a1f1e2b54d","connectionId":221,"connectionCount":37}} {"t":{"$date":"2024-10-12T13:46:03.299+00:00"},"s":"I", "c":"NETWORK", "id":51800, "ctx":"conn221","msg":"client metadata","attr":{"remote":"127.0.0.1:47324","client":"conn221","negotiatedCompressors":[],"doc":{"driver":{"name":"nodejs","version":"6.9.0"},"platform":"Node.js v20.17.0, LE","os":{"name":"linux","architecture":"x64","version":"6.8.0-36-generic","type":"Linux"}}}} {"t":{"$date":"2024-10-12T13:46:03.308+00:00"},"s":"I", "c":"ACCESS", "id":20250, "ctx":"conn221","msg":"Authentication succeeded","attr":{"mechanism":"SCRAM-SHA-256","speculative":true,"principalName":"","authenticationDatabase":"","remote":"","extraInfo":{}}}

When can I see the display of nodebb4.0? Looking forward to it

Is there somewhere listed for CPU, RAM, etc that is required? (I am currently hosting on heroku)

Hi there, Running 3.10.2 and am still fairly new to NodeBB admin. I'm trying to get widgets to layout beside each other similar to community.nodebb.org's Categories page, as well as the layout shown in Harmony theme's Categories example screenshot. I drag widgets over to the Categories Header area, and no matter what I do they only stack vertically. I haven't found any way for the widgets to go beside each other, and am curious if I've hit a weird issue, or if I'm just missing something obvious.

Hello, I was testing on the demo site and noticed that all clients can see new posts arrive in a topic in real-time, which is awesome (and a feature I've been looking for in a forum software ^.^) I think it would also be great if: When posting a new topic, it updates viewers on the /recent and /category pages. (This does not seem to happen on the demo site) Display a person-is-typing indicator Who else is here / viewing indicator These would help enhance the feeling of "presence" and real-time interactivity. Thanks for reading!

I get the nodebb-plugin-composer-quill from github, and the configuration is no problem [image: 1730097857290-dff81bb8-da8a-4203-b767-0bf9d348f540-image-resized.png] However,when I want to create a new topic and click it,the composer cant use. It is like this [image: 1730098070605-b8a13611-6536-4cfa-bd62-7dafcd4676f7-image-resized.png] I must solve the question, what should I do?

I'm trying to use nodebb-plugin-s3-uploads. My home computer has Ubuntu and MinIO. It has a static IP. The VDS has a forum, nodebb-plugin-s3-uploads and the MinIO console (mc). The console (mc) works fine. AWS_ACCESS_KEY_ID="minioadmin" AWS_SECRET_ACCESS_KEY="minioadmin" Bucket = data1 Host = http://"IP":9000 When I try to insert an image into the response, I get the following message:  How can I solve this problem?

Hey all, I have an issue which seems to relate to both browser AS WELL AS server side caching. Essentially the user uploads a new profile photo (or cover photo) they navigate to a different page and still see the profile photo they chose. When they navigate back to their profile the photo changes back to their original photo. When using a browser in incognito mode I am able to see that their profile picture never changed. I do not get back any form of failure / error to troubleshoot this issue. In fact I get back a 200 from the following url, the URL also returns the uploaded pic. https://<URL>/assets/uploads/profile/1-profileavatar.jpeg?1587402445550 Any idea what might be happening here? Have tried restarting / rebuilding to solve to no avail.

For example, I want to change how the topic scroller works, but the javascript is here: https://github.com/NodeBB/NodeBB/blob/0e4fc531e006c3dd2c5fa402e90b20309cc3a1e6/public/src/modules/navigator.js I know I can create a totally fresh scroller and add my own functions, but I was wondering if there is a way I could override some of the navigator functions

I've added the plugin and the API key, but no-one gets any emails from my forum. I've followed the instructions multiple times, restarted several times and used the API key via cURL to confirm it works (copied and pasted it out of nodeBB to be sure it's the same), which it does. Trawling through the startup logs, I can see 2024-10-27T15:53:38.103Z [4567/12061] - info: [plugins/emailer-sendgrid] Custom field nodebb_username already exists, OK. 2024-10-27T15:53:38.162Z [4567/12061] - info: [plugins/emailer-sendgrid] Custom field nodebb_fullname already exists, OK. 2024-10-27T15:53:38.162Z [4567/12061] - info: [plugins/emailer-sendgrid] Done. so that looks good. If I go to the events, I can see: { "confirm_code": "[confirm code]", "email": "[user's email]", "force": true, "timestamp": 1730038787173 } so that looks good too. I've been through the source code for the plugin and I can see where Winston would log something out if there was an issue, but there's nothing in the logs - after all the SASS deprecation warnings, nothing else gets posted. I've enabled port 1337 on my server's firewall to ensure the connections stay alive, in case that's relevant. Do I need to open port 25 for SMTP? Thanks!

Has anyone else noticed that your forum slows down in terms of response after you've chosen an emoji, or even opened the preview to see what ones are available? I mean this [image: 1729620550610-1c427dbd-ca1f-48a4-a845-73e270f78b5a-image.png] On my site at least, the activation of this drop-up means data takes around 2 seconds longer to load until I reload the browser. Has anyone seen this?

Hello, as the title says, how do I calculate the total size of files in use in nodebb? I'm trying to use a CDN like s3, but when I searched, I found that I had to read all objects in the bucket and calculate the file size like this. Is there no other way to find out the total size of files in use in nodebb? https://stackoverflow.com/questions/32192391/how-do-i-find-the-total-size-of-my-aws-s3-storage-bucket-or-folder