I’m facing a startup issue with the e-Signet service and would appreciate some guidance.
Error:
The service fails to start with a Connect Timeout Exception to http://localhost:8888, followed by a Could not resolve placeholder 'mosip.esignet.integration.scan-base-package' error.
My Understanding:
It seems the e-Signet service cannot connect to the local Spring Cloud Config server to fetch its properties.
My Question:
I have the config-server running, but the e-Signet service still times out. Could someone please point me to the correct configuration repository that the local config server should be using for e-Signet? Or is there a common misstep in this setup?
Could you please share more details with us? We’re unable to identify the exact issue you’re facing. It would help if you could answer the following questions:
Which esignet version are you using, or from which branch did you clone the repository?
How are you running esignet—manually using Maven commands, or via Docker images?
Are you using the docker-compose YAML file provided in the esignet repository to run the application?
Are you running only esignet, or other components related to the MOSIP platform as well?
You mentioned running a config-server. Could you clarify—are you referring to our config-server application?
Please note that starting from esignet 1.5.x, users don’t need to provide an external config-server share. Properties can be supplied through the deployment YAML (for Kubernetes) or environment variables (for Docker). Could you explain why you’re providing external properties?
Regarding the error you mentioned: “Could not resolve placeholder”—this typically occurs when only the esignet-service image is used. Currently, we use the esignet-with-plugins image everywhere, which includes all plugins. You need to provide input specifying which plugins you require.