# e-Signet Startup Error: Connect Timeout to Config Server **URL:** \ **Category:** Developer\ **Created:** [November 19, 2025, 10:56am UTC](https://community.mosip.io/t/e-signet-startup-error-connect-timeout-to-config-server/2399 "2025-11-19T10:56:30Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Jawahar](https://avatars.discourse-cdn.com/v4/letter/j/779978/32.png) [@Jawahar](https://community.mosip.io/u/Jawahar)\ **Post date:** [November 19, 2025, 10:56am UTC](https://community.mosip.io/t/e-signet-startup-error-connect-timeout-to-config-server/2399/1 "2025-11-19T10:56:30Z")
Hello everyone, 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? Thank you! ---
**Author:** ![Prathmesh\_Jadhav](https://dub1.discourse-cdn.com/flex017/user_avatar/community.mosip.io/prathmesh_jadhav/32/1628_2.png) [@Prathmesh\_Jadhav](https://community.mosip.io/u/Prathmesh_Jadhav)\ **Post date:** [November 20, 2025, 11:10am UTC](https://community.mosip.io/t/e-signet-startup-error-connect-timeout-to-config-server/2399/2 "2025-11-20T11:10:54Z")
Hi **[Jawahar](https://community.mosip.io/u/jawahar)**! Thanks for reaching out. We are looking into your query/feedback and will get back to you soon! Until then, happy coding with MOSIP! Best regards, Team MOSIP ---
**Author:** ![zesu2210](https://avatars.discourse-cdn.com/v4/letter/z/ad7895/32.png) [@zesu2210](https://community.mosip.io/u/zesu2210)\ **Post date:** [November 20, 2025, 11:51am UTC](https://community.mosip.io/t/e-signet-startup-error-connect-timeout-to-config-server/2399/3 "2025-11-20T11:51:25Z")
Hi @Jawahar 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: 1. Which **esignet** version are you using, or from which branch did you clone the repository? 2. How are you running **esignet** —manually using Maven commands, or via Docker images? 3. Are you using the **docker-compose YAML file** provided in the **esignet** repository to run the application? 4. Are you running only **esignet** , or other components related to the MOSIP platform as well? 5. 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. Thanks & Regards Zeeshan ---
**Author:** ![system](https://europe1.discourse-cdn.com/flex017/uploads/mosip1/original/1X/f60a343830fe848c9a68e2d1cc654d0cb7fbbaf2.svg) [@system](https://community.mosip.io/u/system)\ **Post date:** [November 30, 2025, 11:52am UTC](https://community.mosip.io/t/e-signet-startup-error-connect-timeout-to-config-server/2399/4 "2025-11-30T11:52:07Z")
Closed on November 30, 2025, 11:52am UTC This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.