• Home
  • Categories
  • Recent
  • Popular
  • Top
  • Tags
  • Users
  • Groups
  • Documentation
    • Home
    • Read API
    • Write API
    • Plugin Development
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
v3.5.2 Latest
Buy Hosting

nginx as reverse proxy (nginx+certbot+nodebb)

Scheduled Pinned Locked Moved NodeBB Development
2 Posts 1 Posters 782 Views
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • MJM Offline
    MJM Offline
    MJ
    wrote on last edited by
    #1

    Hi Guys,

    I'm asking this question on behalf of a friend (this is also his forum account)

    I'm trying to help setup nginx as reverse proxy to our website KEEN.wtf
    I've now tried several things and I have the feeling i'm pretty close to get it working, but it's not working yet 🙂

    So I've now set up NGINX as per the usual guides. This works, when I visit keen.wtf I see the default 'Welcome to Nginx' page. Now the next step would be getting our actual nodebb to show up.

    This is how the the nginx serverblock looks now:
    0_1530260855371_09f1c704-f153-4ac9-9f5f-f325b11e3a76-image.png

    This is our current config.json:
    {
    "url": "http://keen.wtf",
    "secret": "secret key",
    "database": "mongo",
    "port": 4567,
    "mongo": {
    "host": "127.0.0.1",
    "port": "27017",
    "username": "",
    "database": "
    "
    }
    }

    When running 'sudo nginx -t' this is the result:
    nginx: [warn] conflicting server name "keen.wtf" on 0.0.0.0:80, ignored
    nginx: [warn] conflicting server name "keen.wtf" on 0.0.0.0:80, ignored
    nginx: [warn] conflicting server name "keen.wtf" on 0.0.0.0:80, ignored
    nginx: [warn] conflicting server name "keen.wtf" on 0.0.0.0:443, ignored
    nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
    nginx: configuration file /etc/nginx/nginx.conf test is successful

    Now the big question, what am I doing wrong?

    Thanks in advance!!

    1 Reply Last reply
    0
  • MJM Offline
    MJM Offline
    MJ
    wrote on last edited by MJ
    #2

    Found a "hidden" file in the nginx/sites-available and nginx/site-enabled folders.
    Deleted that and now I only have one nginx warning left.

    When running 'sudo nginx -t' this is the result:
    nginx: [warn] conflicting server name "keen.wtf" on 0.0.0.0:80, ignored
    nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
    nginx: configuration file /etc/nginx/nginx.conf test is successful

    EDIT:

    Ok i have now also removed the return 301 (line 4) in the nginx server block, I think it also conflicts with the rewrite in line 5.

    Restarted server/nginx/nodebb
    And boom HTTPS works.

    Next thing though, we still don't get to see a greenlock in firefox or chrome. It says something about the site only being partially secure. Any idea why that happens?
    Now also fixed, our logo was still referring to a http link, removed the domain and just made it point to src="/assets/uploads/system/site-logo.png"

    PS. any other tips or adjustments on the config files is also welcome 😉

    1 Reply Last reply
    0

Copyright © 2023 NodeBB | Contributors
  • Login

  • Don't have an account? Register

  • Login or register to search.
Powered by NodeBB Contributors
  • First post
    Last post
0
  • Home
  • Categories
  • Recent
  • Popular
  • Top
  • Tags
  • Users
  • Groups
  • Documentation
    • Home
    • Read API
    • Write API
    • Plugin Development