No, you should not. The function is moved to the group management page, as indicated on your first screen capture.
You have host connectivity problems shown in your debug log:
*** [ DIAGNOSING ]: Networking
[✗] No IPv4 address(es) found on the eth0 interface.
[✗] No IPv6 address(es) found on the eth0 interface.
[i] Default IPv4 gateway: 192.168.1.1
* Pinging 192.168.1.1...
[✗] Gateway did not respond. (https://discourse.pi-hole.net/t/why-is-a-default-gateway-important-for-pi-hole/3546)
*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] register-acunt-fanpage89.suportconfrim76.ml is 0.0.0.0 via localhost (127.0.0.1)
[✗] Failed to resolve register-acunt-fanpage89.suportconfrim76.ml via Pi-hole (192.168.1.64)
You can add blocklists on the group management page, but not if they are duplicates. It appears you have tried to add duplicates. This warning appears three times in your debug log:
2020-05-15 21:46:49: (mod_fastcgi.c.421) FastCGI-stderr: PHP Warning: SQLite3Stmt::execute(): Unable to execute statement: UNIQUE constraint failed: adlist.address in /var/www/html/admin/scripts/pi-hole/php/groups.php on line 687
You have set an IPv4 address in the Pi-hole, but if there is no active interface on the Pi, this will do no good. Let's take a quick look at the interfaces on the Pi. Outputs of the following please:
Hello guys. I'm sorry, but I dont know much about system administration, and I just dont know to "get this sorted out". I'm kind of stuck.
I've uninstalled everything from the Raspbian, uninstalled Pi-hole and installed again, and followed all steps in the documentation, and still doesnt works.
However, now it registers some queries, but theres any ads being blocked.
Your new debug log shows no connectivity from the Pi to the LAN:
*** [ DIAGNOSING ]: Networking
[✗] No IPv4 address(es) found on the eth0 interface.
[✗] No IPv6 address(es) found on the eth0 interface.
[i] Default IPv4 gateway: 192.168.1.1
* Pinging 192.168.1.1...
[✗] Gateway did not respond. (https://discourse.pi-hole.net/t/why-is-a-default-gateway-important-for-pi-hole/3546)
*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] ehg-streamload.hitbox.com is 0.0.0.0 via localhost (127.0.0.1)
[✗] Failed to resolve ehg-streamload.hitbox.com via Pi-hole (192.168.1.64)
May 24 13:17:04 dnsmasq[557]: warning: interface eth0 does not currently exist
The 39 queries you see are from Pi-hole on the internal loopback address and you would not expect to see any of these requests blocked.