I created a new Ubuntu droplet with the Node.js one click install.
Followed this guide to have nodebb installed on the server https://nodebb.readthedocs.io/en/latest/installing/os/ubuntu.html
I created an A record to point the server to my subdomain community.intelisight.com and added same on cloudflare.
But when I try to access the installation (which was successful and the service shows as running) with this http://community.intelisight.com:4567 I get nothing. When I say http://community.intelisight.com same thing, I’m simply unable to access the live site.
My questions are
a) What am I doing wrong? What do I need to do to see the nodebb installation? b) Is there a guide showing how to use nginx as the proxy server so I don’t have to put in the port to access the website? c) How can I setup a free Let’s Encrypt SSL on this installation?
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
When it comes to NodeJS apps and NGINX, the only way to access your URL with attaching the port to the end would be to use NGINX as a Proxy, in which case you would proxy requests on 80/443 to the port of your choice (i.e. your NodeJS app).
For example, this server block will take requests on port 80 and redirect them to port 443, and proxy requests on 443 to port 4567 (i.e your app). This would all be in a single file (i.e. yourdomain.conf).
NGINX as a Proxy
You’d need to change
yourdomain.comto your actual domain, of course, though the above will set you up so that you’re not forced to use the port in the URL.
You’ll need to reload NGINX once you’re done making changes using:
The issue with CloudFlare is common. If you login and navigate to their SSL Settings page, you should see a drop-down with a few options. It’s either Full or Full (Strict) – that’s the setting you need to use.
I’ve ran in to that issue with quite a few sites as of late and that seems to be the only fix for those who use CloudFlare.
Want to learn more? Join the DigitalOcean Community!
Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.
Sign up now
Thanks a lot @jtittle you’ve been really helpful.
I tried the config you sent over, was getting an error on Cloudflare, something like “SSL Handshake Error” so I retried the old config without that “try” line, and it worked.