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
Page should finish loading and present the console.
Actual
Page load hangs. It looks like the culprits are /api and /oapi both attempting to use the IP address for the VM instead of the Public hostname that I just supplied to minishift.
Logs
Chrome's network trace shows a request to:
https://[ip-of-centos-box]:8443/api/v1
https://[ip-of-centos-box]:8443/oapi/v1
https://[ip-of-centos-box]:8443/apis
All of which are initiated from vendor.js. All other page accesses us the public hostname.
Looking at config.js that gets handed down, it has the centos box's IP address and not the hostname.
The text was updated successfully, but these errors were encountered:
Possible that this is user error - do I need to delete the cluster and start it again using the public-hostname flag? (I didn't do that the first time)
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
General information
Steps to reproduce
minishift start --public-hostname localhost
Expected
Page should finish loading and present the console.
Actual
Page load hangs. It looks like the culprits are /api and /oapi both attempting to use the IP address for the VM instead of the Public hostname that I just supplied to minishift.
Logs
Chrome's network trace shows a request to:
https://[ip-of-centos-box]:8443/api/v1
https://[ip-of-centos-box]:8443/oapi/v1
https://[ip-of-centos-box]:8443/apis
All of which are initiated from
vendor.js
. All other page accesses us the public hostname.Looking at
config.js
that gets handed down, it has the centos box's IP address and not the hostname.The text was updated successfully, but these errors were encountered: