Support » Theme: Customizr » Update error

  • Resolved Anna-Karina

    (@kina60)


    Download error. cURL error 35: OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to downloads.wordpress.org:443 .

    What’s wrong?

    • This topic was modified 1 year, 8 months ago by  Anna-Karina.
Viewing 12 replies - 1 through 12 (of 12 total)
  • same problem.

    same problem on all my WordPress websites 🙁

    Which hosting provider do you use?

    Same issue here. Namecheap shared hosting.

    Just discovered the issue is on all of my namecheap wordpress websites, although I believe that at least one lives on a different server.

    I am having the same issue and I am also hosting with Namecheap.

    I’m thinking it may be something related to this, although I don’t know what EasyWP is, and don’t use it.

    https://status.namecheap.com/archives/35817

    If it doesn’t resolve in a couple of hours I’m going to get on their live chat.

    I contacted Namecheap earlier and they just responded and said, “We would like to let you know that our technicians managed to fix the issue and it should be resolved for now.”

    Thanks for the reports. We suspect some routing issues in a newly deployed data center for WordPress.org. For now, we have reverted back to the old data center while we troubleshoot and resolve the issue.

    Looks like the issue reoccurred few hours ago.
    From Namecheap perspective it looks like this:
    Namecheap has few as-paths to 198.143.164.250 (downloads.wordpress.org), including:

    NC (AS22612) – Cogent (AS174) – Telia (AS1299) – SingleHop (AS32475)
    and
    NC (AS22612) – TATA (AS6453) – Telia (AS1299) – SingleHop (AS32475)

    issue occurs when we use first as-path, and if we reroute traffic via second as-path – everything starts working just fine. Same fix we used to apply a week ago. Does WP have any thoughts, how to avoid such situation in future?

    We’re seeing this too on one of our outbound network paths.

    Changing the route to a different path works fine.

    To be thorough, We use a PFSense device as a router/firewall on the malfunctioning route.

    Bad Traceroute:

    2 gi0-2-0-9.rcr21.b023003-0.phx01.atlas.cogentco.com (38.140.141.185) 0.783 ms 0.795 ms 0.865 ms
    3 be3408.ccr32.phx01.atlas.cogentco.com (154.54.28.145) 0.668 ms 0.609 ms 1.105 ms
    4 be2931.ccr41.lax01.atlas.cogentco.com (154.54.44.86) 12.637 ms be2932.ccr42.lax01.atlas.cogentco.com (154.54.45.162) 12.401 ms be2931.ccr41.lax01.atlas.cogentco.com (154.54.44.86) 12.617 ms
    5 be3359.ccr41.lax05.atlas.cogentco.com (154.54.3.70) 12.908 ms be3243.ccr41.lax05.atlas.cogentco.com (154.54.27.118) 12.484 ms 12.748 ms
    6 telia.lax05.atlas.cogentco.com (154.54.10.10) 12.713 ms 13.038 ms 13.482 ms
    7 dls-b21-link.telia.net (62.115.123.136) 40.476 ms 37.229 ms 37.171 ms
    8 kanc-b1-link.telia.net (213.155.130.179) 47.855 ms 47.723 ms 47.683 ms
    9 chi-b21-link.telia.net (213.155.130.176) 58.302 ms 56.489 ms 56.361 ms
    10 serverhub-ic-324864-chi-b21.c.telia.net (62.115.154.247) 57.010 ms 56.935 ms 57.026 ms
    11 dr6506a.ord03.singlehop.net (108.178.47.247) 56.655 ms agg-gegf150.ord03.singlehop.net (108.178.47.245) 56.634 ms dr6506a.ord03.singlehop.net (108.178.47.247) 56.640 ms

    Good Traceroute:
    2 10.220.205.1 (10.220.205.1) 1.062 ms 2.006 ms 10.222.204.1 (10.222.204.1) 0.996 ms
    3 eth3.3.bb2.cloud.140.1.6.phx0.cwie.net (108.170.0.38) 0.960 ms eth3.2.bb2.cloud.140.1.6.phx0.cwie.net (108.170.0.22) 1.243 ms eth3.3.bb2.cloud.140.1.6.phx0.cwie.net (108.170.0.38) 1.196 ms
    4 ae1-501.cr0-phx1.ip4.gtt.net (216.221.159.25) 1.363 ms phx-b1-link.telia.net (80.239.194.109) 1.245 ms phx-b1-link.telia.net (62.115.42.1) 1.432 ms
    5 xe-0-1-7.cr1-chi1.ip4.gtt.net (141.136.107.189) 144.847 ms 144.784 ms dls-b21-link.telia.net (62.115.135.12) 24.133 ms
    6 ip4.gtt.net (173.205.41.90) 54.778 ms ae26.cs2.iah1.us.eth.zayo.com (64.125.31.254) 54.168 ms kanc-b1-link.telia.net (213.155.130.179) 34.286 ms
    7 chi-b21-link.telia.net (213.155.130.176) 46.569 ms dr6506a.ord03.singlehop.net (108.178.47.247) 52.736 ms chi-b21-link.telia.net (213.155.130.176) 46.500 ms

    Thanks @techsurgeons

    This solidifies the theory about cogentco. We have put a work around in place for now for downloads.wordpress.org and api.wordpress.org.

    Can you confirm the workaround is successful for you too?

Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘Update error’ is closed to new replies.