Issues with connectivity can happen due to multiple reasons including socket errors, closed ports, SSL authentication, servers being offline, and code bugs.
If you experience issues connecting to either the OT&E or Production Servers, please follow the steps below for a debug of the connectivity issues. If at the end of it you are still unable to verify the problem, please use the Support function to contact our support staff and provide us with all the output from the specified commands below as well as which step you encountered an error.
Testing internet connectivity to servers
Where HOST is the server you are trying to connect to. If packets are getting sent through and there is no packet loss, it means that the server is online and the error lies somewhere else. If you cannot PING, there is most likely an internal error on your network.
Identifying correct routing and IP whitelisting
traceroute HOST (tracert HOST for Windows)
Where HOST is the server you are trying to connect to.
Connecting to our port
telnet HOST PORT
Where HOST is the server you are trying to connect to, and PORT will be 3121. This will test if port 3121 is open and allowing information to flow through it to our port. If you cannot connect to the port using telnet it means that the port is not opened for communication. Please check the permissions on your firewall if you have one active.
Connecting using SSL
openssl s_client -connect SERVER:PORT -cert DOTCRTFILE -key DOTKEYFILE
The above applies to all registrars on the Production server, and only registrars who have provided SSL certificates for the OT&E server. The above command uses the opensource "openssl" libraries to connect to the server. If you cannot connect to the server using the abovementioned command, it means that either you have not provided us with your certificate (so we cannot accept the SSL handshake) or you have provided the incorrect files in the command. To resolve this, please make sure that the following has been completed:
1. Our server certificate is loaded on your side if your server requires SSL authentication from our server. The file can be downloaded further up in this FAQ.
2. You have provided your certificate and private key on connection, as our servers require Dual SSL. That is usually the .pem file. Different operating systems and server configurations require different files. Please make sure that when using a specific software, the correct keys and files have been loaded correctly.
Debugging of code.
Please note that we do not provide any form of support for specific code or programming languages.