@pitaj This seems to be a new requirement, so if that is truly the case, then our Facebook SSO plugin is not compatible with the latest Facebook changes.
Thanks for reporting
You Web server is the application that makes it possible to access a Web application like NodeBB. In most cases, it's either Apache or Nginx. If you are connected your Droplet via SSH, type
sudo service nginx status just to see what it will tell you. I'm betting that you are running Apache, but I could be wrong. You can also trying cd-ing to the /etc/nginx directory. If it does not exist, then you are running Apache.
If it's a standard ubuntu 12.04 droplet from Digital ocean you probably don't have a web server installed yet, install a current version of nginx (not from the standard ubuntu repository) and set it up to reverse proxy your nodebb app to port 80. there are plenty of good guides on this on the digital ocean support pages.
Okay, sorry to ask again.
I've gotten the proxy down I think, except that there are problems with logging in and the widgets aren't showing on when I go on the domain name (aotforums.com)
But when I got on (aotforums.com:4567) everything is normal.
Can someone help a dummy out (me)?
I installed nginx and am at the NodeBB wiki page for configuring nginx as a proxy server. So far I've just been following instructions word for word, but I'm a newb and don't know what to do with this:
NGINX-served sites are contained in a server block. This block of options goes in a specific place based on how nginx was installed and configured:
/path/to/nginx/sites-available/* -- files here must be aliased to ../sites-enabled
/path/to/nginx/conf.d/*.conf -- filenames must end in .conf
/path/to/nginx/httpd.conf -- if all else fails
Below is the basic nginx configuration for a NodeBB build running on port 4567:
etc etc etc
Alright, I can do that. Didn't want to post a new topic since I'm sort of embarrassed -- the original poster seemed to also not have too much knowledge, but even he figured out how to set up reverse proxy.
The way I found the correct file to update was to look in the /path/to/nginx/conf.d/ file for different files. I don't remember what I saw, but I saw it reference something else that vestacp had created for me under /home/username/web. I went to those files and followed the path even more until I found the actual .conf for the domain I wanted to use and modified the config it had created for me to one that proxies the port. You would be correct that you have to edit a text configuration file, I used nano but I suppose you could use emacs.
When I get home from work I'll see if I can figure out for sure what I did. All I know is that once I found the conf.d folder I was able to trace my way up to the appropriate place.
@HolyPhoenix Hold on, did you have a bacon signature yesterday? I made bacon in the oven last night and damn it was crispy! Also, thanks for pointing me in the right direction.