Muhammad

Hi @camna,

Thank you for sharing your findings and the code modification.

We appreciate the detailed explanation regarding the 301 redirect behavior and how changing it to a 302 redirect resolved the issue in your environment.

I’ve forwarded this information to our development team for review. They will investigate whether the current redirect behavior could cause caching or access issues in certain scenarios and whether a change should be considered in a future update.

Thank you for taking the time to report this and provide the code snippet.

Hi @fotograf561,

Thank you for the clarification.

Since your hosting provider does not allow increasing the Apache timeout on the shared hosting environment, the limitation would likely still affect PDA Free downloads on slower connections.

PDA Gold may help in this case because it includes an alternative download handling method designed for large file transfers and timeout prevention. However, as the restriction is enforced by the hosting environment itself, we cannot fully guarantee the behavior under all server limitations.

If large file downloads are an important requirement for your site, a VPS/dedicated environment or external storage solution would generally provide more reliable results for long-running downloads.

Hi @drjsa ,

Thanks for confirming this thoroughly.

Since caching has already been excluded and the issue still persists even with all plugins disabled, this confirms it is not related to StackCache or any plugin conflict.

At this point, the delay appears to be coming from the way PPWP Lite processes multiple passwords, as it checks them sequentially until it finds a match.

As a temporary fix, you can try reducing the number of passwords or reordering the list so that the most frequently used passwords are placed at the top for faster access.

However, for a permanent and reliable solution with consistent performance, switching to the Pro version is the only option we can suggest.

Let us know how you’d like to proceed.

Hi @drjsa ,

Thanks for reaching out.

PPWP Free stores all passwords of a single post in the WordPress default table postmeta. So it might take time to check passwords and unlock content if you have number of passwords.

If you want to avoid loading delays, you should consider switching to the Pro version. The Pro version stores all passwords in a separate table in the WordPress database. By doing that, we can assign each password a unique ID, which speeds up the password checking process significantly.

Please let us know if you’d like any help with the upgrade or further assistance.

Hi @liwebguy ,

Thank you so much for your kind words! We truly appreciate your feedback.

It’s great to hear that you found our support timely and helpful, even on the free version. Your support means a lot to us and motivates our team to keep improving.

If you ever need any assistance, feel free to reach out , we’re always here to help.

Hi @equilator ,

Thanks for your message.

Please drop us an email at support(at)wpfolio.com for faster and more customized responses from our team.

Hi @vfavrat ,

If the password label is not available in the settings, you can try adjusting it directly in the plugin files.

Step 1:
Navigate to Plugins > Plugin File Editor in your WordPress dashboard and select Password Protect WordPress (PPWP Lite).

Then go to:
/public/views/
and open the file sitewide-password-form.php (or password-form.php if applicable).

Step 2:
Look for the text “Password” and replace it with your preferred translation.

Step 3:
Click Update File to save your changes.

Please give this a try, and if it doesn’t work, let us know. I hope this resolves your issue.

hi @jscooper,

Thank you for reaching out!

Yes, the NGINX rules should be placed inside the server block and outside any location block.

Since you mentioned the file contains confidential information, could you share another sample protected file URL (for testing) so we can check whether the protection is working correctly? That would help us better understand what might be happening.

Also, please confirm whether the file is already marked as protected in the Media Library.