Website unavailable, returning errors, or no longer loading correctly?
The visible error isn’t always the real cause. We investigate the complete stack — DNS, Cloudflare, SSL, NGINX/Apache, PHP-FPM, MySQL/MariaDB, Redis, WordPress, server resources, firewall, Linux or the provider — to find where the failure actually is.
What each HTTP error usually means
PHP errors, a broken plugin/theme, bad .htaccess, memory exhaustion, wrong permissions. We check server logs, not just swap plugins.
Usually the web server can’t reach PHP-FPM — stopped service, socket problem, overloaded workers, or a crashed backend.
A request is taking too long — slow PHP, an overloaded database, insufficient workers, or high server load. We find what’s slow instead of just raising the timeout.
File permissions, web server or .htaccess rules, firewall, Cloudflare, or a security plugin rejecting the request.
Which service actually stopped
All sites on it may go down at once. We validate config syntax before restarting.
Invalid config, broken vhost, module problems, or a failed update — one site or the whole server.
Blank pages, 502/504/500s, or extreme slowness. We check pools, sockets and worker limits.
“Error establishing a database connection” — MySQL/MariaDB service status, crash logs, disk, memory.
When the server is fine but visitors can’t reach it
Wrong A/AAAA/CNAME records, stale propagation, DNSSEC issues. Changed carefully, especially when the domain also handles email.
Expired certs, failed Let’s Encrypt renewal, wrong chain, blocked port 80/443, or Cloudflare SSL mode mismatched with the origin.
Wrong DNS records, proxy/SSL mode, WAF or rate-limit rules, or an unreachable origin. We narrow it to before Cloudflare, inside Cloudflare, or on the origin.
Investigated as a full stack, not just the app
Failed plugin update, theme error, PHP incompatibility, database problem, corrupted files, malware, broken cache, WP-Cron or insufficient memory — because we work with both WordPress and the Linux infrastructure underneath, we check both sides.
WordPress, plugin, theme, PHP version, Linux packages, NGINX/Apache, database or SSL changes right before an outage matter — even if they seem unrelated, mention them.
Deprecated code, missing extensions, incompatible plugins/themes, or a changed PHP-FPM pool configuration. We check application compatibility and PHP-FPM config together.
500 errors, DB failure, session errors, failed WP updates, cache and logging errors. We find what filled the disk — logs, backups, uploads, cache, inode exhaustion — before deleting anything.
CPU saturation, memory pressure, swap, disk I/O, PHP-FPM/MySQL overload, bots or malicious requests. We identify which process is the actual bottleneck.
One site down, or all of them?
Usually infrastructure-level: NGINX, Apache, PHP-FPM, MySQL, DNS, firewall, server load, disk full or a network outage.
Likely specific to that domain — vhost, SSL cert, PHP version, WordPress, its database, DNS, or file permissions.
Telling us which case you’re in narrows the investigation immediately.
Malware, modified PHP, malicious .htaccess, deleted files, database changes or provider suspension can all take a site offline. For WordPress: malware investigation, infected file cleanup, integrity checks, admin account review, and security recommendations — a serious compromise can need more than removing the obvious malicious code.
The web server can be running fine while a provider firewall, UFW, iptables, nftables, CSF or Cloudflare rule blocks port 80/443 or a specific source. If admin access is also lost, provider console or rescue access may be needed.
HestiaCP, DirectAdmin, cPanel & WHM, VestaCP — broken web templates, a failed service update, PHP/SSL/DNS config, or a database service failure. We check the panel and the services underneath it.
Sometimes Linux is fine but the provider isn’t — networking, routing, virtualisation, hardware, storage or a datacentre issue. We help separate website vs server vs provider problems, and gather diagnostics for the support ticket if needed.
When the whole server is unreachable
Rescue System, KVM console, Recovery Console, VNC console, serial console or a rescue ISO — depending on the provider — get us in when SSH no longer works.
Restoring a compromised website without fixing the vulnerability simply recreates the same problem.
Faster diagnosis starts with the right details
Not sure what matters? Just describe what you see.
A fully unavailable production site normally qualifies as Emergency Support
Emergency Support, for critical website and server incidents.
Out-of-Hours Emergency Support — evenings, weekends, holidays.
Both subject to administrator availability — no guaranteed 24/7 coverage unless separately agreed. Full pricing →
Include the domain and any visible error
Written technical details are usually the fastest first step for a website outage.
help@direktsupport.euPhone support is primarily for customers with an active monthly management plan.
More than 22 years of practical experience with websites, WordPress, Linux servers, hosting infrastructure, databases, DNS, email and production environments. Our objective is not simply to reload the page until it works again.
We identify the failing layer, restore service where possible, and determine what caused the outage.