Describe the issue
Send the URL, visible error and the last change made.
WordPress without unnecessary risk
I restore WordPress websites after failed updates, plugin conflicts, 500 errors and broken forms. I identify the cause and secure a backup before agreeing the fix.
I inspect logs, PHP, the theme and plugins to fix the cause rather than hide the symptom.
I restore access and resolve version, theme or plugin conflicts safely.
I check submission, SMTP, validation and notification delivery.
I fix login failures, permissions, redirect loops and critical errors.
I locate heavy requests, plugins and caching faults without removing required features.
I correct URLs, certificates, mixed content and post-migration errors.
This is how WordPress reports that a PHP error has stopped the site. The message itself does not say what broke, so I start the repair with the logs, not with guesses.
The error usually appears right after an update, a new plugin or a change in the hosting settings. The site stops opening for visitors, and access to wp-admin is often lost as well.
Each of them has several possible causes. Below is where I start checking.
Error establishing a database connectionWhat it usually means: WordPress cannot reach the database: wrong details in wp-config.php, the database server is down or tables are damaged.
What I check: Connection details, the database server status at the host and the tables.
Allowed memory size … exhaustedWhat it usually means: A script exceeded the PHP memory limit, usually because of a heavy plugin or an import.
What I check: Which plugin uses the memory and whether the limit suits the site.
Briefly unavailable for scheduled maintenanceWhat it usually means: An update was interrupted and the site is stuck in maintenance mode.
What I check: The .maintenance file and whether the updated files are complete.
ERR_TOO_MANY_REDIRECTSWhat it usually means: A redirect loop, often after switching to HTTPS or changing the site address.
What I check: The site address in the database, server rules, CDN and redirect plugins.
502 / 503 from the serverWhat it usually means: The server cannot keep up or PHP stopped responding, sometimes because of bot traffic.
What I check: Server logs, hosting limits and the heaviest requests.
Send the URL, visible error and the last change made.
I check access, logs and backups, then confirm the scope.
I make the agreed changes with a backup and rollback plan.
I test pages, forms, admin access and document the result.
Prices apply to a typical company website on WordPress. The same error 500 can mean a simple conflict or several hours of work in the code, so I confirm the exact price and timing after the diagnosis, before the work starts.
from 150 PLN
A setting, a configuration issue or one plugin that blocks the site.
Ask for a quotefrom 250 PLN
Diagnosis in the logs, restoring the site and removing the cause of the conflict.
Ask for a quotefrom 200 PLN
Message delivery, SMTP, wp-admin login, permissions and the login loop.
Ask for a quoteMany pages and plugins, WooCommerce with integrations, custom code or a VPS server. Diagnosis first, then the price and the work plan.
individual quote
Ask for a quoteFile and database cleanup plus closing the entry point. Pricing is on the service page.
separate service
Service detailsThe scope depends on the number of pages, plugins, integrations and payments.
quote after diagnosis
Ask for a quoteThe more details you send at once, the faster I find the cause and name the price. Passwords are best shared through a temporary account that you delete after the repair.
The exact price depends on the cause. For a typical company website a simple fix starts from 150 PLN, and an error 500 or a failed update from 250 PLN. Large sites and complex stores are quoted individually. I confirm scope and cost after a short diagnosis, before the repair starts.
Usually the website URL, WordPress admin and hosting access. Temporary passwords are recommended.
Yes, including cart, checkout and extension conflicts. Payment flows are tested without real charges.
An infected site needs a security cleanup that finds the entry point and backdoors, not only the visible malicious code.
It is a general WordPress message about a PHP error that stopped the site. The logs show the cause: most often a plugin or theme conflict, the PHP version or the memory limit. The administrator also receives an email with a link to recovery mode.
Yes. A login loop or lost access to the admin panel is usually caused by a plugin, the site address in the database or permissions. With hosting access I fix it without logging in to WordPress.
I give the timing together with the price after the diagnosis. A simple fix takes less time than a failure that requires analysing files, the database and the server.
Yes, but make a backup first and check that the plugins and the theme support the new version. After the change, test the forms and the admin panel. If the site stops working, switch back to the previous PHP version in the hosting panel.
Website request
The form sends your message directly to my Telegram. A website URL and a short description are usually enough.