In the webclient I am seeing an issue where the service is trying to load images and user information and it is failing because it is trying to use a URL that isn't the same as the webclients.
The Sametime community has used the physical server name of the Docker host hclst.acme.com and I can see this in the sametime.ini
The webclient is webchat.acme.com and is set as such in the custom.env file etc. The webchat error I am seeing when trying to load the images and user data is - GET https://hclst.acme.com/stwebapi/userinfo/image/CN=Richard%20Dew,O=acme 404 (Not Found)
If I copy that url and change the hclst bit to webchat it loads the image and works fine.
When you set the URLs - you should use the ones you expect the end user to use.
So - in your example, you should use "webchat.acme.com" during configuration for the hostname.
OK we have the meeting server setup as meetings then a separate URL for the webchat, so I would assume as the main URL is the meetings thats what I should really be using.
To set this after it's gone live would I just change the sametime.ini file ST_COMMUNITY_ID= parameter and restart?
If thats the case do you know if this is going to break anything for users using the notes embedded client? as in will it pop a config change box or ask them to restart notes etc.
I am assuming a docker environment below -
By default, the hostname used is set for both meetings and webchat.
REACT_APP_MEETING_SERVER_HOSTNAME
If you want to override the chat hostname - you can set
REACT_APP_CHAT_SERVER_HOSTNAME
( https://opensource.hcltechsw.com/sametime-doc/v1202/admin/t_different_hostname.html )
Both of these settings are used for the browser access directly, and an alias used for the installed client(s), so long as it resolves properly, is fine.
For installed clients - we default the 'ST_COMMUNITY_ID' in docker-compose.yml to the 'meeting' hostname (since the chat hostname is optional)
STI__Config__ST_COMMUNITY_ID=${REACT_APP_MEETING_SERVER_HOSTNAME}
If you have previously set a ST_COMMUNITY_ID, you should set this to match.
As a rule, this value should match the hostname the user is using in the installed client(s) configuration.
This specific setting can impact awareness for a user's contact list, it has no direct impact on connectivity - its used to associate contacts with a given community server. I would not expect any popups to users based on this.