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
I have my OS running under an URL like "https://domain.com:99999/os/". I entered this into the "IP" field which did not work. I took my quiet some time to figure out the I had to enter the domain+port+path into the "IP" field (mostly by trial'n'error and searching the forum), but not the protocol (https) part.
Instead of the "IP" and "Use SSL" fields there should be one single URL field where I could just have entered "https://domain.com:99999/os/".
When implementing the existing installations (configurations) should be migrated to the new URL field when upgrading the app. That is, if "Use SSL" is ticked then prefix the "IP" field with "https://" (otherwise just "http://") for creating the new "URL" field.
The text was updated successfully, but these errors were encountered:
I have my OS running under an URL like "https://domain.com:99999/os/". I entered this into the "IP" field which did not work. I took my quiet some time to figure out the I had to enter the domain+port+path into the "IP" field (mostly by trial'n'error and searching the forum), but not the protocol (https) part.
Instead of the "IP" and "Use SSL" fields there should be one single URL field where I could just have entered "https://domain.com:99999/os/".
When implementing the existing installations (configurations) should be migrated to the new URL field when upgrading the app. That is, if "Use SSL" is ticked then prefix the "IP" field with "https://" (otherwise just "http://") for creating the new "URL" field.
The text was updated successfully, but these errors were encountered: