7 commits

Author	SHA1	Message	Date
somebodywashere	315dbe24e4	Removed ipLimit from the panel, changed the code to work with fail2ban (#580) ... * Logging for fail2ban service Removed limitDevice and other unnecessary functions * Logging for fail2ban service Removed limitDevice and other unnecessary functions * fixed shouldCleanLog * last fix * reduced ip limit detection frequency to 30 sec (less logging, more precise) changed maxretry in fail2ban jail config to 2 to fit above * fixed check delay * added 5 seconds delay before cleaning logs	2023-06-15 22:45:34 +03:30
MHSanaei	6897534eb9	access.log #571 ... access.log will be clear only when limitip is not 0	2023-06-08 13:50:35 +03:30
MHSanaei	8d7199c678	some changes ... ip limit method back to v1.6.0 method remove event on getDBClientIps better show ip on log (",\n")	2023-06-03 18:59:32 +03:30
MHSanaei	2af8dd908b	change blockedips to AllowedIps ... now only those IPs that are allowed are able to establish a connection; other connections are dropped it will happen every 10 sec after user offline that IPs will be removed from AllowedIps	2023-05-25 03:21:31 +03:30
MHSanaei	a67fb4999b	bug fix - limit ip	2023-05-23 17:54:15 +03:30
MHSanaei	ef5a938cbf	Update check_client_ip_job.go	2023-04-28 00:30:49 +03:30
Hamidreza Ghavami	1ce00d5686	update and rename client ip job file	2023-04-14 00:07:13 +04:30

Renamed from web/job/check_clinet_ip_job.go (Browse further)