Title: Error on our website
Last modified: October 12, 2026

---

# Error on our website

 *  [MdGroup IT](https://wordpress.org/support/users/mdgroupit/)
 * (@mdgroupit)
 * [2 days, 9 hours ago](https://wordpress.org/support/topic/error-on-our-website/)
 * As part of IT that owns and operates the domain _[ redundant link deleted ]_.
 * Our company website _[ redundant link deleted ]_ is currently displaying a WordPress
   critical error since September. The website was developed and hosted through 
   a previous outsourced vendor, but the hosting/account credentials were not properly
   handed over to our organization.
 * Our domain currently resolves to the server at 129.121.73.92, with the hostname
   server-_[ redundant link deleted ]_. When accessing the server, it displays a
   message directing the website owner to contact [webmaster@129.121.73.92](https://wordpress.org/support/topic/error-on-our-website/webmaster@129.121.73.92?output_format=md).
 * Could you please confirm whether your organization hosts this server/IP and, 
   if so, advise us on the appropriate process for verifying ownership and recovering
   administrative access to the hosting account.
 * We can provide domain ownership/company documentation through appropriate verification
   process.
 * This is an urgent business website recovery matter, so we would appreciate your
   assistance in identifying the correct account/hosting contact.
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Ferror-on-our-website%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

Viewing 5 replies - 1 through 5 (of 5 total)

 *  Moderator [threadi](https://wordpress.org/support/users/threadi/)
 * (@threadi)
 * [2 days, 8 hours ago](https://wordpress.org/support/topic/error-on-our-website/#post-19042814)
 * The reason for the error should be visible in the error log. You can find it 
   in your hosting area. If necessary, the support of your hosting can help you.
 * Alternatively, you could also enable debugging in WordPress. How to do this is
   described here: [https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/](https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/)–
   also here the support of your hosting can help you if necessary to edit the file
   accordingly.
 * In both cases you should be able to see what the cause is in the logfile.
 *  [adamsharma](https://wordpress.org/support/users/adamsharma/)
 * (@adamsharma)
 * [2 days, 7 hours ago](https://wordpress.org/support/topic/error-on-our-website/#post-19042850)
 * This looks like a hosting access issue rather than just a WordPress error. Since
   you still control the domain, I would suggest contacting the current hosting 
   provider with proof of domain ownership and asking whether they can identify 
   the account holder or help with the recovery process. 
   You can also check whether
   any backups are available through your previous developer or hosting company.
   If you manage to recover the website files and database, you may be able to restore
   the site on another hosting account. We had to look into a similar hosting access
   concern while managing the SAS Accountant website, so I understand how difficult
   it can be when the original developer is no longer available. Before making any
   DNS changes, make sure you have checked the existing email records to avoid disrupting
   your business emails.
 *  [Christopher Neuman](https://wordpress.org/support/users/neumanc/)
 * (@neumanc)
 * [2 days, 6 hours ago](https://wordpress.org/support/topic/error-on-our-website/#post-19042969)
 * It sounds like the critical error may actually be the second problem you need
   to solve.
 * The first priority is identifying the hosting provider (HostGator looks like?)
   and recovering legitimate access to the hosting account. Since the previous vendor
   did not hand over the credentials, I would avoid making DNS changes or attempting
   to rebuild anything until you know what access can be recovered.
 * Once you have hosting access, make a complete backup of the website files and
   database before changing anything.
 * Then check the PHP/error logs. The actual fatal error should be recorded there
   and will usually identify the plugin, theme, PHP file, or other component causing
   WordPress to fail.
 * If you cannot recover the existing hosting account, but your organization controls
   the domain and DNS, you still have options. You can establish new hosting and
   rebuild or restore the site there. I would keep the existing DNS pointed at the
   current server until you’ve determined whether the existing WordPress files and
   database can be recovered.
 * Since the server itself is displaying a webmaster contact address, contacting
   that address and providing proof that your organization owns the domain/company
   seems like a reasonable next step. They may be able to identify the hosting provider
   or account holder, although they should not provide credentials without proper
   verification.
 * I would treat this as a hosting/account recovery issue first and a WordPress 
   repair issue second.
 *  Thread Starter [MdGroup IT](https://wordpress.org/support/users/mdgroupit/)
 * (@mdgroupit)
 * [14 hours, 3 minutes ago](https://wordpress.org/support/topic/error-on-our-website/#post-19044461)
 * Thank you for your replies. I would want to clarify that while we do have the
   mail servers in hostgator, the web site mdgroupco and its details are not in 
   this or either hosted separately from the mail server. The story behind this 
   is earlier there was no person related with IT , it was all handled by admin 
   manager who utilized hostgator for the emails and used mdgroupco domain as mail
   access server. The website was using [ns1.mdgroupco.com.](https://www.nslookup.io/domains/ns1.mdgroupco.com/dns-records/)
   [ns2.mdgroupco.com](https://www.nslookup.io/domains/ns2.mdgroupco.com/dns-records/)
   as ns records but there is no hostgator evidence for the website. Moreover the
   admin manager is telling me to handle it without the previous developer’s access
   on the website which until i get which hosting company is hosting exactly wont
   be able to troubleshoot it further
 *  [Christopher Neuman](https://wordpress.org/support/users/neumanc/)
 * (@neumanc)
 * [10 hours, 52 minutes ago](https://wordpress.org/support/topic/error-on-our-website/#post-19044695)
 * Thanks for the additional information. At this point, I would start looking at
   recovery options rather than continuing to chase down the original hosting provider.
 * A couple of questions:
    1. **Do you control the domain name?** Specifically, do you have access to the 
       domain registrar and the ability to update the nameservers or DNS records?
    2. **Do you have a backup of the website?** This could be a WordPress backup, a
       backup from the previous developer, or even a copy of the website files and 
       database.
 * If you control the domain, you have options even without access to the original
   hosting account.
 * Here’s how I would approach it:
    1. **Set up a new hosting account** under your organization’s control.
    2. **Restore the website from a backup**, if one is available. Make sure you have
       both the WordPress files and database.
    3. **If no backup exists**, I would start rebuilding the website using whatever
       content and images you can recover. The Wayback Machine at archive.org may have
       historical snapshots of your website that you can use as a reference.
    4. **Once the website is ready**, update the domain’s A record or nameservers to
       point to the new hosting environment.
 * One important consideration: Since your email is hosted separately through HostGator,
   be careful when changing nameservers. You’ll need to preserve your existing MX,
   SPF, DKIM, and other email-related DNS records to avoid disrupting email delivery.
 * Personally, I would keep the existing nameservers in place if you have access
   to manage the DNS records and simply update the website’s A record when the replacement
   site is ready.
 * The important thing now is determining whether you control the domain and whether
   a usable backup exists. If you have both, recovery should be relatively straightforward.
   If you only control the domain, rebuilding may be your quickest path forward.

Viewing 5 replies - 1 through 5 (of 5 total)

You must be [logged in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Ferror-on-our-website%2F%3Foutput_format%3Dmd&locale=en_US)
to reply to this topic.

 * In: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
 * 5 replies
 * 4 participants
 * Last reply from: [Christopher Neuman](https://wordpress.org/support/users/neumanc/)
 * Last activity: [10 hours, 52 minutes ago](https://wordpress.org/support/topic/error-on-our-website/#post-19044695)
 * Status: not resolved

## Topics

### Topics with no replies

### Non-support topics

### Resolved topics

### Unresolved topics

### All topics
