Since Android does not always fetch missing intermediates, all Android devices can reject TLS certificates if the server by itself does not include these intermediate certificates. According Android security guidance this issue is well known and remains a standard issue for server setups. The old method of telling users to install the GoDaddy intermediate certificate on their device is now replaced by a best practice: the server should provide the full certificate chain (excluding the root) and rely on the device's trust store first, and only after for not user-installed certificates. In GoDaddy’s official guidance it is said to install intermediate certificates with the issued certificate.
GoDaddy’s repository offers Secure Server Certificate – G2 as intermediate and cross-intermediate options, for build the correct chain. For better compatibility with older clients the repository also has cross certificates , but the root certificate shouldn`t be included in the chain.
Web server (like Apache, Nginx, Plesk, or cPanel) should be provided with intermediate certificates (for GoDaddy: use gd_intermediate.crt.pem or gd_bundle.crt, and add gd_cross_intermediate.crt if needed).
Do not ask users to install CA certificates on their devices. If a device still cannot validate the chain, use OpenSSL s_client or SSL Labs to test which intermediate is missing or if a cross-signed path is needed. After get the correct bundle from GoDaddy’s repository or your hostinger. This schange to server-side chain delivery matches GoDaddy’s current certificate files (gd_intermediate.crt.pem, gd_bundle.crt, gd_cross_intermediate.crt, and gdroot-g2_cross.crt) and Android’s requirement for a complete chain from the server.