在IIS负载均衡环境下共享WordPress媒体文件的技术求助

Hey there, let's tackle this file upload sync issue with your load-balanced WordPress sites on IIS 2012 R2. I've worked through similar setups before, so let's break down why your virtual directory approach might have fallen short and fix this properly.

First, let's rule out the most likely culprits:

• Permission gaps: The shared folder probably doesn't have the right NTFS or share permissions for your IIS app pool identity.
• WordPress config mismatch: Even with a virtual directory, WordPress might still be trying to write to the local server's uploads folder if your wp-config.php isn't updated.
• Incorrect virtual directory mapping: If you didn't link the alias correctly to the UNC path or set up "Connect As" properly, IIS can't access the share.

1. Lock Down Shared Folder Permissions #

First, make sure your shared folder (on a dedicated file server or one of your IIS nodes) has the right access:

• Share permissions: Grant Read/Write access to your IIS app pool identity (usually IIS AppPool\YourSiteAppPoolName) or the domain account running your app pool.
• NTFS permissions: Assign the same identity these permissions: Modify, Read & Execute, List Folder Contents, Read, Write. Double-check that permissions are inherited correctly down to subfolders.

2. Force WordPress to Use the Shared Path #

Virtual directories alone won't override WordPress's default local upload behavior—you need to update wp-config.php on both servers:

// Replace with your UNC path (note the double escaped backslashes)
define('UPLOADS', '\\\\your-file-server\\wp-shared-uploads\\site1');
// Keep your site URLs consistent to avoid broken media links
define('WP_HOME', 'https://your-site-domain.com');
define('WP_SITEURL', 'https://your-site-domain.com');

• Use separate subfolders (site1/site2) if you're hosting two distinct WordPress sites to keep their media files separated.
• Never use mapped network drives (like Z:) here—UNC paths are the only reliable way for IIS app pools to access network shares.

3. Reconfigure the IIS Virtual Directory (If Needed) #

If your initial virtual directory setup was off, redo it this way:

• Open IIS Manager, right-click your WordPress site > Add Virtual Directory.
• Set the alias to wp-content/uploads (matches WordPress's default upload folder structure).
• For the physical path, paste the UNC path to your shared subfolder (e.g., \\your-file-server\\wp-shared-uploads\\site1).
• Click Connect As > select Specific user, then enter the account that has permissions to the share (the same one you set up in step 1).
• Run the Test Settings to confirm IIS can connect to the share without errors.

4. Sync Existing Uploads #

Don't forget to copy all existing files from both servers' local wp-content/uploads folders to the corresponding shared subfolders. This ensures old media files are accessible from any server in the load balancer pool.

5. Test the Setup #

• Upload a test image through one server's WordPress media manager.
• Switch to the other server (you can tweak your local hosts file to point your domain to the second server's IP temporarily) and check if the image appears in the media library.
• Verify the test image exists in the shared folder—this confirms the write operation is hitting the shared storage, not the local server.

• If you're using ARR for load balancing, you don't need sticky sessions for this setup, but enabling it won't break anything.
• Make sure both servers have identical PHP configs (especially upload_max_filesize, post_max_size, and memory_limit) to prevent inconsistent upload failures.
• Consider setting up file auditing on the shared folder to troubleshoot any permission-related upload errors later.

内容的提问来源于stack exchange，提问作者user1602126