Error on my site or with the sample application?

maudcarstlf
maudcarstlf Posts: 6
in LFS144 Class Forum

Hi,
I'm currently walking thru the curse and now I'm at the lap 5.2 deploying the Customer-V1. When I open the URL of the service I get following error. from my investigation it looks like a problem of the application but I'm not 100% sure:

Error calling downstream service
ERR_UNESCAPED_CHARACTERS

TypeError [ERR_UNESCAPED_CHARACTERS]: Request path contains unescaped characters
at new NodeError (internal/errors.js:322:7)
at new ClientRequest (_http_client.js:155:13)
at Object.request (http.js:94:10)
at RedirectableRequest._performRequest (/app/node_modules/follow-redirects/index.js:279:24)
at new RedirectableRequest (/app/node_modules/follow-redirects/index.js:61:8)
at Object.request (/app/node_modules/follow-redirects/index.js:511:14)
at dispatchHttpRequest (/app/node_modules/axios/lib/adapters/http.js:262:25)
at new Promise ()
at httpAdapter (/app/node_modules/axios/lib/adapters/http.js:49:10)
at dispatchRequest (/app/node_modules/axios/lib/core/dispatchRequest.js:58:10)

Comments

  • fazlur.khan
    fazlur.khan Posts: 77

    Hello @maudcarstlf,

    I am looking into this error.. I am trying to reproduce this and will get back to you once I find a solution.

    Thank you for your patience.

    regards,
    Fazlur

  • fazlur.khan
    fazlur.khan Posts: 77
    edited May 2024

    Hello @maudcarstlf ,

    Unfortunately I am unable to replicate your error, When I follow the steps, I am able to access the webpage without any errors.

    Can you please try this :-

    export GATEWAY_IP=$(kubectl get svc -n istio-system istio-ingressgateway -ojsonpath='{.status.loadBalancer.ingress[0].ip}')

    Use the gateway IP and access from the browser. If this fails, then
    execute this command : kubectl get svc -n istio-system istio-ingressgateway
    And if the EXTERNAL-IP column shows as pending , then this is not going to work as the external load balancer has not been provisioned.

    Instead, make use of your Node IP and node port of the istio-ingressgateway service and access from the browser.

    For example: In my case : I made use of publicip of my node and port 30909
    like http://35.239.4.160:30909/ --> this worked for me.

    student@cp:~/LFS144x/ch5-security$ kubectl get svc -n istio-system istio-ingressgateway
    NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
    istio-ingressgateway LoadBalancer 10.103.187.172 15021:30880/TCP,80:30909/TCP,443:32057/TCP,31400:30657/TCP,15443:31660/TCP 14m

    Please provide additional information like output of
    kubectl get svc -n istio-system istio-ingressgateway
    kubectl get all

    Hope this help.

  • maudcarstlf
    maudcarstlf Posts: 6

    Hi, next days I'm not able to access my Lab, I will try to reproduce as soon as possible. Thank you.

  • saschpe
    saschpe Posts: 2
    edited January 2025

    I have the same issue but the LoadBalancer works fine (using Minikube tunnel). See discussion at https://forum.linuxfoundation.org/discussion/comment/40661#Comment_40661?utm_source=community-search&utm_medium=organic-search&utm_term=ERR_UNESCAPED_CHARACTERS

Categories

Upcoming Training