Hello,
The minikube ip is 192.168.49.2
Kind regards and thanks
De: Mai Philipp, FG-522 <Philipp.RA.Mai@xxxxxx>
Enviado el: jueves, 5 de diciembre de 2024 13:03
Para: jbrazuelo@xxxxxx; 'tractusx developer discussions' <tractusx-dev@xxxxxxxxxxx>
Asunto: AW: [tractusx-dev] Deploy Tractus-X locally
So, you are using your local lookup and the identical IP configs, as given in the install documentation as an example:
>>In the following steps, replace 192.168.49.2 with your minikube ip if it differs.
What is the actual IP-address of your minikube? Is it 192.168.49.2? “minikube ip” should give you an answer. Is your client also in the same subnet as your minikube? If not do you have the appropriate routes configured?
Hello,
I don’t any proxy and the result of the command nslookup is the following:
nslookup portal.arena.test
Server: 127.0.0.53
Address: 127.0.0.53#53
Non-authoritative answer:
Name: portal.arena.test
Address: 192.168.49.2
Kind regards and thanks
From the information given I would first try to verify that networking is working as intended.
Assuming you have followed the tutorial:
- Please check that nslookup portal.arena.test on your client returns the minikube IP
- You could also try disabling any the proxy configuration on your local machine
Kind regards
Philipp
| Sent from outside the BMW organization - be CAUTIOUS, particularly with links and attachments. | | Absender außerhalb der BMW Organisation - Bitte VORSICHT beim Öffnen von Links und Anhängen. |
Hello,
We are deploying Tractus-X locally, following the steps of the link:
https://eclipse-tractusx.github.io/docs/tutorials/e2e/connect/deployComponents/
When we try to open the site http://portal.arena.test fail

We don't know what could be wrong. If anyone can help us with this problem we would be very grateful.
Kind regards and thanks.