Thanks! It’s still running as root, I’ll change this if I manage to see Vikunja in the browser.
Yes, the service us enabled and running. I figured out that service --status-all only calls status for sysvinit jobs, so it’s normal.
I have set the log to “DEBUG” but still can’t see any log. The log file(s) don’t get created. Here’s are last lines from calling sudo service vikunja status :
Jul 03 18:43:12 vps31 vikunja[5380]: 2021-07-03T18:43:12.150268198+02:00: INFO ▶ [EVENTS] 074 Starting handler, topic=task.created, subscriber_name=task.created.task.counter.incre
Jul 03 18:43:12 vps31 vikunja[5380]: 2021-07-03T18:43:12.150295618+02:00: INFO ▶ [EVENTS] 075 Starting handler, subscriber_name=task.assignee.created.task.assigned.notification.se
Jul 03 18:44:00 vps31 vikunja[5380]: 2021-07-03T18:44:00.01078948+02:00: DEBUG ▶ models/getTasksWithRemindersInTheNextMinute 076 [Task Reminder Cron] Looking for reminders between
Jul 03 18:44:00 vps31 vikunja[5380]: 2021-07-03T18:44:00.019779515+02:00: DEBUG ▶ models/getTasksWithRemindersInTheNextMinute 078 [Task Reminder Cron] Found 0 reminders
I still cannot make the front end talk to the back end, the Chrome console shows 404 errors when trying to reach the backend. https:/subdomain.domain.tld/api/v1/info redirects to the login page, which misses the Register button. Do you have a runbook or a list of commands to try? I’ve disabled ufw, tried many variants of the Apache site conf and Vikunja config.yml and am still lost.
Here are some samples of errors from the Chrome console:
app.92e95fe9.js : Uncaught (in promise) TypeError: Cannot read property 'imprint_url' of undefined
app.92e95fe9.js : Error during service worker registration: TypeError: Failed to register a ServiceWorker for scope ('https://subdomain.domain.tld/') with script ('subdomain.domain.tld/sw.js'): An unknown error occurred when fetching the script.
chunk-vendors.dc994606.js:64 : POST https://subdomain.domain.tld/api/v1/login net::ERR_CONNECTION_REFUSED
Here is a sample of my terminal:
jb@vps31:~$ curl https://localhost:3456/api/v1/info
curl: (35) error:1408F10B:SSL routines:ssl3_get_record:wrong version number
jb@vps31:~$ curl http://localhost:3456/api/v1/info
{"version":"v0.17.1","frontend_url":"https://subdomain.domain.tld","motd":"","link_sharing_enabled":true,"max_file_size":"20MB","registration_enabled":true,"available_migrators":null,"task_attachments_enabled":true,"enabled_background_providers":["upload"],"totp_enabled":true,"legal":{"imprint_url":"","privacy_policy_url":""},"caldav_enabled":true,"auth":{"local":{"enabled":true},"openid_connect":{"enabled":false,"redirect_url":"\u003cfrontend url\u003e","providers":null}},"email_reminders_enabled":true}
Calling /vi/info with curl appears in the vikunja service status as:
Jul 03 20:19:23 vps31 vikunja[17187]: 2021-07-03T20:19:23.654465069+02:00: WEB ▶ my.pub.lic.ip GET 200 /api/v1/info 508.957µs - curl/7.58.0 (I managed to have it logged, after replacing stdout with file in config.yml.)
I can see the output of /v1/info in the brower too, but only if I type http://subdomain.domain.tld:3456/api/v1/info . It doesn’t work with https or without the :3456
If it can help, they are on the same server. The FE has a SSL sertificate from Let’s Encrypt, seemingly like try.vikunja.io.
– EDIT:
I’ve set up a new site with a new Apache conf file, that is only active on Port 80. And tadam, it connected to the back-end!
It’s not a permanent solution though. I also notice a “Network error” every second or so.
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://subdomain.domain.tld:3456/api/v1/notifications?page=1. (Reason: CORS request did not succeed).