App/Something no longer working

Question

App/Something no longer working

MHS 0

I'm new. I'm not a programmer but have decades of "Lite" experience with CMS's like Wordpress, Joomla, as well as basic knowledge of php/css/html/ blah blah blah.

I'm looking run a community website, and was hopeful to be able to use our Sharepoint site as a webpage. Found out that was removed some time ago.

So, now, I need a webhost to build a VERY Basic page for a community of about 200 members. I would need a database for Login, and I would need a page for displaying PDF files for downloading (HOA Documents, Forms, ect.

Thought I would give Microsoft Azure a go, but what a complete information overload and learning curve for some guy in his 50's that just want to build a website. Got a Wordpress Web App installed (although there is like 20 to choose from) and was able to get WP Installed and running. Next challenge was to refresh my WP Knowledge to build it. Everything was supposedly going smooth until I installed a few Plugins, and then ....Http Error 500.

Did I do something wrong? Was it the Server? Instance? I don't know. Don't really care as I'm learning that the support from MS is simply a Joke, won't let me create a ticket.. Meanwhile, my 30 day trial is ticking away and I'm wasting my time with this MSBS.

So, OK MS, what went wrong? I've run the AI tool which is fancy and all but its information overload. The Logs are not really telling this newb anything. I'm sure its all good when your dealing with a IT Pro that knows there way around, but that's not me.

The question really is, do you care to fix it? I'm not asking for a Bachelors Degree Education on how to DIY, but I don't want to make the same mistake moving forward, and all the AI and Logs will not prevent that.

Golla Venkata Pavani 2,005 Reputation points Microsoft External Staff Moderator

2026-02-26T19:25:37.6366667+00:00
Hi @MHS

Thank you for reaching us regarding the issue.

HTTP 500 errors on WordPress running in Azure App Service are almost always caused by application‑level issues in WordPress itself, not by the Azure server, instance, or platform.

In your scenario, where the site works initially and then starts returning HTTP 500 immediately after installing plugins, the most common cause is a faulty, incompatible, or conflicting WordPress plugin that triggers a PHP fatal error during page load.

Azure App Service continues to run correctly, but because WordPress crashes at runtime, Azure can only return a generic “HTTP 500” response.

Why the logs didn’t seem helpful:

By default, Azure App Service logs focus on the platform and runtime, not WordPress internals. Microsoft documentation explains that WordPress‑specific errors are not visible unless WordPress debugging is explicitly enabled. Without that, fatal PHP errors caused by plugins may not appear clearly, which is why the logs felt opaque.

Quick Recovery steps:

Disable All Plugins via the Database (safest when you can't reach /wp-admin):

Go to the Azure Portal > Your App Service > Settings > Configuration or directly to your linked database (usually Azure Database for MySQL).

Use the Query Editor (or phpMyAdmin if enabled via extensions) to run these SQL commands (replace wp_ with your actual table prefix from wp-config.php if different):
UPDATE wp_options SET option_value = 'a:0:{}' WHERE option_name = 'active_plugins';

This deactivates every plugin instantly.

Refresh your site URL. It should now load (likely showing errors or warnings, but no 500).

Log in to /wp-admin, then reactivate plugins one at a time, testing the site after each to identify the culprit. Delete or replace the bad one.

Check Logs for Clues:

In the Azure Portal, go to your App Service > Monitoring > Log stream (real-time) or App Service logs / Application logs.

Look for PHP fatal errors mentioning a specific plugin file or line number—these often point directly to the issue.

Enable WordPress debug mode temporarily by editing wp-config.php (via Kudu or FTP):
define('WP_DEBUG', true); define('WP_DEBUG_LOG', true); define('WP_DEBUG_DISPLAY', false);
Errors will then appear in /wp-content/debug.log (download via Kudu: Advanced Tools > Go > site/wwwroot).

Other Common Checks:

Confirm your PHP version (under Configuration > General settings) matches what your plugins expect, most modern ones work best on PHP 8.1 or 8.2.

If the site still 500s after disabling plugins, it could be memory limits (rare on trial tiers but possible). Scale up temporarily to a higher plan (e.g., S1 or B1) via Scale up to test.

Restart the App Service (Overview blade > Restart) after changes.

Microsoft also provides a helper tool, the WordPress Buddy+ Azure Site Extension, specifically to disable plugins and recover access when the WordPress admin dashboard is unreachable.

Reference:
https://learn.microsoft.com/en-us/azure/app-service/wordpress-faq
https://learn.microsoft.com/en-us/troubleshoot/azure/app-service/web-apps-open-source-technologies-faqs
https://learn.microsoft.com/en-us/azure/app-service/troubleshoot-diagnostic-logs
https://learn.microsoft.com/en-us/azure/app-service/configure-language-php?pivots=platform-linux

Kindly let us know if the above comment helps or you need further assistance on this issue.

Please "upvote" if the information helped you. This will help us and others in the community as well.
Golla Venkata Pavani 2,005 Reputation points Microsoft External Staff Moderator

2026-02-27T19:29:29.85+00:00

Hi @MHS

I'm just reaching out to see if your issue has been resolved or if you've had a chance to review my previous comment?

2 answers

Your answer

Golla Venkata Pavani 2,005 Reputation points Microsoft External Staff Moderator

2026-02-27T19:29:29.85+00:00

Hi @MHS

I'm just reaching out to see if your issue has been resolved or if you've had a chance to review my previous comment?

Answer 1

MHS 0

I don't have a "Query" option as mentioned above, and as shown on the resource page here: https://learn.microsoft.com/en-us/azure/azure-sql/database/connect-query-portal?view=azuresql&wt.mc_id=fulltextsearch_inproduct_azure-portal-global-search

Answer 2

HTTP 500 errors on a new WordPress site in Azure App Service are almost always caused by application-level problems, not by the Azure platform itself. In the scenario described (site worked, then HTTP 500 after installing a few plugins), the most likely cause is a faulty or incompatible WordPress plugin.

For WordPress on Azure App Service, the recommended way to recover from this situation without deep debugging is to disable the problematic plugins and, if needed, reset the WordPress sign-in password directly in the site’s environment. Azure provides a helper extension for this:

Use the WordPress Buddy+ Azure Site Extension to disable plugins:
- WordPress Buddy+ can disable WordPress plugins when locked out of the admin dashboard due to a bad plugin.
- After disabling the plugins, the site should stop returning HTTP 500 if the plugin was the root cause.
If sign-in to WordPress is also broken, use WordPress Buddy+ to change the WordPress sign-in password:
- This lets access the WordPress admin area again once the site is responding.
If the site was recently migrated or the URL changed, verify that WordPress isn’t redirecting incorrectly (which can sometimes look like a failure):
- WordPress Buddy+ can also update the site URL directly in the MySQL database.
For ongoing troubleshooting of WordPress on App Service:
- Enable WordPress debug logs as described in the WordPress on App Service FAQ to see which plugin or theme is causing errors.
- Review the “Typical issues and resolutions” list for common WordPress-on-Azure problems (CORS, intl extension, existing installation conflicts, etc.).

If the app is still returning HTTP 500 after disabling plugins, treat it as a general application startup/response error:

For ASP.NET Core or other app types on App Service, HTTP 500 often indicates:
- An exception during startup or while generating the response.
- Misconfiguration (for example, targeting a framework version that isn’t installed, or missing permissions to Azure Key Vault).
- In these cases, the guidance is to:
  - Run the app from a command prompt on the server or
  - Enable the ASP.NET Core Module stdout log and check the Application Event Log to see the exact error.
For HTTP 502/503 (if encountered instead of 500), the common causes are:
- Requests taking too long.
- High memory or CPU usage.
- Exceptions preventing the app from responding.
- The mitigation options include:
  - Monitoring metrics (CPU, memory, requests) in the App Service “Metrics” blade.
  - Scaling the app up or out if resource limits are being hit.
  - Using auto-healing to recycle the worker process when requests hang or memory thresholds are exceeded.
  - Restarting the app from the Azure portal.

For the specific goal (simple community site with logins and document downloads) and skill level described, WordPress on App Service is a valid choice, but stability depends heavily on plugin quality. To avoid repeating the issue:

Install plugins one at a time and test after each install.
Prefer well-known, actively maintained plugins with good reviews.
Keep a note of which plugin was installed just before any failure; if HTTP 500 appears again, disable that plugin via WordPress Buddy+.
Use the WordPress troubleshooting guides in the WordPress on App Service FAQ when encountering common issues.

References:

Share via

App/Something no longer working

2 answers

Your answer