Failed to execute 'replace' on 'Location'; 'https://' is not a valid URL

[wss29]

hi,
Has anyone encountered this kind of problem before?

the application image runs fine on Kubernetes using the following nginx.yaml, but when I set it up on Theia Cloud, the error mentioned above appears.

apiVersion: apps/v1
kind: Deployment
metadata:
    name: nginxweb
spec:
    selector:
        matchLabels:
            app: nginxweb1
    replicas: 2
    template:
        metadata:
            labels:
                app: nginxweb1
        spec:
            containers:
                - name: nginxwebc
                  image: kiada:0.1
                  imagePullPolicy: IfNotPresent
                  ports:
                      - containerPort: 8080

apiVersion: v1
kind: Service
metadata:
    name: nginxweb-service
spec:
    externalTrafficPolicy: Cluster
    type: LoadBalancer
    selector:
        app: nginxweb1
    ports:
        - protocol: TCP
          port: 80
          targetPort: 8080

[wss29]

hi @JanKoehnlein
We have deployed Kubernetes (k8s) and Theia-Cloud on a Local Area Network (LAN) that is not connected to the internet. Previously, we encountered issues in this setup. However, today, when I connected a computer to the internet, the application ran successfully in Theia-Cloud. On the LAN, though, the same problems persist.

I suspect that the issue might be related to the hosts.configuration.baseHost value. Specifically, ssli.io is a public DNS service that dynamically maps raw IP addresses to domain names. Since the LAN is not connected to the internet, this DNS service may not function properly.

To address this, I tried setting 192.168.0.200 192.168.0.200.sslip.io in the /etc/hosts file, but it didn’t resolve the issue. I also attempted using nip.io, but that didn’t work either.

Have you ever dealt with a similar situation on a LAN? What possible value could I use for hosts.configuration.baseHost in this environment? Note that the baseHost value must be a DNS name and cannot be an IP address, so setting an IP directly is not an option.

[wss29]

hi @JanKoehnlein
I solve the problem on LAN, when deploying on LAN, kubernetes uses coredns as DNS server, but the default corefile can not resolve 192.168.0.200.sslip.io , so we need to add it to the corefile

1. edit coredns configmap, add hosts
   kubectl edit configmap coredns -n kube-system
   
2. restart Coredns pod
   kubectl delete pod -n kube-system -l k8s-app=kube-dns