-
-
Cloud Connector Standalone Citrix Secure Ticketing Authority (STA) service
-
-
-
-
-
-
Fixed Issues
This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
Fixed Issues
- OpenSearch circuit breaker causing HTTP 429 errors in large deployments (XASUP-8128)
In large-scale deployments where a high number of DDCs, StoreFront servers, and VDAs were sending AOT logs simultaneously, OpenSearch intermittently rejected requests with HTTP 429 due to the parent circuit breaker tripping. This issue is now resolved.
- Director unable to access logs after enabling AOT Log Server in Studio (XASUP-7776)
When the AOT Log Server is configured using HTTP, the LOCAL_DOWN_ONLY flag is enabled by default. This prevents Director from displaying logs and may result in access errors. This issue has been fixed in Log Server version 2603 and later. When configured in HTTPS mode, the LOCAL_DOWN_ONLY flag is automatically disabled, allowing Director to display logs without additional configuration.
However, when operating in HTTP mode, the LOCAL_DOWN_ONLY flag remains enabled for security reasons and must be manually updated by the user to allow log access.
- Port conflict error when upgrading Log Server (XASUP-7658)
During a Log Server upgrade, the installer incorrectly reported that the configured port was already in use due to a system cache conflict, causing the upgrade to fail on first attempt. This issue is now resolved, and upgrades complete successfully without requiring a retry.
- Log Server authentication key is cleared when updating settings in Citrix Studio (STUD-40505)
Updating the Log Server address and port in Citrix Studio works initially, but if you revisit the settings and modify the Log Server details without re-entering the authentication key, the authentication key placeholder becomes empty after saving, even though the operation appears successful. This results in missing or invalid configuration in Director and Monitor. As a workaround, always re-enter and validate the authentication key whenever modifying Log Server settings. This issue is now resolved in 2603 and in Web Studio release 73.
Share
Share
In this article
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Citrix product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.