Hello all,
On 3rd attempt to install following exact instructions from Debian and Apache guides. I get to the login screen only for it to be unable to find the API. I’m ready to pull my hair out.
Please help. No clue what I’m doing but I have to get this working for a project.
Using DigitalOcean Debian droplet. Followed guide exactly.
Can you reach the api url in your browser? (try https://your-domain.tld/api/v1/info)
Anything in the logs?
No logs are being produced even though the default config is untouched in that section (except i set everything to debug). no /logs directory exists inside opt/vikunja/. I’ve successfully gotten it to stop throwing me that specific error by restarting the linux service for vikunja, but now when i try to create a user acct, i get a “Internal Server Error” on the front-end. since i dont have a log available to me, im stuck.
No the API returns a 404
If you can’t reach the api then you should start by looking at the proxy (are you using one?)
Logs should be available via journalctl, they are passed to stdout by default.
Ever since v0.23.0 I am getting the same error when trying to log in on the desktop app. I can access Vikunja without any problems from the browser, only the desktop frontend does not work. Also, I can access https://vikunja.mydomain.com/api/v1/info without any problems. The logs I get from the vikunja container are:
123.123.123.123 GET 200 /api/v1/info 99.434µs - Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) vikunja-desktop/v0.23.0 Chrome/120.0.6099.276 Electron/28.2.2 Safari/537.36
There is no error displayed in the logs, but for some reason the desktop app still gives me the message that it could not reach it.
I am using Vikunja in docker with nginx as a proxy as described in the in the docs.
Ok turns out I had to set VIKUNJA_CORS_ENABLE=true.