Facebook
Twitter
-
If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
CentOS2Alma discussion -
Please beaware of a breaking change in the REST API on the next Plesk release (18.0.62).Starting from Plesk Obsidian 18.0.62, requests to REST API containing the Content-Type header with a media-type directive other than “application/json” will result in the HTTP “415 Unsupported Media Type” client error response code. Read more here
GEOLOCATION: How to deny access by IP?
- Thread starter emperor
- Start date
You can describe your business case and vote for this feature here https://plesk.uservoice.com/forums/...suggestions/4173744-enable-nginx-geoip-module
Also you can start using Fail2ban to avoid future acceess requests from unwanted IPs.
Also you can start using Fail2ban to avoid future acceess requests from unwanted IPs.
@emperor,
There is the "Apache way of doing things" and the possibility to change the Nginx binary, as has been suggested by IgorG.
What is your preference?
If you like to follow the Nginx method, please let me know: I will start testing a custom compilation of Nginx, including geoip module.
Regards.....
There is the "Apache way of doing things" and the possibility to change the Nginx binary, as has been suggested by IgorG.
What is your preference?
If you like to follow the Nginx method, please let me know: I will start testing a custom compilation of Nginx, including geoip module.
Regards.....
burnley
Regular Pleskian
Hate to dig up old threads, however this one is interesting. I've voted at https://plesk.uservoice.com/forums/...suggestions/4173744-enable-nginx-geoip-module and added a possible use case, quoting:
"It'd be a great addition to the sw-nginx build. Enforcing rate limits is a must have these days and using ngx_http_geoip_module should be a very effective way to slow down the botnets' brute force attacks against commonly abused locations, like Wordpress/Joomla/Drupal or Magento login pages. A basic example:
limit_req_zone $geoip_country_code zone=geoipcountrycode:10m rate=5r/m;
location ~* (\/wp-login\.php|\/administrator) {
limit_req zone=geoipcountrycode burst=10;
proxy_pass http://real.serv.er:7080;
[...]"
"It'd be a great addition to the sw-nginx build. Enforcing rate limits is a must have these days and using ngx_http_geoip_module should be a very effective way to slow down the botnets' brute force attacks against commonly abused locations, like Wordpress/Joomla/Drupal or Magento login pages. A basic example:
limit_req_zone $geoip_country_code zone=geoipcountrycode:10m rate=5r/m;
location ~* (\/wp-login\.php|\/administrator) {
limit_req zone=geoipcountrycode burst=10;
proxy_pass http://real.serv.er:7080;
[...]"
Similar threads
