Hi Team,

My website outingx.com was going well.

A few days ago, I saw that it shows that the site is not found but I don't change anything. I talked to my hosting and they said that the site needs to point to this IP (173.236.180.1) so I made the change in the DNS zone. Everything is good then. Today, I checked the same and it seems something changed the IP automatically, and the full website is down. I never used any Cloudflare thing for this website.

Also, check whether my other 2 websites were impacted or not for similar reasons. So please change my IP permanently to my hosting IP so that I don't have any down issues. Let me know the update.

Thanks

    The majority of site errors can typically be resolved using one of the solutions below. It is advised that you troubleshoot using this advice whilst you wait for a member of the Ezoic team to get back to you.

    1. Clear out your browser cache

    There is a chance that you are cached into an older, erroring version of your site. Please clear out your cache or try viewing the URL as domain.com/?nocache. If you see the site is live, you can be assured that it is a caching issue and the site is not actually down

    2. Origin Error

    This includes the following errors: 500, Origin, 520, 403 forbidden, 401, 503. If you are seeing an origin error on the site, we advise you to follow the advice found in this thread: https://community.ezoic.com/d/10310-what-to-do-if-you-see-an-origin-error

    If your host isn’t able to whitelist Ezoic’s IPs, please inform the Ezoic team of this and await potential next steps.

    3. DNS_PROBE_FINISHED_NXDOMAIN

    This means that you need to update the records in your Ezoic DNS settings. Please check to see if the DNS records in Ezoic match up with the DNS records at your host. If they do not, you will need to edit the records in the Ezoic DNS settings. The following guide will help you with this: https://community.ezoic.com/d/11329-what-to-do-if-you-see-a-compatibility-error

    4. SSL errors, such as ‘Your connection is not private’ and ‘NET::ERR_CERT_DATE_INVALID

    We advise you to disable any SSL plugins and SSL at your host. Once you’ve disabled any third party SSL technologies make sure to clear the cache and check if the error persists.

    5. Other errors

    If you are still seeing another kind of error error, send over a screenshot of the specific error message you’re seeing on your site alongside a screenshot of the DNS records from your host to allow the Ezoic team to look into this quicker for you. If you have managed to resolve the error, let us know in the thread!

      naim671102 The site is definitely pointing to 173.236.180.1 - please can you send over a screenshot of your DNS records from your host so that we can take a look?

        You are posting too frequently - please wait before posting again