Installed the ST Proxy 11.5 with our errors (self signed certificate).
But when we try to logon, we got the error "Sametime is temporarily not available".
Installed the ST Proxy 11.5 with our errors (self signed certificate).
But when we try to logon, we got the error "Sametime is temporarily not available".
Check if the Proxy Server can connect to the community server.
Is the ST Proxy server on the same Machine as ST Community? If so, check if you are not having any port "collisions".
Proxyserver is installed on the same machine. Loginpage on 8443 opens correctly. I think there a no port conflicts.
Is Sametime Community Server running? Do you see any errors in the Community Logs? I would also check the connectivity to the Community Server and MongoDB.
Port 1516 for the Communinty Server and 27017 for the MongoDB.
Community Server is running. When looking at the Logs, i found this:
Anwendungsname: unknown type(0x14c3)
ok, so you have to add the type of the client in the sametime.ini settings.
This article will help:
https://www.assono.de/blog/neue-sametime-client-ids
Is the community server on the 11.5 release as well?
We are not using the VPS_ALLOWED_LOGIN_TYPES... there is only the entry for VPS_PREFERRED_
Community Server is at Version 11.5 as well.
Hello Marcus,
is this a new installation ?
There are some consideration you can get this error.
Did you check your sametime<date>.log for errors ?

Yesterday we had the same problem on a new installation with a defekt in the userinfoconfig.xml - after corrected the file/structure the Login was possible.
Entered the correct LTPA entries into the Sametime.ini and IT WORKS! Thank you!
I would add it there, if not already there, and restart the server.
If that does not help, try setting the trace in the sametime.ini, maybe you will get a clearer message of what the issue is.
Alexander also has a point. If you are having a formatting issue with "userinfoconfig.xml" you should see an error message in a console (st community server) when the server is starting up.
@Marcus Prell
Hello Marcus
First try this:
instead of using the http(s)://<stproxyserver>/chat
try using the classic client
http(s)://<stproxyserver> /stwebclient/index.jsp
if you are not able to login with the classic client
then you will want to check your proxy server logs to make sure that the proxy server did in fact connect to
the community server.
if however you are able to login the classic client then you may have something else going on.
and would recommend that you collect
stdiagzip from community server, a copy of the logs and Conf directory from the Proxy server and open a case so that we can review your config and assist you further
Please let me know if his was helpful