Hypernode Nginx Targeted Bot Blocking -- 2
Budget: ₹750 – ₹1,250 INR
I need an experienced Nginx specialist who knows Hypernode inside-out to harden my Magento shop against abusive crawlers. Security threats are my primary concern; we have already been hit by a few DDoS-style spikes traced to shady user agents hammering layered navigation and search/filter URLs.
My plan is to deploy Hypernode’s official bot block configuration, tune it for our environment and keep it 100 % upgrade-safe. Country-wide blocking is off the table unless absolutely unavoidable—I only want the malicious traffic gone while Googlebot and other legitimate crawlers continue to index the site normally.
Scope of work
• Parse recent access logs, flag suspicious user agents and URL patterns (layered navigation, search, filter).
• Adapt Hypernode’s bot-block snippets in Nginx, adding custom rules for the patterns you discover.
• Return 403 or 444 to the offenders; real shoppers must reach every filter page without issues.
• Follow Hypernode best practices so future platform updates never overwrite the configuration.
• Provide a simple monitoring script or Grafana panel that proves reduced CPU and load averages after deployment.
Deliverables
1. Sanitised log analysis report highlighting abusive traffic signatures.
2. Final Nginx include file(s) with inline comments.
3. Test results showing blocked bots receive 403/444 while legitimate requests succeed.
4. Before-and-after performance snapshot (load, CPU, memory).
The job is finished once the rules are live, server load has stabilised and normal users confirm they can still browse layered navigation without hiccups.
My plan is to deploy Hypernode’s official bot block configuration, tune it for our environment and keep it 100 % upgrade-safe. Country-wide blocking is off the table unless absolutely unavoidable—I only want the malicious traffic gone while Googlebot and other legitimate crawlers continue to index the site normally.
Scope of work
• Parse recent access logs, flag suspicious user agents and URL patterns (layered navigation, search, filter).
• Adapt Hypernode’s bot-block snippets in Nginx, adding custom rules for the patterns you discover.
• Return 403 or 444 to the offenders; real shoppers must reach every filter page without issues.
• Follow Hypernode best practices so future platform updates never overwrite the configuration.
• Provide a simple monitoring script or Grafana panel that proves reduced CPU and load averages after deployment.
Deliverables
1. Sanitised log analysis report highlighting abusive traffic signatures.
2. Final Nginx include file(s) with inline comments.
3. Test results showing blocked bots receive 403/444 while legitimate requests succeed.
4. Before-and-after performance snapshot (load, CPU, memory).
The job is finished once the rules are live, server load has stabilised and normal users confirm they can still browse layered navigation without hiccups.