Muhammad

Hi @csebe,

No worries at all, we’re just glad you were able to pinpoint the issue!

Thanks for checking the console and confirming it’s related to API permissions. Some security plugins can indeed restrict REST API access for certain roles, which would explain the “rest_forbidden” response for Editors.

If you need further, feel free to let us know — happy to assist further!

Hi @agouser35,

Thanks for getting back to us, and I truly apologize for the confusion earlier.

It looks like there was a mix-up between the rewrite rules for different server types. Just to clarify:

✅ For Apache servers (like yours), our plugin usually inserts the required .htaccess rewrite rules automatically.

❗ For NGINX and IIS servers, those rules need to be implemented manually in the server configuration, as .htaccess files are not supported.

We’ll follow up with you to help troubleshoot further and make sure your file protection is working properly.

For a faster and more detailed response, could you please send us a message through our contact form? This will allow us to look into your setup more closely and provide better assistance.

Thanks again for your patience — we’re here to help!

HI @bmamedia,

Thanks for the update and for confirming that you’re using PPWP Lite.

It’s good to know you’ve already excluded the page from caching and aren’t using any security plugins. Since the issue seems intermittent and results in a 502 error, it could still be related to server resources or a conflict with another plugin or theme.

Could you try temporarily switching to a default theme (like Twenty Twenty-Four) and deactivating other plugins (except PPWP Lite) to see if the issue still occurs? This can help rule out any compatibility conflicts.

Also, if you’re using any firewall or reverse proxy service (like Cloudflare), it might be worth checking their logs as well.

Let us know how it goes, we’ll do our best to assist further!

Hi @mbusik,

Thank you for the update! No worries at all — enjoy your holiday, and feel free to send the logs and screenshots whenever you’re back and have the time.

We’ll be here to assist you further then.

Hi @incredimike,

Thanks for your suggestion and for pointing that out! I can see how having the ability to customize the cookie name could be helpful for compatibility with certain platforms and caching setups.

I’ve forwarded your request to our development team for review. If they find it feasible, we may include a filter like apply_filters('ppwp_cookie_name', ...) in a future update.

We really appreciate your input, please feel free to share any other ideas or feedback!

@moderator,

Thank you very much for your detailed explanation — I truly appreciate the guidance and completely understand the importance of following forum policies.

I’d like to sincerely apologize for any misunderstanding. Just to clarify, we have not requested or accessed the user’s admin area or server in any way.

The user voluntarily shared a test page so we could better understand and verify the issue they described. They also shared their email address on their own, which we only used to follow up about the sample password they wanted us to test — no admin login credentials were ever asked for or involved.

That said, I fully understand how my wording may have seemed unclear, and I’m grateful for the reminder. I’ll be extra mindful moving forward to stay within the forum’s public support framework and avoid even the appearance of requesting access.

Thanks again for your work keeping this space safe and collaborative for everyone.

Hi @wpress2010,

That sounds like a solid approach for now. As mentioned earlier, we’ve looped in our development team to see if there’s a more seamless workaround or fix we can implement in a future update.

In the meantime, feel free to toggle the protection as needed while editing — and if anything else comes up, don’t hesitate to reach out.