Requesting Assistance with WordPress Login Issue Post-Deployment on Azure

Rod Price 20 Reputation points
2025-05-08T14:48:00.1266667+00:00

I’m following regarding my WordPress deployment on Azure App Service. I’ve successfully imported a .wpress backup using the All-in-One WP Migration Unlimited Extension, but I’m now encountering a persistent issue: the login page (/wp-admin) spins indefinitely without error, and I can’t access the dashboard.

Here’s a quick summary of what I’ve tried:

App is hosted on App Service (Linux, S1)

Database is MySQL Flexible Server (B1ms) with VNet-only access

Manually set WP_HOME and WP_SITEURL in wp-config.php

Scaled up from B1 to S1 and restarted the app

Logs show PHP-FPM is starting, but there are memory warnings and permission errors

Suspect plugin conflict or VNet-based communication timeout is preventing login completion

I’d appreciate any help confirming whether this is a known issue with plugin execution under VNet restrictions or if I should consider rebuilding with public-access MySQL. I’d also like guidance on the safest way to disable plugin loading temporarily if needed.

Site: https://ithosnewwp-btbba4bdffgbd8dh.westus-01.azurewebsites.net Resource Group: ithos-prod-rg

Azure App Service
Azure App Service
Azure App Service is a service used to create and deploy scalable, mission-critical web apps.
8,965 questions
{count} votes

2 answers

Sort by: Most helpful
  1. Siva Nair 2,420 Reputation points Microsoft External Staff Moderator
    2025-05-08T17:57:45.3966667+00:00

    Hi Rod Price,

    Based on above analysis, the issue is likely due to: Plugin conflicts post-restore (common with .wpress imports) / Restricted MySQL connectivity via VNet-only access/ Memory or permission errors triggered under App Service Linux

    Lets do some troubleshooting:

    1. Safely Disable All Plugins- This ensures any faulty plugin doesn’t block the login process.

    Via Kudu Console or FTP:

    mv /home/site/wwwroot/wp-content/plugins /home/site/wwwroot/wp-content/plugins_disabled
    

    Alternate (via MySQL):

    UPDATE wp_options SET option_value = 'a:0:{}' WHERE option_name = 'active_plugins';
    
    1. Verify MySQL Flexible Server Connectivity- Ensure the App Service is correctly integrated with the same VNet/subnet as the MySQL server.

    Check from Kudu Console:

    nc -zv <mysql-name>.mysql.database.azure.com 3306
    

    If this fails, update NSG rules or expose MySQL to App Service outbound IPs for testing.

    1. Fix File Permissions and Increase Memory

    File permission issues often occur post-import on Linux.

    chown -R www-data:www-data /home/site/wwwroot
    chmod -R 755 /home/site/wwwroot
    

    In wp-config.php, increase memory and enable debug logging:

    define('WP_MEMORY_LIMIT', '256M');
    define('WP_DEBUG', true);
    define('WP_DEBUG_LOG', true);
    

    Retain your current VNet + Private MySQL architecture, as it's more secure. Only consider switching to public access temporarily for debugging, if absolutely necessary.

    If you have any further assistant, do let me know.

    0 comments No comments

  2. Sampath 3,750 Reputation points Microsoft External Staff Moderator
    2025-05-14T11:46:58.0633333+00:00

    Hello @Rod Price,

    Here are some troubleshooting steps that might help:

    Disable All Plugins Temporarily – This can help rule out plugin conflicts:

    • Via Kudu Console or FTP:
      
           mv /home/site/wwwroot/wp-content/plugins /home/site/wwwroot/wp-content/plugins_disabled
      
      
    • Via MySQL:
      
           UPDATE wp_options SET option_value = 'a:0:{}' WHERE option_name = 'active_plugins';
      
      

    Verify MySQL Connectivity – Ensure your App Service is correctly integrated with the same VNet/subnet as the MySQL server:

    
       nc -zv <mysql-name>.mysql.database.azure.com 3306
    
    

    If this fails, update NSG rules or expose MySQL to App Service outbound IPs for testing.

    Fix File Permissions & Increase Memory – File permission issues often occur post-import on Linux:

    
       chown -R www-data:www-data /home/site/wwwroot
    
       chmod -R 755 /home/site/wwwroot
    
    

    In wp-config.php, increase memory and enable debug logging:

    
       define('WP_MEMORY_LIMIT', '256M');
    
       define('WP_DEBUG', true);
    
       define('WP_DEBUG_LOG', true);
    
    

    Your current VNet + Private MySQL setup is more secure, so switching to public access should only be a last resort for debugging. If you continue to face issues, checking Azure logs for PHP-FPM errors and reviewing plugin execution under VNet restrictions might provide further insights.

    Refer this link for more details

    Not able to log into wordpress website.... self hosting on Azure - Stack Overflow

    WordPress Troubleshooting Techniques on Azure Websites | Microsoft Azure Blog

    How to fix wordpress issue in Azure - Microsoft Q&A

    If you have any further assistant, do let me know.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.