Line 85: |
Line 85: |
| {{Note box|This FIRST user will be the 'master administrator' even if you use [[Rocket_Chat#LDAP_Authentication|'''LDAP authentication''']] for your users. So if even if you use LDAP, this user will still be able to login and grant Rocket.Chat admin rights to [[Rocket_Chat#LDAP_Authentication|LDAP]] accounts.}} | | {{Note box|This FIRST user will be the 'master administrator' even if you use [[Rocket_Chat#LDAP_Authentication|'''LDAP authentication''']] for your users. So if even if you use LDAP, this user will still be able to login and grant Rocket.Chat admin rights to [[Rocket_Chat#LDAP_Authentication|LDAP]] accounts.}} |
| | | |
− | ==Make Rocket.Chat available on a sub domain==
| |
− | Install the '''[[Webapps-common]]''' contrib.
| |
− |
| |
− | To create your sub domain (e.g. https://chat.yourserver.com)
| |
− | db domains set chat.mycompany.local domain Description "RocketChat" Nameservers internet \
| |
− | TemplatePath WebAppVirtualHost RequireSSL enabled ProxyPassTarget http://localhost:3000/ ProxyPreserveHost yes
| |
− | The 'ProxyPassTarget' property could also point to another host (IP) that has Rocket.Chat installed, e.g. a virtual SME Server on the same LAN. In that case, also LDAP and open/close ports have to be taken into consideration.
| |
− | To expand and activate:
| |
− | signal-event webapps-update
| |
− |
| |
− | If your server' default FQDN is already chat.yourserver.com, there is no need to create a new subdomain. Instead of the above command, you can enter the following:
| |
− | db domains setprop chat.yourserver.com TemplatePath WebAppVirtualHost RequireSSL enabled ProxyPassTarget http://localhost:3000/ ProxyPreserveHost yes
| |
− |
| |
− | To disable the default access on port 3000, for we now access our chat platform via the subdomain, and for security we close the default access method.
| |
− | config setprop rocketchat access private
| |
− | signal-event remoteaccess-update
| |
− |
| |
− | You can now visit Rocket.Chat at https://chat.yourserver.com. Rocket.Chat will notice that the URL that is being used to access Rocket.Chat has been changed, and will propose to change it to the new URL.
| |
| | | |
| ==Auto start Rocket.Chat at boot== | | ==Auto start Rocket.Chat at boot== |
Line 142: |
Line 124: |
| | | |
| Please note that it may take a little while, up to a minute, for rocketchat to become available. In the mean time you can be shown a HTTP error 503. Please try again in a minute or a bit longer. Why this is? No Idea for now, other that it may be related to MongoDB processes. | | Please note that it may take a little while, up to a minute, for rocketchat to become available. In the mean time you can be shown a HTTP error 503. Please try again in a minute or a bit longer. Why this is? No Idea for now, other that it may be related to MongoDB processes. |
| + | |
| + | |
| + | |
| + | ==Make Rocket.Chat available on a sub domain== |
| + | Install the '''[[Webapps-common]]''' contrib. |
| + | |
| + | To create your sub domain (e.g. https://chat.yourserver.com) |
| + | db domains set chat.mycompany.local domain Description "RocketChat" Nameservers internet \ |
| + | TemplatePath WebAppVirtualHost RequireSSL enabled ProxyPassTarget http://localhost:3000/ ProxyPreserveHost yes |
| + | The 'ProxyPassTarget' property could also point to another host (IP) that has Rocket.Chat installed, e.g. a virtual SME Server on the same LAN. In that case, also LDAP and open/close ports have to be taken into consideration. |
| + | To expand and activate: |
| + | signal-event webapps-update |
| + | |
| + | If your server' default FQDN is already chat.yourserver.com, there is no need to create a new subdomain. Instead of the above command, you can enter the following: |
| + | db domains setprop chat.yourserver.com TemplatePath WebAppVirtualHost RequireSSL enabled ProxyPassTarget http://localhost:3000/ ProxyPreserveHost yes |
| + | |
| + | To disable the default access on port 3000, for we now access our chat platform via the subdomain, and for security we close the default access method. |
| + | config setprop rocketchat access private |
| + | signal-event remoteaccess-update |
| + | |
| + | You can now visit Rocket.Chat at https://chat.yourserver.com. Rocket.Chat will notice that the URL that is being used to access Rocket.Chat has been changed, and will propose to change it to the new URL. |
| + | |
| | | |
| ==WebRTC configuration== | | ==WebRTC configuration== |