Closed danielecazzari closed 4 years ago
Hi Daniele
Should be fairly simple to fix -but will need more details pls - send me yr updated info to jeremy.cook@cloudacademy.com and I will try and troubleshoot this for you.
In your environment what is the value of $FRONTEND_PUBLIC_FQDN - to determine this rerun the following:
kubectl get svc aks-nginx-ingress-controller -n nginx-ingress -o json
INGRESS_PUBLIC_IP=$(kubectl get svc aks-nginx-ingress-controller -n nginx-ingress -o=jsonpath='{.status.loadBalancer.ingress[0].ip}')
echo INGRESS_PUBLIC_IP: $INGRESS_PUBLIC_IP
API_PUBLIC_FQDN=api.$INGRESS_PUBLIC_IP.nip.io
FRONTEND_PUBLIC_FQDN=frontend.$INGRESS_PUBLIC_IP.nip.io
echo API_PUBLIC_FQDN: $API_PUBLIC_FQDN
echo FRONTEND_PUBLIC_FQDN: $FRONTEND_PUBLIC_FQDN
Problem resolved - the Ingress resource for the frontend was recreated
Hi,
I'm having issue displaying the frontend portal. To be more specific if I run:
curl -s -i $FRONTEND_PUBLIC_FQDN
this is the result:I tried to navigate logs but didn't found any obvious issue. All pods are running:
Thanks a lot
Daniele
PS: Note I have some issues with nip.io since it's blocked by my company policy. I'm currently using Azure Cloud Shell and a private PC to access it but I wonder if there are alternative solutions.