@oplik0 +1 on the Jitsi stuff. Don't know jack about the code. I have been following that project since its very early days. Impressive and sustained progress, it makes. No flash in the pan, one or two shot wonder preceding an exit strategy, were they. Impressive. 👍
Broken forum after migration
I migrated my nodebb forum to a digital ocean droplet from my local machine. I made a backup of my mongodb database and transfered it to my droplet via ssh. Rebuilt and configured nodebb using that database. When I navigate to the forum with my browser (chrome and firefox) all of the data from my local machine is there. However the header is broken and there are no tools such as admin settings button. A notification box in the bottom right says I lost my connection and it is attempting to reconnect. But I can still navigate all of the categories just fine here is a screenshot
does anyone have experience migrating a nodebb forum that may be able to give me a direction to look as to where i might find a solution?
@rimann make sure that
config.jsoncontains the correct
urlvalue. It should be set to exactly the URL at which you access the site. If you're just testing, I recommend using
./nodebb devto start NodeBB.
Thank you for the tip. I actually remember reading to make sure and do that but I forgot. Unfortunatly after doing this I recieve this type error:
TypeError: Cannot read property 'replace' of null at setupConfigs (/home/riley/nodebb/src/start.js:96:68) at Object.start.start (/home/riley/nodebb/src/start.js:13:2) at Object.<anonymous> (/home/riley/nodebb/app.js:97:25) at Module._compile (module.js:577:32) at Object.Module._extensions..js (module.js:586:10) at Module.load (module.js:494:32) at tryModuleLoad (module.js:453:12) at Function.Module._load (module.js:445:3) at Module.runMain (module.js:611:10) at run (bootstrap_node.js:387:7)
@rimann that probably means that you set the
urlvalue to something invalid. What did you set it to? If it's something you'd rather not share, you can PM me instead.
Thanks to PitaJ I have the solution for anyone else who encounters this problem. Make sure the url in the conf.json is correct. Also make sure that the ip adress is prefixed with