@baris Sorry, school got in the way of me responding. I'll try downgrading jQuery. Thank's for the help, I was really confused.
J4ckk3
Posts
-
Fresh installation seems broken -
Fresh installation seems brokenYes there are. Here are screenshots of the errors,
Here's the actual type error (not the jquery exception)
-
Fresh installation seems brokenHi,
The VPS is running Ubuntu 18.04. It's hosted with Digital Ocean.
I've installed NodeBB numerous times and I've never had this happen before.
Here is what I'm seeing,
When I reload the page with F5 I see this,
I only see the first image when I navigate NodeBB with the navbar. I check the page source and there seems to be empty style tags when I've navigated to the page via the navbar.
Here's my configuration (I haven't set the site up with a reverse-proxy yet, I'll do this once I fix the issue),
{ "url": "http://####", "secret": "#", "database": "redis", "redis": { "host": "127.0.0.1", "port": "6379", "password": "#", "database": "0" }, "port": "4567" }
I've already checked the connection to redis. That's working. I'm running NodeBB on an unprivileged user. If you have any ideas to what's going on please let me know. I even tried a different version of NodeBB, no luck.
-
Fresh installation seemingly brokenI just recently installed NodeBB on an Ubuntu 18.04 VPS.
My configuration is below,
{ "url": "http://161.35.48.102:4567", "secret": "#", "database": "redis", "port": "4567", "redis": { "host": "127.0.0.1", "port": 6379, "password": "#", "database": 0 } }
Here is what I'm seeing,
I was originally running the site with Nginx and a reverse proxy, but after having these issues I stopped Nginx and updated the configuration to try and see if Nginx was the issue.
When I use Ctrl-F5 (or just F5) to reload the page everything shows up as working properly, but when I use the navbar to navigate the website I experience the issue you see above. Using inspect element the style tags appear to be empty. Also, when I log into my account the pages show as completely empty.
I've never experienced this issue before. I'm wondering if this is a filesystem permission issue. At this point I don't know what to do.
Any ideas?