<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>hexonet on</title><link>https://docs.whmcs.com/9-1/tags/hexonet/</link><description>Recent content in hexonet on</description><generator>Hugo -- gohugo.io</generator><atom:link href="https://docs.whmcs.com/9-1/tags/hexonet/index.xml" rel="self" type="application/rss+xml"/><item><title>HEXONET Disconnections and Failures</title><link>https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-domains/hexonet/hexonet-disconnections-and-failures/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-domains/hexonet/hexonet-disconnections-and-failures/</guid><description>Diagnoses HEXONET Disconnected and Authorization Failed errors by checking credentials in Domain Registrars settings, disabling two-factor authentication or creating a restricted API user, reviewing IP address restrictions, whitelisting ports 80 and 443, and confirming test versus production HEXONET OTE credentials aren&amp;rsquo;t mismatched.</description></item><item><title>HEXONET Empty Response Errors</title><link>https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-domains/hexonet/hexonet-empty-response-errors/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-domains/hexonet/hexonet-empty-response-errors/</guid><description>Fixes the HEXONET Empty response from API error by testing connectivity with ping api.ispapi.net from the WHMCS server command line and whitelisting ports 80 and 443 in the server firewall.</description></item></channel></rss>