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 Jul 16, 2021. It is now read-only.
Running the latest pull from github in my kubernetes cluster I keep getting errors Unexpected token < in JSON at position 0 in the browser console and a spinning wheel.
vendor.ef3063430e06959a3905.bundle.js:727 EXCEPTION: Unexpected token < in JSON at position 0
t.handleError @ vendor.ef3063430e06959a3905.bundle.js:727
Running Chrome browser Version 57.0.2987.133
Monocular deployed in minikube 0.19.0 using helm helm install --name monocular deployment/monocular.
Service started with minikube service monocular-monocular-ui
The monocular-api pods are not reporting any errors.
The text was updated successfully, but these errors were encountered:
Currently, out of the box, Monocular only supports running alongside an Nginx Ingress controller. See the requisites section here. This means that in order to access to the Monocular app, you need to do it through the Nginx ingress controller exposed service instead of from the UI.
I believe that your issue is the same one experienced here #234
There is an issue w.r.t supporting the deployment of monocular without an ingress controller where you can find a workaround #235
Running the latest pull from github in my kubernetes cluster I keep getting errors
Unexpected token < in JSON at position 0
in the browser console and a spinning wheel.Running Chrome browser Version 57.0.2987.133
Monocular deployed in minikube 0.19.0 using helm
helm install --name monocular deployment/monocular
.Service started with
minikube service monocular-monocular-ui
The monocular-api pods are not reporting any errors.
The text was updated successfully, but these errors were encountered: