you need to manually compile and add the module "mod_proxy_wstunnel" to the Apache 2.2 branch. If you're running Ubuntu or Debian, you're likely on the 2.2 branch of code.
you need to manually compile and add the module "mod_proxy_wstunnel" to the Apache 2.2 branch. If you're running Ubuntu or Debian, you're likely on the 2.2 branch of code.
@ -12,23 +13,31 @@ The following guide will assist with that if you're on Debian or Ubuntu. This is
#### NOTE: On ubuntu, if you’re missing the ./configure file
NOTE: On ubuntu, if you’re missing the ./configure file
You need to first run ./buildconf. After this is complete, you will then be able to use ./confugure.
------------------------------------
You need to first run ./buildconf. After this is complete, you will then be able to use ./configure.
>automake & libtool package was needed too.
**automake & libtool package was needed too.**
>apt-get install automake libtool
****
..code::
# Enable the necessary modules
apt-get install automake libtool
Enable the necessary modules
-----------------------------
1. sudo a2enmod proxy
1. sudo a2enmod proxy
2. sudo a2enmod proxy_html
2. sudo a2enmod proxy_html
3. sudo a2enmod proxy_wstunnel
3. sudo a2enmod proxy_wstunnel
## Add the config to Apache
Add the config to Apache
-----------------------------
The next step is adding the configuration to your virtualhost.conf file, typically located in /etc/apache2/sites-available/. The below configuration assumes you've used 4567 (default) port for NobeBB installation. It also assumes you have the bind address set to 127.0.0.1.
The next step is adding the configuration to your virtualhost.conf file, typically located in /etc/apache2/sites-available/. The below configuration assumes you've used 4567 (default) port for NobeBB installation. It also assumes you have the bind address set to 127.0.0.1.
..code::
ProxyRequests off
ProxyRequests off
<Proxy *>
<Proxy *>
@ -47,8 +56,11 @@ The next step is adding the configuration to your virtualhost.conf file, typical
The last thing you need to be sure of is that the config.json in the NodeBB folder has use_port: false. Otherwise some functionality will not work properly.
The last thing you need to be sure of is that the config.json in the NodeBB folder has use_port: false. Otherwise some functionality will not work properly.
****
## Example nodebb/config.json
Example nodebb/config.json
-----------------------------
..code:: json
{
{
"base_url": "http://www.yoursite.com",
"base_url": "http://www.yoursite.com",
@ -68,4 +80,5 @@ The last thing you need to be sure of is that the config.json in the NodeBB fold
"relative_path": ""
"relative_path": ""
}
}
>Change the domain and dont use the secret in the example above.
**Change the domain and dont use the secret in the example above.**