Title: Christopher Neuman's Replies | WordPress.org --- # Christopher Neuman [ ](https://wordpress.org/support/users/neumanc/) * [Profile](https://wordpress.org/support/users/neumanc/) * [Topics Started](https://wordpress.org/support/users/neumanc/topics/) * [Replies Created](https://wordpress.org/support/users/neumanc/replies/) * [Reviews Written](https://wordpress.org/support/users/neumanc/reviews/) * [Topics Replied To](https://wordpress.org/support/users/neumanc/replied-to/) * [Engagements](https://wordpress.org/support/users/neumanc/engagements/) * [Favorites](https://wordpress.org/support/users/neumanc/favorites/) Search replies: ## Forum Replies Created Viewing 6 replies - 1 through 6 (of 6 total) * Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) In reply to: [Error on our website](https://wordpress.org/support/topic/error-on-our-website/) * [Christopher Neuman](https://wordpress.org/support/users/neumanc/) * (@neumanc) * [7 hours, 44 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. * Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) In reply to: [Wp-admin and wp-login.php redirect to homepage, not admin](https://wordpress.org/support/topic/wp-admin-and-wp-login-php-redirect-to-homepage-not-admin/) * [Christopher Neuman](https://wordpress.org/support/users/neumanc/) * (@neumanc) * [1 day, 2 hours ago](https://wordpress.org/support/topic/wp-admin-and-wp-login-php-redirect-to-homepage-not-admin/#post-19043978) * Do you still have access to your WordPress admin dashboard (wp-admin), and do you have any recent backups of the website? * If you have access to WordPress and a usable backup, there may be options to recover or migrate the website without relying on your current hosting provider. * Email can also be migrated to another provider as long as you have the login credentials for your existing mailboxes and the current mail server is still accessible. With IMAP, you can typically transfer your existing emails and folders without losing your email history. You’ll also need access to your domain’s DNS settings to direct new emails to the new provider. * The main things I’d want to establish first are whether you have WordPress admin access, whether any backups are available, and whether you can still access your email accounts. * Happy to help troubleshoot further here if you have any questions. * Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) In reply to: [Gutenberg editor not loading – Cloudflare 522 on JS react files](https://wordpress.org/support/topic/gutenberg-editor-not-loading-cloudflare-522-on-js-react-files/) * [Christopher Neuman](https://wordpress.org/support/users/neumanc/) * (@neumanc) * [1 day, 20 hours ago](https://wordpress.org/support/topic/gutenberg-editor-not-loading-cloudflare-522-on-js-react-files/#post-19043202) * [@kcaluwae](https://wordpress.org/support/users/kcaluwae/) Based on what you found, I really don’t think this is a Gutenberg or WordPress problem. * The biggest clue is everything works when you turn off the Cloudflare proxy, but you start getting the 522 errors again as soon as Cloudflare is enabled. Since you’re also seeing the same thing on two sites on the same Hetzner server, I would focus on Cloudflare and the connection between Cloudflare and your server. * I would first check your Cloudflare settings. If you have WAF rules, rate limiting, Bot Fight Mode, Rocket Loader, or any custom Cache Rules enabled, try temporarily disabling them one at a time and see if the problem goes away. * I would also check your DNS records in Cloudflare. If you have an AAAA record, make sure IPv6 is actually configured and working correctly on the server. * Since this is a 522, I would also check the server itself to make sure something isn’t blocking or rate limiting Cloudflare. This could be the Hetzner firewall or something on the server such as CSF, Fail2Ban, firewalld, iptables/nftables, ModSecurity, or another security system. * One thing that could really help narrow this down is watching your server access/ error logs while you reproduce the problem. When one of those JavaScript files gets a 522, check if the request actually shows up in your web server access log. * If the request never reaches the web server, then I would suspect something is blocking or timing out the connection between Cloudflare and the server. * Since everything works perfectly when you bypass Cloudflare, I wouldn’t spend much more time changing WordPress, Gutenberg, PHP, or plugins. I would focus on figuring out what is happening between Cloudflare and the Hetzner server. * Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) In reply to: [Error on our website](https://wordpress.org/support/topic/error-on-our-website/) * [Christopher Neuman](https://wordpress.org/support/users/neumanc/) * (@neumanc) * [2 days, 2 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. * Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) In reply to: [Gutenberg editor not loading – Cloudflare 522 on JS react files](https://wordpress.org/support/topic/gutenberg-editor-not-loading-cloudflare-522-on-js-react-files/) * [Christopher Neuman](https://wordpress.org/support/users/neumanc/) * (@neumanc) * [2 days, 3 hours ago](https://wordpress.org/support/topic/gutenberg-editor-not-loading-cloudflare-522-on-js-react-files/#post-19042938) * The first thing I would do is temporarily disable the Cloudflare proxy for the domain (turn the orange cloud gray) and test the site again. Since you mentioned Gutenberg works when Cloudflare is bypassed, that should help confirm the problem is between Cloudflare and your hosting server. * A 522 generally means Cloudflare is having trouble connecting to the origin server. * I would also check with your hosting provider to make sure the server isn’t experiencing an outage, high load, networking problems, or other issues. Since you’re seeing the same problem on two WordPress sites hosted on the same server, that makes me suspect the server or its firewall/security configuration before an individual WordPress plugin. * While reproducing the problem, check your website/server error logs. If you’re using cPanel, Plesk, or DirectAdmin, you should be able to view these from your hosting control panel. * I would also check whether Wordfence or a server-level firewall/security system is blocking or rate-limiting Cloudflare IP addresses. * Once you find and correct the underlying issue, turn the Cloudflare proxy back on and test again. * Since both sites on the same server are affected and they work when Cloudflare is bypassed, I wouldn’t focus on the caching plugin first. I’d start with the host/server, firewall, and the connection between Cloudflare and the origin. * Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) In reply to: [Unable to access website](https://wordpress.org/support/topic/unable-to-access-website-12/) * [Christopher Neuman](https://wordpress.org/support/users/neumanc/) * (@neumanc) * [2 days, 4 hours ago](https://wordpress.org/support/topic/unable-to-access-website-12/#post-19042830) * Hi Jim, * I wouldn’t delete the site or reinstall WordPress just yet. Your existing content and database may still be perfectly fine. * The first thing I’d investigate is the Charity Hub theme. WordPress is reporting a fatal error involving that theme, and since you’re running PHP 8.5, compatibility with the older theme is a possibility. * Before making changes, create a complete backup of your website files and database. * If you have access to Bluehost’s file manager, you can temporarily rename the Charity Hub theme folder under wp-content/themes/. WordPress may then fall back to another installed default theme, allowing you to regain access. * I’d also recommend checking the PHP error logs to identify the exact cause of the fatal error. * Once you regain access, you can determine whether the existing theme can be updated or whether rebuilding with a modern, maintained theme makes more sense. * There’s a good chance you can recover the existing installation without starting over. - This reply was modified 2 days, 4 hours ago by [Christopher Neuman](https://wordpress.org/support/users/neumanc/). Viewing 6 replies - 1 through 6 (of 6 total)