You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all, I tried to access https://your.domain/logs?password=yourpassword as suggested in the documentation, but it displays the error below. Should this happen? In all the installations I have made of YellowCloaker, they all remain this way.
The log folder is properly with the Whiteclicks and Blackclicks and there are several clicks in both records.
Is there any way to automatically capture the IP of the leads that arrive in Whiteclicks? And condense this information into a blacklist.txt automatically?
My intention is to be able to determine this blacklist.txt in this option below:
Thanks for your attention, have a nice day! (:
The text was updated successfully, but these errors were encountered:
Nope, right now there is no way to get all whiteclicks ips into some kind
of a text file. Neither is there any way to automatically blacklist those
ips. What's the purpose of this? If your traffic is already being filtered
properly using the settings that you made - why do you need to create a
blacklist? How are you going to use that blacklist? Maybe in some other
installations of the cloaker, right? But then, why just not make the same
settings? No clues.
First of all, I tried to access https://your.domain/logs?password=yourpassword as suggested in the documentation, but it displays the error below. Should this happen? In all the installations I have made of YellowCloaker, they all remain this way.
The log folder is properly with the Whiteclicks and Blackclicks and there are several clicks in both records.
Is there any way to automatically capture the IP of the leads that arrive in Whiteclicks? And condense this information into a blacklist.txt automatically?
My intention is to be able to determine this blacklist.txt in this option below:
Thanks for your attention, have a nice day! (:
The text was updated successfully, but these errors were encountered: