Skip to main content

website does not work after publishing and connecting to godaddy

Mik O

Please check: https://www.drdavejenkins.com/

It was working generally previously on computers but not on mobile phones using vpn.

Now it seems to have an error with dns or ssl. "Your connection to this site is not secure"
"

This site can’t be reached

drdavejenkins.com’s server IP address could not be found.

Try:

ERR_NAME_NOT_RESOLVED"

 

 

 

 

0

Comments

10 comments

Date Votes
  • KC George

    Hello Mik,

    We see the design below when visiting your website. If you recently changed your name servers from Cloudflare to GoDaddy, users may encounter the above error in some parts of the world, until the new name servers are fully propagated. The above error will disappear within 24-30 hours when the DNS propagation completes.

    0
  • Mik O

    Hi KC George, thank you for your reply. We have had ongoing issues since mid-July when I first published the website. It initially wasn't working on mobile phones using VPN and support here said it was working for them, so I did some research and found that DNS propagation using DNS checker showed that the A record for the domain was not resolving in many locations worldwide.

    So I changed to Cloudflare to see if it would resolve it, but it did not. So I changed back to GoDaddy.
    Could you please confirm:

    • Are there any known VPN-related access restrictions or IP blocks on Brizy Cloud infrastructure?
    • Could there be DNS propagation issues or configuration problems on your end affecting accessibility?
    • Is there any additional setup required to ensure reliable access for VPN users?
    0
  • KC George
    • Edited

    Hello Mik,

    Let me answer your questions.

    1. Are there any known VPN-related access restrictions or IP blocks on Brizy Cloud infrastructure? Brizy Cloud websites are usually available when accessed over a VPN. We have not received complants about VPN access from other users.
    2. Could there be DNS propagation issues or configuration problems on your end affecting accessibility? DNS propagation issues can affect any website, not just Brizy Cloud websites. We use a web application firewall and some uninteneded users could get blocked. We need to investigate this on a case to case basis. 
    3. Is there any additional setup required to ensure reliable access for VPN users?. No addtional setup is required from your side to make a website accessible over VPNs.

    Please follow these steps.

    • Kindly wait till DNS Checker shows GoDaddy Name servers in all available locations around the world at https://dnschecker.org/#NS/drdavejenkins.com 
    • Check the website using a VPN to see if it is inaccessible from any location.
    • Share with us the name of the VPN provider and the specific locations from where the website is inaccessible.

    Once we hear from you, we will investigate this issue.

    0
  • Mik O

    Still doesn't work on mobile using VPN - specifically Nord VPN. I tried Argentina, Los Angeles, Sydney, New Zealand, Amsterdam, etc and they all just say "This site can't be reached. DNS address could not be found." This has been the same issue since I first reported it July 18th (I was told then that it worked fine).

    0
  • KC George

    Hello Mik,

    Kindly follow the troubleshooting steps suggested at https://support.nordvpn.com/hc/en-us/articles/20095679510801-I-can-t-access-websites-or-apps-are-not-working-with-NordVPN. This will help identify if the issue is on Nord VPN side. Kindly get back to us with your findings.

    0
  • Mik O

    Tested all their links/tests and it's fine. I've had friends test it from various locations - just like in July, some work fine others don't.

    Even without VPN. Here's one from a friend (no vpn).

    0
  • Mik O

    0
  • KC George
    • Edited

    Hello Mik,

    I used these services to check your website's SSL certificate and and they confirmed that it is valid.

    1. https://www.ssl.org/
    2. https://www.sslshopper.com/ssl-checker.html#hostname=https://www.drdavejenkins.com/
    3. https://www.geocerts.com/ssl-checker

    Kindly request your friends to access your website from an altenate browser (other than Safari) and check if the error persists. If the above error is specific to Safari browser, request them to follow the solution provided at https://discussions.apple.com/thread/255057550?sortBy=rank

    0
  • Mik O

    Hi KC George,

    Can you please check this site: https://www.ssllabs.com/ssltest/analyze.html?d=www.drdavejenkins.com

    It shows some issues and potential solutions. Is there anything we can do about it? 

    1. Cipher Suite Weakness and Compatibility

    • The server is supporting a weak cipher suite (TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) with SHA-1 and CBC mode.
    • Some modern clients, including Safari on iOS and some VPN clients, may reject weak or deprecated cipher suites for security reasons.
    • If the client refuses all available cipher suites offered by the server, the TLS handshake fails, causing connection failure.

    2. Protocol or Cipher Suite Mismatch with Java Clients

    • Though Java clients are different from mobile browsers, this mismatch indicates the server’s TLS settings might be too restrictive or incompatible.
    • Mobile Safari and VPN clients often have strict TLS requirements similar to modern Java clients.
    • If your server only supports certain cipher suites incompatible with these clients, they cannot establish a secure connection.

    3. Session Resumption Not Working

    • While session resumption itself won’t outright block connectivity, its absence can lead to longer connection times and in some cases timeouts on slower or unstable networks such as VPNs or mobile data.
    • This can worsen user experience or cause perceived failures.

    4. SNI Requirement

    • Combined with the above, if clients do not fully support SNI or your server doesn’t handle non-SNI clients well, connection failures will increase.
    • NordVPN’s network or certain mobile Safari versions might be affected by this.

    Conclusion

    • The weak cipher suites and protocol mismatches are very likely contributors to the site not working on NordVPN mobile apps and Safari on iPhones.
    • These clients tend to enforce stricter security than desktop browsers or other environments.

    Recommended Next Steps

    1. Disable weak cipher suites like TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA.
    2. Enable modern cipher suites with AES-GCM and SHA-256 or better.
    3. Ensure TLS 1.2 and 1.3 are enabled and preferred.
    4. Test your site again using SSL Labs to confirm improvements.
    5. Check session resumption settings to improve connection stability.

     

     

    0
  • KC George

    Hello Mik,

    SSL Labs graded your website's SSL certificate with an A+. 

    We will escalate these two suggestions from the AI agent to our developers and will investigate the possibility of implementing them.

    1. Disable weak cipher suites like TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA.
    2. Enable modern cipher suites with AES-GCM and SHA-256 or better.
    0

Please sign in to leave a comment.

Didn't find what you were looking for?

Ask a Question