lyfsy

Exclamation HTAccess help needed Part 2 (now urgent)

Jan 22nd, 2020
911
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 4.97 KB | None | 0 0
  1. Exclamation HTAccess help needed Part 2 (now urgent)
  2. I previously sought advice about this issue in the following thread;
  3. ++++++++++++++
  4. list of top cheapest host http://Listfreetop.pw
  5.  
  6. Top 200 best traffic exchange sites http://Listfreetop.pw
  7.  
  8. free link exchange sites list http://Listfreetop.pw
  9. list of top ptc sites
  10. list of top ptp sites
  11. Listfreetop.pw
  12. Listfreetop.pw
  13. +++++++++++++++
  14.  
  15. https://www.webhostingtalk.com/showt...230&p=10138955
  16.  
  17. I was given the following code to try to achieve an effective block on websites referring people I am trying to prevent seeing my website - in particular one person who is a threat to me and to the community I represent;
  18. Code:
  19. RewriteEngine on
  20. RewriteCond %{HTTP_REFERER} newipnow\.com [NC,OR]
  21. RewriteCond %{HTTP_REFERER} hidemyass-freeproxy\.com [NC,OR]
  22. RewriteCond %{HTTP_REFERER} translate\.googleusercontent\.com [NC,OR]
  23. RewriteCond %{HTTP_REFERER} archive\.org [NC]
  24. RewriteRule .* - [F]
  25. Now in the last few minutes I checked on Stat Counter and discovered that the first block - for newipnow.com - didn't work as another person who is a threat to me used it and was able to access my website despite the above code in my HTAccess. This second person is a bigger threat to me because he has threatened to kill me in the past (and the police believed he was bluffing to my total fury).
  26.  
  27. So this is now urgent. How do I fix this on my HTAccess file and make sure it actually works? I'm desperate here.
  28. Many reasons "REFERER" might be bypassed or simply not work.
  29. Maybe this will help you get on the right road:
  30. https://forums.cpanel.net/threads/ht...31/post-300623
  31.  
  32. make money kh3
  33. www.trinityfunnelsystem.com
  34. cloudcone.com
  35. seastarhits.com
  36. domain and range
  37. secure.hostgator.com
  38. 10buckblast.com
  39. e host morgan
  40.  
  41. Show your support for everyone affected by the Australian bush fires, and those fighting them
  42. Not really, because the code suggested is what I am already using for IP deny - and at times even that hasn't worked.
  43. I am interested though in this comment; "One very easy thing to do is just simply drop all connections that have an "X-Forwarded-For" variable set and this kind of block can be setup easily in .HTACCESS."
  44.  
  45. From what was said, this is what most proxies use and would be useful. So how would I do this?
  46. Not really, because the code suggested is what I am already using for IP deny - and at times even that hasn't worked.
  47. Looks like you missed the rest of that block and only saw the IP?
  48. <Files *>Order Allow,Deny
  49. Allow from all
  50. Deny from 10.1.3.0/24
  51. Deny from hidemyass.com
  52. deny from proxy.com
  53. deny from anonymouse.com
  54. deny from proxify.com
  55. </Files>
  56. Show your support for everyone affected by the Australian bush fires, and those fighting them
  57. No I didn't miss that. "Deny from" hasn't been working for IP's at times so why would it work for websites that I'm already having issues with too? That's what I meant.
  58. Could you show me that other coding I asked about?
  59. I confirmed the rewrites do block if they have the keywords in the referer header. So what does the referer in a log file show? Is the user agent used an actual browser or something else obvious like "newipnow-proxy"? Again both coming from the apache log files and not scripts. A few log entry examples of those that shouldn't not have access may help.
  60. -Steven | u2-web@Cooini, LLC - Business Shared Hosting | Isolate sites with Webspaces | Site Builder | PHP-FPM | MariaDB
  61. WHMCS Modules: Staff Knowledgebase | Custom Modules and Hooks
  62. I previously sought advice about this issue in the following thread;
  63. https://www.webhostingtalk.com/showt...230&p=10138955
  64.  
  65. I was given the following code to try to achieve an effective block on websites referring people I am trying to prevent seeing my website - in particular one person who is a threat to me and to the community I represent;
  66. Code:
  67. RewriteEngine on
  68. RewriteCond %{HTTP_REFERER} newipnow\.com [NC,OR]
  69. RewriteCond %{HTTP_REFERER} hidemyass-freeproxy\.com [NC,OR]
  70. RewriteCond %{HTTP_REFERER} translate\.googleusercontent\.com [NC,OR]
  71. RewriteCond %{HTTP_REFERER} archive\.org [NC]
  72. RewriteRule .* - [F]
  73. Now in the last few minutes I checked on Stat Counter and discovered that the first block - for newipnow.com - didn't work as another person who is a threat to me used it and was able to access my website despite the above code in my HTAccess. This second person is a bigger threat to me because he has threatened to kill me in the past (and the police believed he was bluffing to my total fury).
  74.  
  75. So this is now urgent. How do I fix this on my HTAccess file and make sure it actually works? I'm desperate here.
  76. Use a provider that can give you access to a CDN that can just block entire countries.
  77. Akamai does this well and you can block entire IP ranges.
  78. But you need to block all VPN ports as well.
  79. Just blocking single IP addresses is pointless as they can get new ones easily.
  80. If privacy is that important you are probably better off hosting your stuff on a private cloud and allowing access to designated IPs.
Advertisement
Add Comment
Please, Sign In to add comment