Hi everyone,
I set up my second vikunja instance lately by using the api .deb packet and a nginx instance.
Since we register our users manually, I disabled user registration by setting enableregistration: false
in the /etc/vikunja/config.yml file.
This flag does not seem to get applied, even if reloading the vikunja and nginx service.
This is the debug log output from vikunja-service:
● vikunja.service - Vikunja
Loaded: loaded (/lib/systemd/system/vikunja.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2023-03-24 14:37:48 CET; 1s ago
Main PID: 4351 (vikunja)
Tasks: 5 (limit: 11791)
Memory: 43.4M
CPU: 226ms
CGroup: /system.slice/vikunja.service
└─4351 /usr/local/bin/vikunja
Mar 24 14:37:48 cVikunja systemd[1]: Started Vikunja.
Mar 24 14:37:49 cVikunja vikunja[4351]: 2023/03/24 14:37:49 No home directory found, not using config from ~/.config/vikunja/. Error was: $HOME is not defined
Mar 24 14:37:49 cVikunja vikunja[4351]: 2023/03/24 14:37:49 Using config file: /etc/vikunja/config.yml
Mar 24 14:37:49 cVikunja vikunja[4351]: 2023-03-24T14:37:49.016437387+01:00: INFO ▶ migration/Migrate 04e Ran all migrations successfully.
Mar 24 14:37:49 cVikunja vikunja[4351]: 2023-03-24T14:37:49.016851922+01:00: DEBUG ▶ models/RegisterReminderCron 04f [Task Reminder Cron] Timezone is GMT
Mar 24 14:37:49 cVikunja vikunja[4351]: 2023-03-24T14:37:49.017237591+01:00: INFO ▶ cmd/func25 050 Vikunja version v0.20.4
Mar 24 14:37:49 cVikunja vikunja[4351]: 2023-03-24T14:37:49.017963982+01:00: DEBUG ▶ routes/setupRateLimit 051 Rate limit configured with memory and 100 requests per 1m0s
Mar 24 14:37:49 cVikunja vikunja[4351]: 2023-03-24T14:37:49.018618166+01:00: DEBUG ▶ routes/setupRateLimit 052 Rate limit configured with memory and 100 requests per 1m0s
Mar 24 14:37:49 cVikunja vikunja[4351]: ⇨ http server started on [::]:3456
which looks to me like /etc/vikunja/config.yml is being used as a config file.
the /etc/vikunja/config.yml has this line in it:
# Whether to let new users registering themselves or not
enableregistration: false
However, registration via the frontend is still possible.
I could not find any other topic related to this, has someone an idea what this could be related to?
Thanks alot