Someone has mirrored my WordPress site to their own domain. Can nginx waf solve this? It's causing my site to disappear from the search results pages.

https://erikpoehler.com/2022/08/02/how-to-block-direct-ip-access-to-your-nginx-web-server/ can i use this in aapanel ?

follow up, aapanel_kern. this site is using up my resources

Hello, Is the problem solved? Are they using reverse proxy? zimbabwee

aaPanel_Kern Not yet, please help me. I'm confused because I'm a beginner, especially when it comes to editing nginx. It seems they're using a reverse proxy. Please help me. This is very bad, my index in serps is even lost and it burdens the server. I tried using cloudflare under attack but it didn't work and cloudflare makes noindex nofollow if under attack is activated I have also activated CC, SmartCC on WAF but it still doesn't work

Hello, have you tried to allow only Cloudflare's IP access? zimbabwee

aaPanel_Kern How to ? they also use cloudflare on their domain

Configuring prohibits reverse proxying in CloudFlare "Security" → "Security rules" → "Create rule". Rule name: Block Reverse Proxy Match the conditions (select "Or" to combine multiple conditions to expand the interception range): headers → via → exists (the Via header exists, proxy feature) headers → x-forwarded-for → exists headers → x-real-ip → exists (there is a real IP header, commonly used by the proxy) headers → forwarded → exists zimbabwee

aaPanel_Kern I will try it right now

https://www.cloudflare.com/ips/ Only cloudflare's IP access is allowed: allow 173.245.48.0/20; allow 103.21.244.0/22; allow 103.22.200.0/22; allow 103.31.4.0/22; allow 141.101.64.0/18; allow 108.162.192.0/18; allow 190.93.240.0/20; allow 188.114.96.0/20; allow 197.234.240.0/22; allow 198.41.128.0/17; allow 162.158.0.0/15; allow 104.16.0.0/13; allow 104.24.0.0/14; allow 172.64.0.0/13; allow 131.0.72.0/22; allow 2400:cb00::/32; allow 2606:4700::/32; allow 2803:f800::/32; allow 2405:b500::/32; allow 2405:8100::/32; allow 2a06:98c0::/29; allow 2c0f:f248::/32; deny all; if(window.hljsLoader && !document.currentScript.parentNode.hasAttribute('data-s9e-livepreview-onupdate')) { window.hljsLoader.highlightBlocks(document.currentScript.parentNode); }

aaPanel_Kern still accessible, but sometimes get 444 or 403. Is there a server side solution so that it can only be accessed by my domain?

Nginx WAF

aaPanel_Kern

I'm not sure if you did it correctly
Do you use Website statistics-v2 to view the exception's IP?

zimbabwee

aaPanel_Kern Yes, it seems I blocked my own IP address. I used the logs on /wwwlogs to see which IP addresses visited the page. Because webstats v2 doesn't seem to update in real time.

Can a reverse proxy like this be done if I replace the webserver with apache?

« Previous Page