Running Sametime docker on a multi-ip server

HCL Sametime Sametime Forum
,
1

Hi everybody


I have installed Sametime Premium 12 Docker version.

My server has multiple IP addresses and another service is listening ports 80 and 443 binded on a specific IP.

To bind SameTime to a different IP I modified the following lines in the .env file

# Exposed HTTP port.
HTTP_PORT=xx.tt.zz.ww:80

# Exposed HTTPS port.
HTTPS_PORT=xx.tt.zz.ww:443


# IP address of the Docker host
DOCKER_HOST_ADDRESS=xx.tt.zz.ww

and both Sametime meetings and chat works well

but if I try to create a meeting from the chat window the system generate a link like this:

https://sametime.host.name:xx.yy.zz.ww:443/meeting/MeetMe.I5MyjuxKmGVQ47WgEccLXu

that is clearly wrong

Is it possible to fix this?

Thanks a lot
tommaso

2

Please send this up as a case so we can investigate.

3

how can I send a case?

(sorry but I don't know)

4

In the menu above - click "Customer Support" and then click "Create Product Case".

5

@Anthony Payne How do other forum members get the results/answers, when this and other questions in this forum are handled as a case?

6

if HCL Support will publish technote, this would be a great solution. Support should not only solve but focused on sharing knowledge in Technotes, so customers can solve cases themself.

7

Hi everybody,

I opened the case, as suggested, and with the support of HCL we found this workaround:


1) the .env file remains untouched
================

...

# Exposed HTTP port.
HTTP_PORT=80


# Exposed HTTPS port.
HTTPS_PORT=443

# IP address of the Docker host
DOCKER_HOST_ADDRESS

...


2) while the changes are done in the nginx secion of the docker-compose.yml file
=================

...

nginx:
image: hclcr.io/st/meetings-web:${BUILD_LEVEL}
restart: ${RESTART_POLICY}
ports:
- "xx.tt.zz.ww:80:80"
- "xx.tt.zz.ww:443:443"

...

It is a workaround because we renounce to use the HTTP_PORT and HTTPS_PORT parameters but it works.

Thanks to HCL and everybody who helped.

Tommaso