I just ran the Ansible setup from that wiki doc on a bare Debian Buster machine and it worked. Maybe you just hit a transient network issue. Try running the Ansible command again, and see if it fails in the same spot.
My quick notes on the install:
# On Debian Buster
# This is for doing all the Ansible steps just on one computer.
# It assumes you aren't using a centralized Ansible setup
# (e.g. if this is your only Ansible using computer...).
#
# Run below as regular "sudo" user, or as root:
sudo apt update
# XXX Note, needs python 2 setuptools, NOT python3-setuptools
sudo apt install ansible python-setuptools
sudo apt clean
git clone https://gitlab.com/librespacefoundation/satnogs/satnogs-client-ansible.git
cd satnogs-client-ansible
cp -r production.dist production
vi production/inventory/hosts
# Make that file below
# * Replace ansible_user "debian" with your username that can ssh/sudo, NOT "satnogs".
# * Set a ansibe_host (the computer hostname).
---
all:
hosts:
satnogs:
ansible_host: 'satnogs-client'
ansible_user: 'debian'
ansible_ssh_pipelining: true
satnogs-setups:
hosts:
satnogs:
satnogs-radios:
hosts:
satnogs:
hamlib-utils:
hosts:
satnogs:
satnogs-clients:
hosts:
satnogs:
snmpds:
hosts:
satnogs:
gpsds:
hosts:
satnogs:
# Set up ssh keys:
ssh-keygen -t ed25519
cat ~/.ssh/id_ed25519.pub >> ~/.ssh/authorized_keys
# Make sure you can ssh to yourself (replace 127.0.0.1 with the
# name you set in ansible_host)
ssh 127.0.0.1 true
# Run the playbook:
ansible-playbook -i production/inventory -K site.yml
# Now run the SatNOGS setup:
sudo satnogs-setup