All links under Admin->Manage don't work

[nmeadows]

I just got Nodebb installed and running. In the admin page, every link under "Manage" gives this error:
Not Found
You seem to have stumbled upon a page that does not exist. Return to the home page.

Every link in the rest of the admin panel works fine. Any ideas? There's no errors in the logs.

[PitaJ]

Try a rebuild and restart

[nmeadows]

@PitaJ Thank you. I have tried that several times now. No luck.

[PitaJ]

Did you try running it manually from the command line? What's the output of git status?

[gotwf]

This one seems pretty strange. I'd expect an either/or whether ACP worked at all, not a fail of a single tab/sub menu. Maybe something got corrupted/horked at the initial setup stage. Some gremlin glitch in la' machine? Since this is all brand spanking new and you've nothing to loose but some time, I suggest you try blowing the db away and run set up. Also, ensure you are doing so as your nodebb user, not root.

Some other thoughts:

1. Are you using Mongodb or Redis?

2. Have you double/triple checked your config.json parameters? Typos?

3. What version of Nodejs are you running?

4. Are you hitting the nodebb app server directly or proxying thru e.g. Nginx?

Any one of which could potentially cause a glitch so maybe double check all that 'chit? I'd rule out #1 though if you blow db away and problem persists. Hence, maybe some low hanging fruit you can rule out there, eh? Then focus on else?

May the force be with you.

[nmeadows]

Git status is clean. I tried updating to v1.14.x. It upgraded fine, but the issue remained.

[nmeadows]

@gotwf I just tried blowing out all code, and starting fresh.
For more details:
Running in Kubernetes (alpine linux base-image with npm/node/etc installed there)
Postgres database (using existing cluster, and I have lost of postgres background)
Node version is v12.15.0
Proxying via the Kubernetes default ingress

After restarting from scratch, I tried bypassing the Kubernetes ingress, and going strait to the host/port, and low-and-behold, the admin/manage pages work. When using that ingress, they do not (but all other paths work?). That's a head scratcher for sure.

[gotwf]

@nmeadows Indubitably. I am retired old dinosaur. Did some devops in my day a'la Salt and Chef but that predated Kubernetes so I've no clue. But at least now you have pinpointed the link in the chain that is failing and where to focus future troubleshooting efforts. Good job.

[nmeadows]

@gotwf I have found the culprit, and it has nothing to do with NodeBB, so I'm sorry to have bothered you.
It ended up being our security team turned on web filtering rule on our load balancer that filters out certain URL paths that have admin/manage/etc in the path. The idea being to filter our administration pages and force the use of VPN to get to those paths. It's a fine idea, but I was not informed of that change.

Thank you for your help.

[gotwf]

@nmeadows Cool. Glad you got it sorted.

And that is a smart idea.

[scottalanmiller]

@gotwf said in All links under Admin->Manage don't work:

@nmeadows Indubitably. I am retired old dinosaur. Did some devops in my day a'la Salt and Chef but that predated Kubernetes so I've no clue. But at least now you have pinpointed the link in the chain that is failing and where to focus future troubleshooting efforts. Good job.

Salt? Get off my lawn, whippersnapper.

[scottalanmiller]

@nmeadows said in All links under Admin->Manage don't work:

@gotwf I have found the culprit, and it has nothing to do with NodeBB, so I'm sorry to have bothered you.
It ended up being our security team turned on web filtering rule on our load balancer that filters out certain URL paths that have admin/manage/etc in the path. The idea being to filter our administration pages and force the use of VPN to get to those paths. It's a fine idea, but I was not informed of that change.

Thank you for your help.

Better to bother us and get it fixed than to not bring it up and not Glad that you got it figured out.