adamant-scooter-39283
11/30/2022, 4:09 AMhelm install epinio --create-namespace --namespace epinio epinio/epinio --set global.domain=<http://192.168.49.2.sslip.io|192.168.49.2.sslip.io>
After doing a minikube service -n epinio epinio-ui --url
, I’m able to access the Epinio UI via <http://127.0.0.1:63777>
but the admin/password
login is not working (see screenshot). Anyone know why? 🤔
Thanks in advancebroad-dream-81849
11/30/2022, 6:22 AM<https://epinio.192.168.49.2.sslip.io|https://epinio.192.168.49.2.sslip.io>
. Can you try that one? 🙂adamant-scooter-39283
11/30/2022, 1:31 PMminikube service -n epinio epinio-ui --url
so minikube can expose the epinio-ui
service in my localhost
url like this:
➜ minikube service -n epinio epinio-ui --url
😿 service epinio/epinio-ui has no node port
<http://127.0.0.1:54256>
When I access <http://127.0.0.1:54256>
it gives me the Epinio UI screen but when trying to login with admin/password
it is giving me the error I sent in the screenshot above.minikube ip
which is 192.168.49.2 but because the Epinio UI is loading on localhost (http://127.0.0.1:54256) redirected by minikube (with the command minikube service -n epinio epinio-ui --url
) it cannot get to the correct route in some sense.broad-dream-81849
12/01/2022, 2:39 PM-> % minikube service -n traefik traefik --url
<http://127.0.0.1:58766>
<http://127.0.0.1:58767>
helm upgrade --install epinio epinio/epinio \
--namespace epinio \
--create-namespace \
--set global.domain="<http://192.168.49.100.sslip.io|192.168.49.100.sslip.io>" \
--version 1.5.1 \
--wait
<https://epinio.127.0.0.1.sslip.io:58767>
address