# How to start Vikunja (debian package)? **URL:** \ **Category:** Support\ **Created:** [28 May 2023 00:30 UTC](https://community.vikunja.io/t/how-to-start-vikunja-debian-package/1381 "2023-05-28T00:30:49Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![dkim19375](https://community.vikunja.io/user_avatar/community.vikunja.io/dkim19375/32/720_2.png) [@dkim19375](https://community.vikunja.io/u/dkim19375)\ **Post date:** [28 May 2023 00:30 UTC](https://community.vikunja.io/t/how-to-start-vikunja-debian-package/1381/1 "2023-05-28T00:30:49Z")
Note: [Also asked in Matrix, but had no response for an hour so I’m asking here too](https://matrix.to/#/!dCRiCiLaCCFVNlDnYs:matrix.org/%24moyAHvvF_8QGvT5dB4JC_eYDKksgKAa7nGOrluo1JgY) Using the .deb package (installed using dpkg), how do I actually _start_ vikunja? I thought that it’d automatically start, but when setting up the frontend, it couldn’t find the files because none had been generated If I do `sudo vikunja`, it outputs ```auto /usr/local/bin/vikunja: 1: Syntax error: "(" unexpected ``` ---
**Author:** ![kolaente](https://community.vikunja.io/user_avatar/community.vikunja.io/kolaente/32/5_2.png) [@kolaente](https://community.vikunja.io/u/kolaente)\ **Post date:** [28 May 2023 06:03 UTC](https://community.vikunja.io/t/how-to-start-vikunja-debian-package/1381/2 "2023-05-28T06:03:20Z")
When you install Vikunja it should set up a systemd service which should automatically start and stop the api on system boot. If that doesn’t start, check the logs. > [@dkim19375](#): > > but when setting up the frontend, it couldn’t find the files because none had been generated Can you explain that a little more? ---
**Author:** ![dkim19375](https://community.vikunja.io/user_avatar/community.vikunja.io/dkim19375/32/720_2.png) [@dkim19375](https://community.vikunja.io/u/dkim19375)\ **Post date:** [29 May 2023 02:40 UTC](https://community.vikunja.io/t/how-to-start-vikunja-debian-package/1381/3 "2023-05-29T02:40:20Z")
I just figured out that it’s a service (`vikunja.service`), and when viewing the logs, it shows: ```auto May 28 22:38:13 instance-1 systemd[1]: Started Vikunja. May 28 22:38:13 instance-1 systemd[458850]: vikunja.service: Failed to execute /usr/local/bin/vikunja: Exec format error May 28 22:38:13 instance-1 systemd[458850]: vikunja.service: Failed at step EXEC spawning /usr/local/bin/vikunja: Exec format error May 28 22:38:13 instance-1 systemd[1]: vikunja.service: Main process exited, code=exited, status=203/EXEC May 28 22:38:13 instance-1 systemd[1]: vikunja.service: Failed with result 'exit-code'. ``` I assume this is related to the syntax error I got in the original post Is there a download link or some way to reinstall the executable? ---
**Author:** ![kolaente](https://community.vikunja.io/user_avatar/community.vikunja.io/kolaente/32/5_2.png) [@kolaente](https://community.vikunja.io/u/kolaente)\ **Post date:** [30 May 2023 07:53 UTC](https://community.vikunja.io/t/how-to-start-vikunja-debian-package/1381/4 "2023-05-30T07:53:10Z")
Which architecture are you using? The .deb package only supports x86 but you can download other binaries from [https://dl.vikunja.io](https://dl.vikunja.io). ---
**Author:** ![dkim19375](https://community.vikunja.io/user_avatar/community.vikunja.io/dkim19375/32/720_2.png) [@dkim19375](https://community.vikunja.io/u/dkim19375)\ **Post date:** [30 May 2023 19:07 UTC](https://community.vikunja.io/t/how-to-start-vikunja-debian-package/1381/5 "2023-05-30T19:07:25Z")
Ah, I’m not using x86 When running `uname -m`, I get `aarch64` So does this mean that I just follow the directions from [Install Backend | Vikunja](https://vikunja.io/docs/install-backend/#install-from-binary) instead? I know that arm64/aarch64 is not that common, but I still suggest specifying that it’s not supported in the docs 🙂 ---
**Author:** ![kolaente](https://community.vikunja.io/user_avatar/community.vikunja.io/kolaente/32/5_2.png) [@kolaente](https://community.vikunja.io/u/kolaente)\ **Post date:** [30 May 2023 19:21 UTC](https://community.vikunja.io/t/how-to-start-vikunja-debian-package/1381/6 "2023-05-30T19:21:02Z")
Yeah that’s correct. I’ll take a look to check if we can put the supported architecture in the package’s meta information so that you get a proper warning during the installation. Edit: looks like it is already specified in nfpm but not propagated to the package?