heleuzapatrocinio
Forum Replies Created
-
As a complement to the information already provided, I would like to detail the actions that my hosting provider has already performed on the server in an attempt to resolve the issue:
- Apache Restart: The Apache server was restarted to ensure any changes were applied.
- ModSecurity Rule Release: ModSecurity rules that could be blocking Elementor requests were disabled/whitelisted.
- Varnish Cache Verification: My hosting provider confirmed that there is no active Varnish cache on the server for my domain, ruling out the possibility of server-side caching storing an older version of the site or its headers.
- Infrastructure Checks: DNS, IP, SSL certificate, and site access were all verified and confirmed to be operating normally.
Final Consideration:
My hosting provider states that, from their server infrastructure perspective, there are no active blocks or errors that would justify the
Blocked a frame...error in Elementor..
Hi @vipul78
Thank you for your detailed response and for pointing out the redirect issue. I have now completed all the steps you recommended, including the server-level 301 redirect, and I would like to confirm the results.1. Server-Level 301 Redirect (Applied via .htaccess)
I added the following rewrite rules to my
.htaccessfile to force all URL variants to the single canonical URL:apache<IfModule mod_rewrite.c> RewriteEngine On # 1. Redirecionar HTTP para HTTPS RewriteCond %{HTTPS} off RewriteRule ^(.*)$ https://%{HTTP_HOST}/$1 [R=301,L] # 2. Redirecionar WWW para non-WWW RewriteCond %{HTTP_HOST} ^www\.(.+)$ [NC] RewriteRule ^(.*)$ https://%1/$1 [R=301,L] </IfModule>
Test Results:
http://heleuzaengads.com.br✅ redirects tohttps://heleuzaengads.com.brhttps://www.heleuzaengads.com.br✅ redirects tohttps://heleuzaengads.com.br
2. HTTP Headers Plugin
I installed and activated the “HTTP Headers” plugin as suggested and configured the following security headers:
- X-Frame-Options: Set to
SAMEORIGIN - Content-Security-Policy: Set
frame-ancestors 'self'
3. Additional Steps Taken (to eliminate other variables)
- Cleared all caches (WordPress, browser, and requested server-side cache clearance from my hosting provider).
- Tested in an incognito/private window with all browser extensions disabled.
- Removed any temporary custom code from
.htaccess,wp-config.php, andfunctions.php.
🔴 The Result
Despite completing all of these steps, including the .htaccess redirect, the error persists. The browser console still shows:
Uncaught SecurityError: Failed to read a named property 'elementorFrontend' from 'Window': Blocked a frame with origin "https://heleuzaengads.com.br" from accessing a cross-origin frame.“The redirects are working correctly (I tested and confirmed them). However, the
Blocked a frame...error persists, which suggests that a different server-level configuration (such as a security header or cache) is still blocking the iframe.”- Can you confirm if there are any additional server-level security headers or Apache directives that could be causing this block?
- Is there any other diagnostic step you recommend?
- This reply was modified 15 hours, 14 minutes ago by heleuzapatrocinio.
Dear vipul78,
Thank you for your response.
I have carefully followed all the steps you requested and I would like to confirm the results below:1. Screenshot of the console error
✅ Attached.
The error message remains the same:Uncaught SecurityError: Failed to read a named property 'elementorFrontend' from 'Window': Blocked a frame with origin "https://heleuzaengads.com.br" from accessing a cross-origin frame.2. Screenshot of WordPress Dashboard > Settings > General
✅ Attached.
Both URLs are correctly set to:https://heleuzaengads.com.br(WordPress Address)https://heleuzaengads.com.br(Site Address)
3. Disable Cloudflare Rocket Loader
✅ Not applicable.
I do not use Cloudflare on this website.4. Remove any custom code used temporarily✅ Completed.
I removed all custom code I had added to:.htaccesswp-config.phpfunctions.php
After removing the custom code, I cleared all caches (WordPress, server, and browser) and tested again.
Result: The error persists.5. Ensure no browser extensions are active while testing
✅ Completed.
I tested the editor in:- Incognito/private mode
- Different browsers (Chrome, Firefox, Edge)
- All extensions disabled
Result: The error persists in all scenarios.🔴 Summary
Despite completing all the steps you suggested, the
Blocked a frame...error still occurs. The issue does not appear to be caused by:- Custom code
- Browser extensions
- Cache
- Theme or plugin conflicts
- Cloudflare (not used)
At this point, I believe the issue may be related to a server-side configuration that is blocking the iframe required by the Elementor editor.
I kindly ask for your further guidance on what to try next.
Thank you for your time and support.
Sincerely,
screenshots – https://we.tl/t-NGOm8yT08FQ1RpjO
- This reply was modified 1 day, 6 hours ago by heleuzapatrocinio.