RavenDB Studio cannot be reached using a custom hostname

[ramonsmits]

Symptoms

If a different machine other than localhost is used, RavenDB Studio cannot be reached.

Who's affected

Users of Service control higher than 4.33.0

Root cause

Newer versions of RavenDB bind by default only to localhost for security reasons.

Confirmed workarounds

A workaround is to use an asterisk (*) instead of a machine name, or remote into the machine and access the Raven DB studio using localhost

[DharmishthaVPatel]

Our team has begun investigating the root cause of this issue. We’ll provide updates here as we make progress.

[DharmishthaVPatel]

• Documentation has been updated to clarify that from service control higher than 4.33.0, RavenDB Studio is accessible only via localhost.
• Service control management utility(SCMU) has been updated to fix the link to access the RavenDB Studio while in maintenance mode.
• Changes to SCMU will be released in Service Control 6.8.1