In https://github.com/Informatievlaanderen/VSDS-LDESServer4J/issues/1029, it was described that the actuator uses the internal addresses, which makes sense, as Spring Boot uses this internal address everywhere. This has now been fixed, where the property ldes-server.host-name is used to bind the internal address to this, which replaces the functionality of the already existing property server.address.
This change comes with the precaution that the application will not startup when the server cannot be bound to ldes-server.host-name.
In https://github.com/Informatievlaanderen/VSDS-LDESServer4J/issues/1029, it was described that the actuator uses the internal addresses, which makes sense, as Spring Boot uses this internal address everywhere. This has now been fixed, where the property
ldes-server.host-name
is used to bind the internal address to this, which replaces the functionality of the already existing propertyserver.address
. This change comes with the precaution that the application will not startup when the server cannot be bound toldes-server.host-name
.