If running databox (e.g.) in a VM and exposing it via non-standard ports, the core-ui Javascript still attempts to use the https with no port (i.e. port 443) to access core-ui server API and therefore these calls fails.
It would be useful if it used the same port as the UI is loaded from. It would also suffice if there was a way to configure non-standard ports #307 but this isn't strictly the same issue.
Should have said, that was core-ui 0.5.2-dev, running on a local browser (Chrome, outside the VM)
If running databox (e.g.) in a VM and exposing it via non-standard ports, the core-ui Javascript still attempts to use the https with no port (i.e. port 443) to access core-ui server API and therefore these calls fails.
It would be useful if it used the same port as the UI is loaded from. It would also suffice if there was a way to configure non-standard ports #307 but this isn't strictly the same issue.
Should have said, that was core-ui 0.5.2-dev, running on a local browser (Chrome, outside the VM)