Error: ESOCKETTIMEDOUT while implementing A/B target | Community
Skip to main content
Madhusudan_S
Level 2
January 24, 2022
Solved

Error: ESOCKETTIMEDOUT while implementing A/B target

  • January 24, 2022
  • 1 reply
  • 1814 views

Hi Team,

 

We are implementing A/B Targeting for one of the site but while adding URL during visual composer it showing following error

 

Error: ESOCKETTIMEDOUT
   at Object.error (/var/www/vizproxy/modules/utils/common.js:106:15)
   at PatchedRequest.onError (/var/www/vizproxy/modules/proxy_response_handler.js:61:31)
   at emitOne (events.js:82:20)
   at PatchedRequest.emit (events.js:169:7)
   at ClientRequest.<anonymous> (/var/www/vizproxy/node_modules/request/request.js:819:16)
   at ClientRequest.g (events.js:260:16)
   at emitNone (events.js:67:13)
   at ClientRequest.emit (events.js:166:7)
   at TLSSocket.emitTimeout (_http_client.js:535:10)
   at TLSSocket.g (events.js:260:16)

 

Any one can help /suggestion for this issue

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Gokul_Agiwal

Hi @madhusudan_s 

It seems like this issue Error: ESOCKETTIMEDOUT is more about network related  / connection issues and nothing with Target so I would suggest to check your URL and it's implementation. 

 

1 reply

Gokul_Agiwal
Community Advisor
Gokul_AgiwalCommunity AdvisorAccepted solution
Community Advisor
January 24, 2022

Hi @madhusudan_s 

It seems like this issue Error: ESOCKETTIMEDOUT is more about network related  / connection issues and nothing with Target so I would suggest to check your URL and it's implementation. 

 

Madhusudan_S
Level 2
January 24, 2022

Hi @gokul_agiwal 

Yes, you are correct when i used different website URL .experience is loading loading perfectly but when when I using my stagging site URL it showing above error. anything we can sort at domain level

 

My Target logg working perfect with 200 request log

 

Thanks & Regards,

Madhusudan Sura

Adobe Employee
January 26, 2022

@madhusudan_s  I would recommend whitelisting the following IPs for your staging environment and then try enabling EEC: https://experienceleague.adobe.com/docs/target/using/experiences/vec/troubleshoot-composer/troubleshooting-issues-related-to-the-enhanced-experience-composer-eec.html?lang=en 

 

This should be helpful in accessing the staging URL within VEC.