From the menu options on the right hand panel of the window, click "Server proxy settings". Now in the IIS control panel, click on the server name in hierarchy/tree and open up the Application Request Routing module.You need to be using HTTPS in order for the Rocket.Chat+ mobile apps to function (and because its good practice of course). Go to the IIS control panel and set up a website with an HTTPS binding (you can get a free SSL certificate using Lets Encrypt - if you want).Then install ARR 3.0 ( ) and URL Rewrite ( ).Make sure the IIS role you added to the server includes Websockets support.This takes external HTTPS traffic on port 443, and rewrites/proxies the request to the internal location of Rocket.Chat (). Now we need to look at setting up IIS as a reverse proxy. If your Windows Server installation is already a virtual machine (as ours was) you'll need to get your IT team to enable Nested Virtualisation for your virtual machine (see here) Docker uses Windows HyperV to run the container.This is geared around Windows 10, but works also on Windows Server (we used Windows Server 2016). First, follow the Windows 10 installation instructions get to Docker (and Rocket.Chat) up and running.Perhaps not our final solution, but we have got it to the point where it runs stably on Windows - in a Docker container - using IIS to reverse proxy requests. However, like a lot of open source software, there's little information on getting the system up and running using Windows Server. Slack seemed to be the "go to" solution - but if you have a lot of users, and want niceties such as SAML single sign-on, it's also very expensive.Ī colleague found Rocket.Chat, which looked very similar to Slack - and best of all, being open source is basically free. My company has been experimenting with Instant Messaging systems.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |