I tried to reproduce the issue on our ovh instance, with no luck: the wizard installation process went smoothly. Can you share with us the exact commercial offer you are using ? I’ll try to reproduce this with the exact same setup.
That being said, /dev/urandom call shouldn’t block…
Other question: Is this command blocks on your server: dd if=/dev/urandom bs=32 count=1 2>/dev/null | base64 -w 0 | rev | cut -b 2- | rev
If it doesn’t, we’ll consider swap the command in the wizards for this.
02/17/2021:04:46:35 PM][INF] crowdsec_wizard: Installing patterns
INFO[0000] Machine '244b714165db48e8b6d0eb0a0286881e' created successfully
INFO[0000] API credentials dumped to '/etc/crowdsec/local_api_credentials.yaml'
[02/17/2021:04:46:35 PM][INF] crowdsec_wizard: Crowdsec LAPI registered
INFO[0002] Successfully registered to Central API (CAPI)
INFO[0002] API credentials dumped to '/etc/crowdsec/online_api_credentials.yaml'
WARN[0002] Run 'sudo systemctl reload crowdsec' for the new configuration to be effective
[02/17/2021:04:46:38 PM][INF] crowdsec_wizard: Crowdsec CAPI registered
Created symlink from /etc/systemd/system/multi-user.target.wants/crowdsec.service to /etc/systemd/system/crowdsec.service.
[02/17/2021:04:46:44 PM][INF] crowdsec_wizard: Enabling and starting crowdsec daemon