Skip to main content
Skip table of contents

FAQ Cloudgateway

We recommend using CGW version >= 3.1.21 as earlier versions might cause a 401 websocket error

Since CGW ver. 3.1.20 theres a new property in the CGW config which must replace the previous property:

cg.censhareLogoutUrls:

  • http://${CENSHARE_SERVER_HOST_PORT}/forward/rest/service/webserver/rest/csLogout

  • http://${CENSHARE_SERVER_HOST2_PORT}/forward/rest/service/webserver/rest/csLogout

the previous value was a single-value property cg.censhareLogoutUrl
the new implementation uses cg.censhareLogoutUrls name and must contain an array of all necessary censhare logout URLs

If core-cloud-gateway is runnin gon the same server as the censhare server. Localhost and port 9000 should be used.

  • http://localhost:9000/forward/rest/service/webserver/rest/csLogout

On non cloud systems there is a property in the CGW config which causes the logs to fill up with the following message:

core-cloud-gateway[1154]: {"timestamp":"2025-03-04 03:40:53.799","level":"ERROR","thread":"OkHttp http://localhost:4318/...","logger":"io.opentelemetry.exporter.internal.okhttp.OkHttpExporter","message":"Failed to export spans. The request could not be executed. Full error message: Failed to connect to localhost/127.0.0.1:4318","context":"default"}

To stop this from happening set the following value to false:
management.tracing.enabled: false

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.