The user kyler reports that the ‘Users’ link in the admin menu doesn’t display any users, though it works correctly from the ‘Settings’ menu. cpradio explains this is due to caching, which takes a day or two to populate, and clarifies that the menu shown is not the admin menu but the general user menu. jomaxro asks about potential CSS/JS customizations or plugins and requests a link to the forum, which kyler provides as support.outergain.com. The user also asks about the proper way to shut down Discourse before a server reboot, and cpradio confirms that a standard shutdown -r now command is sufficient for a Docker install. kyler expresses concern about potential corruption, but cpradio reassures that no issues are likely, and kyler thanks the community for their help.
I’ve installed a new discourse forum and it’s working great, but there’s one bug I haven’t seen before. Brief facts: normally I’ve paid the discourse team to install it for me at Digitial Ocean. But I like Linode, so this time I finally just installed myself following the instructions at Github.
It’s on a 1GB VPS with Ubuntu 16.04 LTS. Discourse v1.8.0.beta6.
Discourse is the only thing running on the VPS.
When I click on the admin menu, and then ‘Users’ the page comes up and shows nobody. If I click on ‘Settings’ and from there click on ‘Users’ they display correctly.
Also, what’s the proper way to shut down Discourse for a server reboot? I had to issue a ‘reboot’ command last night in Linux, but didn’t know how to gracefully shut down Discourse first. Hopefully I didn’t screw anything up.
When you load users this way, are there any errors in your Browser console?
Have you attempted any CSS or JS customizations on the site?
Any third-party plugins?
Also, for a support topic, please share a link to the forum.
I’ve never done anything to Discourse before a reboot, and I don’t think it’s necessary to do anything. One of the devs (like @codinghorror) should be able to confirm this.
Last night, some other stuff started acting weird on the forum, so I rebooted the server and it’s been fine since. Was afraid the combo signified a larger issue, but glad to hear it’s just caching.
@codinghorror, if you could verify a proper shut down process, that would be awesome. And thanks for the sweet product.
Performing shutdown -r now will properly stop all forum services, as that is controlled by the Docker container (this assumes you did a docker install – which is the only supported install).
awesome. so did i screw anything up? this is a brand new forum and I can wipe and reinstall worst case. i don’t want something corrupted that’s gonna bite me later.
I don’t think you did. You can check http://example.com/logs to see if there are any red flags/errors but based on what you are seeing/reporting I doubt there is.