How many users can be created?

[CA2MI]

From what I remember there was a pretty big increase in the number of users that can be created now on a newer Algo server. What is the limit now?

[davidemyers]

From config.cfg:

You can add up to 65,534 new users over the lifetime of an AlgoVPN.

[CA2MI]

That's great. I tried to do 4,000 user in a new install and it took about 12 hours 1 cpu 1 gig on a Linode. I know really minimal. But the pipe broke so I'm not sure if it actually finished correctly. None of the .png files were created so it might not have finished correctly.

[davidemyers]

The limit used to be 252. When I increased the limit I only tested it to 260 to make sure the previous limit was gone. If I tried to test to 65,534 it would probably still be running... 😃

[CA2MI]

Maybe I'll try 2000 to start :)

[CA2MI]

I'm currently running 20 algos around the globe for a nice little crypto group.

[CA2MI]

I ran into this error...any idea what it might mean?

included: /root/algo/playbooks/rescue.yml for localhost

TASK [debug] *******************************************************************
ok: [localhost] => {
"fail_hint": [
"Sorry, but something went wrong!",
"Please check the troubleshooting guide.",
"https://trailofbits.github.io/algo/troubleshooting.html"
]
}

TASK [Fail the installation] ***************************************************
fatal: [localhost]: FAILED! => {"changed": false, "msg": "Failed as requested from task"}

PLAY RECAP *********************************************************************
localhost : ok=88 changed=12 unreachable=0 failed=1 skipped=32 rescued=1 ignored=0

stty: invalid integer argument: ‘A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[B\033[B\033[B\033[B\033[B\033[B\033[B\033[B\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\033[A\n\033[30’
root@localhost:~/algo#

[davidemyers]

That looks like you used the up and down arrow keys repeatedly somewhere where they weren't being read, then the key sequences all came out when Ansible finished. Was there an error message from Ansible prior to this output?

[CA2MI]

Well... It was sitting there for a bit so i did use the arrow keys that did show up and then it kicked in again it of course disappeared off the screen until the end which I saw an error this morning. I tried 2000 users. I'm currently blowing the server away and starting from scratch.

As part of my setup I do turn off as many "logs" as possible. This shouldn't be an issue running this prior to the install should it?

Disable logging - service rsyslog stop && systemctl disable rsyslog.service

[davidemyers]

I don't know whether or not disabling rsyslog would cause problems. On Ubuntu I think everything logs to the main journal (viewable with journalctl) and rsyslog is only used to duplicate the messages into traditional files for backwards compatibility with programs that expect to read those files. So if you disable rsyslog you can still read all logs with journalctl.

[CA2MI]

ok, I'll check that. I'm starting with a new server build and this is showing up. This appears when I seem to change the DNS to quad9. I used what I found in an earlier post.

---

dnscrypt_servers:
ipv4:
– quad9-doh-ip4-filter-pri
– quad9-doh-ip4-filter-alt
ipv6:
– quad9-doh-ip6-filter-pri
– quad9-doh-ip6-filter-alt

************ errors below ******************

TASK [dns : Ubuntu | Ensure that the dnscrypt-proxy service directory exist] ***
changed: [localhost]

TASK [dns : Ubuntu | Add custom requirements to successfully start the unit] ***
changed: [localhost]

TASK [dns : dnscrypt-proxy ip-blacklist configured] ****************************
changed: [localhost]

TASK [dns : dnscrypt-proxy configured] *****************************************
fatal: [localhost]: FAILED! => {"changed": false, "msg": "AnsibleUndefinedVariable: 'dict object' has no attribute 'ipv4'"}
included: /root/algo/playbooks/rescue.yml for localhost

TASK [debug] *******************************************************************
ok: [localhost] => {
"fail_hint": [
"Sorry, but something went wrong!",
"Please check the troubleshooting guide.",
"https://trailofbits.github.io/algo/troubleshooting.html"
]
}

TASK [Fail the installation] ***************************************************
fatal: [localhost]: FAILED! => {"changed": false, "msg": "Failed as requested from task"}

PLAY RECAP *********************************************************************
localhost : ok=61 changed=20 unreachable=0 failed=1 skipped=27 rescued=1 ignored=0

(.env) root@localhost:~/algo#

[davidemyers]

Be very careful with indentation when editing config.cfg.

Also the -alt servers are gone. I use this:

dnscrypt_servers:
  ipv4:
    - quad9-doh-ip4-filter-pri
  ipv6:
    - quad9-doh-ip6-filter-pri