You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.
for anyone running with the recommended config of having the C-S API behind a reverse-proxy, or moving things to non-standard ports, this isn't going to work. Given we parse the config file to find the shared secret, why don't we also at least sanity-check that we're connecting to a port with the C-S API exposed?
The text was updated successfully, but these errors were encountered:
for anyone running with the recommended config of having the C-S API behind a reverse-proxy, or moving things to non-standard ports, this isn't going to work. Given we parse the config file to find the shared secret, why don't we also at least sanity-check that we're connecting to a port with the C-S API exposed?
The text was updated successfully, but these errors were encountered: