HTTP 444 since moving to new server - no issues for over a year before moving

​@JesseJames 

I am unaware of that specific error message, but was able to find this Docusign error codes overview.

Error code: 444  - No response: The client receives no information from the server, including the 444 status code itself.

It appears that your new server is unable to connect to Docusign.
→ Have you read this article, specifically “Allowlists for Docusign eSignature service” and configured your new server accordingly? 

If your Docusign server is in the EU, the correct baseURI should be https://eu.docusign.net.
You can verify this by logging into your Docusign eSignature account as an Administrator.
→ This is not the issue here, as the error code would be most likely 401 - Unauthorized, when making subsequent API calls that require Authentication.

PHP SDK Version 6.1. is outdated and probably 4 years old and may require an update.
The current version 8.4 and can be found here on GitHub.
→ While highly recommended to update to the latest version, this is not the root cause.

I am a bit confused about your last sentence: What level of support are you paying for?
→ Support could check, if your IP address was blocked and may be able to unblock it, but this would probably result in 403 - Forbidden error code.

> Have you read this article, specifically “Allowlists for Docusign eSignature service”

We have read this and verified we are not blocking any Docusign services

> If your Docusign server is in the EU, 

We have verified that our account is still set to use a north american server.

> PHP SDK Version 6.1. is 

As our setup worked fine before the move, we are aiming to ensure we can still use Docusign before upgrading the SDK. This is in our plans to upgrade.

> I am a bit confused about your last sentence: What level of support are you paying for?

We are not paying for Support. We had “assumed”, perhaps incorrectly, that checking if Docusign is blocking our server doesn’t require a paid support account. 

Additional notes: We have verified that other servers in the same geo zone and cloud data center, can indeed see the Docusign API. It appears that only the server with our site on it is blocked from seeing the API. We mentioned this to support and were told on 2 occasions they cannot help us. 

We are open to get this going, but after over 2 months of trying, we are runnign out of possible solutions. 

same here:

curl -v  https://eu.docusign.net/restapi
* Host eu.docusign.net:443 was resolved.
* IPv6: (none)
* IPv4: 185.81.100.106
*   Trying 185.81.100.106:443...
* Connected to eu.docusign.net (185.81.100.106) port 443
* ALPN: curl offers h2,http/1.1
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
*  CAfile: /etc/ssl/certs/ca-certificates.crt
*  CApath: /etc/ssl/certs
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_128_GCM_SHA256 / X25519 / RSASSA-PSS
* ALPN: server did not agree on a protocol. Uses default.
* Server certificate:
*  subject: jurisdictionC=US; jurisdictionST=Delaware; businessCategory=Private Organization; serialNumber=5711317; C=US; ST=California; L=San Francisco; O=DocuSign, Inc.; CN=eu.docusign.net
*  start date: Jan 17 00:00:00 2025 GMT
*  expire date: Jan 17 23:59:59 2026 GMT
*  subjectAltName: host "eu.docusign.net" matched cert's "eu.docusign.net"
*  issuer: C=US; O=DigiCert Inc; CN=DigiCert EV RSA CA G2
*  SSL certificate verify ok.
*   Certificate level 0: Public key type RSA (2048/112 Bits/secBits), signed using sha256WithRSAEncryption
*   Certificate level 1: Public key type RSA (2048/112 Bits/secBits), signed using sha256WithRSAEncryption
*   Certificate level 2: Public key type RSA (2048/112 Bits/secBits), signed using sha256WithRSAEncryption
* using HTTP/1.x
> GET /restapi HTTP/1.1
> Host: eu.docusign.net
> User-Agent: curl/8.5.0
> Accept: */*
>
< HTTP/1.1 444
< Content-Type: text/html
< Vary: Origin
< X-Content-Type-Options: nosniff
< X-DocuSign-TraceToken: 1a59513c-c9e3-41e1-b70e-c5b2953dc508
< X-DocuSign-Node: FR101FE42
< Date: Wed, 05 Nov 2025 11:55:29 GMT
< Content-Length: 54
< Strict-Transport-Security: max-age=31536000; includeSubDomains
<
* Connection #0 to host eu.docusign.net left intact
The custom error module does not recognize this error.

Anyone can help us?

I solved changing ip address! There a way to unban ip?