Sametime 12 Proxy with reverse proxy

Hi everybody,

has anyone successfully configured a reverse proxy server with Sametime12?

I'm asking, because I have some problems

Background:

- In Sametime 12 everything is a container

- When installing in a single Server, using only Docker, the Sametime Chat Proxy can be reached with "MEETINGS_HOST/chat"

- We want to use something like "chat.company.com" for webchat, "sametime.company.com" for Notes Chat and "meet.company.com" for Meetings

Meetings and Sametime are not a Problem, because we can set the Hostname for Meetings and Notes Chat is on another Port.

So I tried to use a Nginx Proxy on another server to send requests from "chat.company.com" to "meet.company.com/chat", which is the Proxy/Webchat.

The Problem seems to be that the integrated Nginx of the Docker deployment has the "nosniff" header option set. This is a problem for a reverse Proxy server, because it can't determine mime-types.

I can manually edit the Nginx config and comment the header. But that doesn't persist.

Ist there another option than modifing the Docker image?

Thanks

Florian

Simple answer -

You don't need anything other than an alias for a docker deployment.

https://webchat.company.com/chat

https://meetings.company.com/meeting

against the same docker deployment will work just fine without any additional steps.


But that is sort of my problem.

A user has to type "/chat" behind "webchat.company.com". I want "webchat.company.com" to always go to the Webchat/Proxy.

Because any request without context automatically redirects to "/meetings".

And I don't want to just do a redirect from "webchat.company.com" to "meet.company.com/chat", because that would confuse users.

If you are comfortable making changes to the meet.conf file (in the sametime-config/nginx path)

You can copy that file to a new location ('custom-config' folder that is parallel to the 'sametime-config' folder).

Make your changes to the new copy.

and then mount it to the nginx volumes by adding this line in the nginx section of docker-compose.yml --

./custom-config/meet.conf:/defaults/meet.conf

and that should prevent it from being overwritten.

You should be able to modify meet.conf so that you are hostname specific for /chat and /meeting redirects - but that is up to your skill. :D

Note: This is considered a customization - we'll do our best to support you with it, but if there is an issue, you may have to go back to defaults until we sort it out. I've done some limited testing with this concept for a different issue.

Hey Anthony,

thank you. Now I can get to tinkering :)

@Anthony Payne for this to work do you need to do anything else apart from point a DNS record at the Docker server?

Reason I ask is that the server is setup as meetings.acme.com all works fine as stated before and if I go to meetings.acme.com/chat web chat works, however we also have webchat.acme.com pointed at the server but that doesn't work at all for anything but it pings with the correct ip etc.

Hi Richard -

See - https://help.hcltechsw.com/sametime/1201/admin/t_different_hostname.html

Thanks Anthony I had been searching for that for ages but wasn't expecting it to be listed in the meetings sub menu :)