Skip to main content

Frequent "Connection could not be established" Errors Recently

Comments

7 comments

  • KHAISAR AHMAD QA Lead

    Hello David, 
    We are observing this issue across different customers belonging to different IA's. Upon some search we identified the IP in the error message is related to a different provider, and this is nothing an issue at Celigo side. We have logged a support ticket with Shopify Partner support to understand if there was any downtime at their systems which caused this issue. We are also raising it for Magento 2. 

    Can you please confirm which IA customers are facing this issue. Is it other than Shopify & Magento 2. Will keep you posted further based on the reply we have from the Shopify or Magento 2 support. 

    Please let us know if anything is requried. 

    Thanks, 

     

     

     
    
    
    0
  • David Gollom Strategic Partner
    Top Contributor
    Celigo University Level 4: Legendary
    Answer Pro
    Great Answer
    Engaged

    Hi Khaisar,

    All of the errors are in Imports going to NetSuite.  Here's and error on a custom flow from FTP to NetSuite,

    Connection could not be established. Target service might be inactive. [connect ECONNREFUSED 23.212.250.72:443]

    I've resolved all the errors at this point to it's hard to find them again.  I'll post more examples if I see them today.  

    0
  • Eric Ito

    Hi Khaisar,

    We are also seeing the same issue recently over the past few days. Like David, ours seems to be a response from NetSuite when importing from Shopify to NetSuite. We are seeing this with the Shopify IA and also in the Returnly IA. Our custom flows are not experiencing the same issues.

    Thanks,
    Eric

    0
  • KHAISAR AHMAD QA Lead

    Hello Eric / David
    Sorry for the delay. We have also raised a support ticket with NetSuite through one of the other customers who is experiencing this issue. Can you as well please raise another ticket to get more press on this issue. If possible can you as well share that Case ID w/ us, so that we can escalate internally to NetSuite and get more details from their side. 

    Thanks

     
    
    
    0
  • Stefan Lindner

    Hi all,

    same issue recently over the past few days also on our end. Like David/Eric we see this error for Shopify IA and custom flows as a response from NetSuite when importing from into NetSuite.

    latest error from today:
    "Connection could not be established. Target service might be inactive. [connect ECONNREFUSED 184.86.251.8:443]"

    IP looks like the one from NetSuite RESTlet endpoint "xxx.restlets.api.netsuite.com" - it resolves to 184.86.251.25 in my case...

    Regards,
    Stefan

    0
  • David Gollom Strategic Partner
    Top Contributor
    Celigo University Level 4: Legendary
    Answer Pro
    Great Answer
    Engaged

    Just got the error again on the 17th of Aug last week.  

    Connection could not be established. Target service might be inactive. [connect ECONNREFUSED 23.212.250.68:443]

    It's a server on their CDN.  

    Tracing route to a23-212-250-68.deploy.static.akamaitechnologies.com [23.212.250.68]

    0
  • KHAISAR AHMAD QA Lead

    Hello David, 
    Can you please raise a support ticket with Celigo, providing the details of the Customer and Shopify Store where you are observing this issue. 
    We already have a Shopify Support ticket open, and as per Shopify team, their systems where down only on Aug5 and later to that this issue hasn't occurred. But as you have experienced this again on Shopify systems, we can share the latest example with them and request for proper resolution and RCA. 

    Please let us know if you think otherwise. 

    Thanks, 

     
    
    
    0

Please sign in to leave a comment.