Closed lindertho closed 3 weeks ago
Hello @lindertho,
thank you for raising this issue. This is a configuration issue on your end. I would suspect that you are using the registry integration feature. For that you need to set the basyx.externalurl
in the aas-env.properties (application.properties) file like this:
basyx.externalurl=http://10.3.1.52:8081
Ah, perfect. Thank you for the help.
Updating the basyx.externalurl
in the aas-env.properties
file resolved the issue.
Summary: There seems to be a problem using the AAS GUI remotely. When the setup example is used and accessed locally, it works fine. However, when the GUI is used remotely through a browser, it sometimes uses invalid localhost IPs even if the correct remote IPs are specified. We are unsure if this is an internal error or an issue on our side.
Steps to Reproduce:
Expected Behavior: The AAS can be accessed remotely.
Actual Behavior: The AAS cannot be accessed.
Screenshots![image](https://github.com/eclipse-basyx/basyx-applications/assets/50629169/00caaf52-5b69-481b-9186-0e17dac46ec0)
Version eclipsebasyx/aas-gui:v2-240515