Aounds like the API key, or header, is invalid. Sure it does not ask for an Authorization header?
On Tue, Nov 10, 2020, 12:18 Robert Kudyba <rkud...@fordham.edu> wrote: > > Do any of you use any alternatives to use with ipset or populate >> > /etc/hosts.deny TCP Wrappers? >> >> Here's another useful resource: https://iptoasn.com/ >> > > Any idea how to download the list and update /etc/hosts on a regular > basis? I tried the suggested plain text command (after creating an API key): > curl -G https://api.abuseipdb.com/api/v2/blacklist \ > -d confidenceMinimum=90 \ > -H "Key: $YOUR_API_KEY" \ > -H "Accept: text/plain" > > But I get: > <!DOCTYPE html> > <html> > <head> > <meta charset="UTF-8" /> > <meta http-equiv="refresh" content="0;url=' > https://api.abuseipdb.com/login'" /> > > <title>Redirecting to https://api.abuseipdb.com/login</title> > </head> > <body> > Redirecting to <a href="https://api.abuseipdb.com/login";> > https://api.abuseipdb.com/login</a>. > </body> > _______________________________________________ > Fail2ban-users mailing list > Fail2ban-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/fail2ban-users >
_______________________________________________ Fail2ban-users mailing list Fail2ban-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fail2ban-users
