Okay so I have elementor pro and an icon widget as the hamburger on tablet and mobile. The icon/ hamburger calls a pop up which acts as an off canvas menu.

The off canvas menu/pop up when called always comes from the top down. Even when entrance set to slide from the right… I’ve checked and all animations are off , so it doesn’t make sense to me. Any help is appreciated with regards to stopping it from flying in from the top down. Cheers

https://preview.redd.it/rhm2wf3ggx4h1.png?width=1196&format=png&auto=webp&s=f383b13cd04813895b7178f8d1453f7dfba5bc69

Hi There, I am getting massive memory usage and cpu spike on hostinger with wordpress, using divi theme, litespeed with cloudflare... Can get to the bottom of it... any ideas? Happy to give my link in DM if anyone can assist get to the bottom of this at it is killing my resource limits.

Happy to offer an exchange link insertion backlinks using appropriate anchor text in my SEO company website based in uk. Ideal for other agencies and/or local business sites. Dm me if your interested and we can exchange domain details

Best regards,

Is there any way to automate blog post creation on Squarespace via API?

I run an SEO agency and we automate blog publishing for clients on WordPress and Wix using n8n. The workflow pulls from a Google Sheet, reads the article from Google Docs, handles images, SEO metadata, tags, categories, and publishes automatically.

We have a client on Squarespace now and I have hit a wall. The Squarespace API only seems to cover commerce (orders, products, inventory). There is no blog post endpoint that I can find.

So far the workarounds I have come across are:

- The XML import via Settings > Advanced > Import/Export, but that is manual and posts land in Not Linked

- The SQSPThemes CSV to XML converter tool for batch imports

- Browser automation with Playwright or Puppeteer, which feels fragile and possibly against the ToS

- Hosting the blog on WordPress via a subdomain and keeping the main site on Squarespace

Has anyone found a better way? Is there a hidden API, a plugin, or a third-party tool that can create and publish blog posts programmatically on Squarespace?

Any help appreciated. Genuinely surprised this is not a thing yet when Wix and WordPress have had it for years.

TL;DR: Hostinger is returning 429 on all POST requests to the WordPress REST API from n8n cloud. GET requests work fine. Affects all Hostinger sites across multiple separate accounts. Same workflows work perfectly on non-Hostinger hosts and worked fine until yesterday afternoon. Tried everything I can think of including Cloudflare proxy. Looking for help or anyone who has solved this.

The Setup

I run automated blog publishing workflows on n8n cloud for multiple WordPress sites. The workflows use the WordPress REST API to create posts, tags, and set SEO metadata. Each run makes roughly 10-15 API calls over about 60 seconds: a few GETs to fetch media, categories, tags, and pages, then POSTs to create tags and publish a draft post.

I have three sites on Hostinger (different accounts, different plans) and one site on a different host. The workflows had been running fine for weeks with no issues.

What Happened

During a debugging session for an unrelated issue, I ran one workflow roughly 10-12 times in about 4 hours. This generated approximately 120-175 API requests from n8n cloud's outbound IP to Hostinger.

After that burst, every subsequent API call returned 429 Too Many Requests with an empty body. The error message: "The service is receiving too many requests from you."

I then tested the other two Hostinger sites (completely separate accounts). All three failed with 429. The non-Hostinger sites continued working perfectly with identical workflow code.

What I Have Investigated and Ruled Out

Wordfence - Rate limiting set to Unlimited on all rules. n8n IP added to the allowlist that bypasses all rules. Not the cause.

Must-use plugins - Only hostinger-auto-updates.php and hostinger-preview-domain.php. Neither has rate limiting.

ModSecurity - Disabled completely via .htaccess. Still 429.

Custom User-Agent - Changed from default axios to a custom header. Still 429.

.htaccess rules - No custom rate limiting present. Standard WordPress and LiteSpeed config only.

Hostinger IP Manager - Added n8n IP to the Allow list. No difference.

Time-based cooldown - Waited 90 minutes with zero requests, still 429. Waited 8+ hours with zero requests, still 429.

Application password - Generated a fresh WordPress application password. Still 429.

Disabling tag creation - Disabled the tag creation node entirely so only one POST request fires. Still 429.

What Hostinger Support Said

Spoke with four different agents over about 12 hours:

• The rate limit is global per IP at the CDN level, not per account or per site
• Thresholds are not disclosed (internal security config)
• Normal usage of 15 requests per site twice a week is "very light and should not come close to triggering any limits"
• Cannot be adjusted or whitelisted per account
• GET and POST treated the same (but in practice only POST fails)
• No customer dashboard to monitor usage
• Stated cooldown is 30-60 minutes but mine persisted 8+ hours
• Eventually escalated to their technical team who are still investigating

Cloudflare Proxy Attempt (Partial Success)

Based on advice from existing community posts about Hostinger blocking Meta webhooks, I put Cloudflare (free plan) in front of one site.

Results:

• GET requests all work perfectly through Cloudflare (media, categories, tags, pages all fetched)
• POST requests still return 429

Key finding: A direct curl POST from my local machine through the same Cloudflare proxy returned 401 (expected, auth issue) but NOT 429. So the POST block is path-specific. n8n cloud connects through a specific Cloudflare edge server that seems to have accumulated rate limit strikes, while my local machine connected through a different edge and had no issues.

Header stripping: Created a Cloudflare Transform Rule to remove X-Forwarded-For and CF-Connecting-IP headers before forwarding to origin. Still 429. The rate limiting appears to be based on the connecting IP at TCP level, not HTTP headers.

Current Situation

• All three Hostinger sites return 429 on POST requests from n8n cloud
• Non-Hostinger site works perfectly with identical code
• GET requests work, only POST fails
• Cloudflare proxy did not resolve POST blocking (though GET works through it)
• Curl from local machine through Cloudflare works (no 429)
• Hostinger technical team is investigating but no resolution yet
• Over 24 hours into this issue

What I Think Is Happening

Hostinger tracks rate limits at the origin server based on the connecting IP. n8n cloud has a fixed outbound IP on Azure. Once that IP exceeds the undisclosed threshold, all POST requests from it get blocked across all Hostinger sites globally. The cooldown is far longer than the 30-60 minutes support claims.

Even through Cloudflare, if n8n consistently routes through the same Cloudflare edge, that edge IP may also accumulate strikes at Hostinger's origin.

What I Need Help With

1. Has anyone on n8n cloud successfully resolved persistent 429 errors from Hostinger?
2. Is there a way to force n8n cloud outbound traffic through a proxy or VPN to change the source IP?
3. Has anyone used a static IP proxy service (like QuotaGuard) with n8n cloud to work around hosting rate limits?
4. Is there a Cloudflare configuration I am missing that would prevent the origin from seeing any client IP information?
5. Should I just move the sites off Hostinger entirely? Is this a lost cause?

Environment

• n8n: Cloud (latest)
• WordPress: 6.9.x
• Hosting: Hostinger shared hosting (multiple plans and accounts tested)
• CDN: Cloudflare free plan (currently active on one site)
• Security: Wordfence free with all rate limiting disabled and n8n IP allowlisted
• Page builders: Elementor and Divi (both affected identically)
• SEO plugins: Rank Math and Yoast (both affected identically)

Any help appreciated. Happy to provide more technical details if needed.