By the way, I happened to see that Atlassian has a hipchat. In fact, it was already there, and it was acquired in 2012.
hipchat has its own server mode, which provides an ova virtual machine. Since the description is too good, I tried it.
The first is that it needs to use several ports, 80, 443, 5222, 5223. This is not negotiable. Since both 80 and 443 are already apache, I don't want to waste a public network ip, so I directly change the bridge mode of the virtual machine to NAT. Then tragedy struck for two days.
The reverse proxy for port 80 is easy, but it took a day to figure out the port 443. Without further ado, paste the configuration directly, apache 2.4:
<VirtualHost *:443>
ServerAdmin [email protected]
ServerName hipchat.test.com
<Proxy *>
Order deny,allow
Allow from all
</Proxy>
SSLEngine On
SSLProxyEngine On
SSLProxyVerify none
SSLProxyCheckPeerCN off
SSLProxyCheckPeerName off
SSLCertificateFile "D:/services/web/Apache24/conf/hipchat/star_hipchat_com_chain.crt"
SSLCertificateKeyFile "D:/services/web/Apache24/conf/hipchat/star_hipchat_com.key"
ProxyRequests Off
ProxyPreserveHost On
ProxyPass / https://192.168.133.201/
ProxyPassReverse / https://192.168.133.201/
</VirtualHost>
The crt and key files can be configured with your own ssl, or you can use the one that comes with hipchat. I directly use the one that comes with it. In the server of hipchat, execute lsof -i:443 and find that it is occupied by nginx, and look directly at nginx The configuration file gets the certificate and private key, and then sz sends it out.
For the reverse proxy in https mode, you need to pay attention to these three lines:
SSLProxyVerify none
SSLProxyCheckPeerCN off
SSLProxyCheckPeerName off
I have searched a lot of configuration and it is not easy to use. The last one is easy to use. The source is: http://serverfault.com/questions/538086/proxyerror-ah00898-error-during-ssl-handshake-with-remote-server
In this way, map 5222 and 5223 with vmware NAT, and you can use it (note that you need to open the corresponding port in the firewall).
hipchat provides a full range of windows, linux, mac, android, ios clients. In the actual test, when the server bandwidth and speed are good, the voice and text effect is good when available, other video and desktop sharing are basically slag...
It takes a long time to start hipchat, mainly because the architecture is too complicated. According to my observation, it includes php, python, java, and it seems to have a little ruby. I also ran an ElasticSearch server for retrieval. The complexity of the architecture is amazing.
What makes hipchat unreliable is that both https://www.hipchat.com/ and https://www.hipchat.com/server are not easy to use in the past two days on weekends, and the service has always been down.
In addition, if you want to test, the document mentions that the hipchat network command can modify the ip address, but be careful that this command takes a long time to complete, and stopping halfway may cause the service to fail (because the ip address is not completely changed)!
I started to use the NAT mode, and after I finally started running, I found that the connection rate of voice and video was very low. In the case of two users, I could communicate once in half a day, and the voice effect was acceptable. Go to independent ip mode and find... but it doesn't work!
In short, the conclusion is that the server of your own host is strongly not recommended!