upgrade to 1.6.x is fine. still same error when trying to go to 1.7.x

interestingly enough I pulled the 1.5.x branch and the upgrade ran fine. maybe ill go to 1.6 first

I'm going from 1.5.3 to 1.7.3.

my git is where it needs to be and a git pull shows me all is up to date. when i run nodebb upgrade i see

sudo ./nodebb upgrade
/opt/nodebb/src/cli/index.js:60
        .description('Welcome to NodeBB')
         ^

TypeError: program.name(...).description is not a function
    at Object.<anonymous> (/opt/nodebb/src/cli/index.js:60:3)
    at Module._compile (module.js:570:32)
    at Object.Module._extensions..js (module.js:579:10)
    at Module.load (module.js:487:32)
    at tryModuleLoad (module.js:446:12)
    at Function.Module._load (module.js:438:3)
    at Module.require (module.js:497:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (/opt/nodebb/nodebb:5:1)
    at Module._compile (module.js:570:32)

or sudo systemctl status mongod

they want it in the head / body fields.

footer.tpl doesn't have those. i'm going to try header.tpl

@julian yeah I was thinking that. I'll give it a go and see what happens.

For those of you who are doing SEO.

Where are am I putting the tag manager code? In the .tpl files (it wants it on "every" page). Maybe header.tpl or footer.tpl?

Thanks for any thoughts here!

@PitaJ said in Simplifying the URL:

@etakmit unfortunately, multiple posts can have the same title, so some kind of unique ID has to be included in the url. It could be the pid of the post, either prepended or appended to the URL, or something else.

Fair point!

What I'm ultimately looking for is that URLs to posts are simply

http://domain/post-title

Sadly I dont think either of your options quite fit although they're pretty close! Thank you!

The URL for topics currently looks like
https://forum.com/topic/15/url-rewrites

We'd like to see

https://forum.com/url-rewrites

I haven't found a toggle in the admin side, nor did I see a plugin to accomplish this. Is this something that can be done simply? I kicked around the forum here and all of my searches generally ran into old config.json references which didn't seem to apply.

@julian I'm still determining what is best. I think once a month depending on the timing could be problematic (although a manual renew isn't the worst thing in the world).

Even the letsencrypt walkthrough says twice a day

Note: if you're setting up a cron or systemd job, we recommend running it twice per day (it won't do anything until your certificates are due for renewal or revoked, but running it regularly would give your site a chance of staying online in case a Let's Encrypt-initiated revocation happened for some reason). Please select a random minute within the hour for your renewal tasks.

I might go with that or I might go weekly. We'll see.

All set. Thanks guys. Was definitely painless once I wrapped my head around it (and remembered to allow 443 through my firewall ... d'oh)

@RoiEXLab thanks! Between your reply and @hek 's reply I should be able to figure this out!

@hek that's where its getting me. since my nodebb is in /opt/nodebb I could just run the letsencrypt script facing that right?

SSL is new to me, as such I haven't made it work on any other site that I've run before.

Looking at Letsencrypt and their directions I don't get any nginx information. Everything is for apache. So I don't know where to begin (I understand generally what I'd do in nginx to point 443 but otherwise I'm pretty lost).

Anyone have a general step by step overview for me?

Thanks!

@tedbaker said in How do I get rid of NodeBB?:

@etakmit isn't this the 'Site Title' under Settings > General, you can either change the text or turn it off

I was so worried about the icon section that I entirely missed that field. Thank you!

Tried to change the logo in the upper left corner of nodebb (it says nodebb). I wanted to replace that with a logo. It seems o have just put a logo next to the word NodeBB. Where can I find the NodeBB to remove?

And solved. Thanks again @PitaJ

@PitaJ it doesn't match. I was just using 127.0.0.1. I'll give this a look first thing in the AM. Thanks!

Just as the topic says. Registration links in my emails sent out to new users point to 127.0.0.1 instead of the URL of the domain. Thoughts? I've proven adept at creating uncommon issues.