github-starred/vikunja
2
0
Fork 0
mirror of https://github.com/go-vikunja/vikunja.git synced 2026-05-06 03:27:53 -05:00
Code Issues 690 Packages Projects Releases 11 Wiki Activity

[GH-ISSUE #75] Bug: Docker instance using default compose template - Error message on web page on first login #5937

New Issue
Closed
opened 2026-04-20 16:23:51 -05:00 by GiteaMirror · 8 comments
GiteaMirror commented 2026-04-20 16:23:51 -05:00
Owner
Copy Link

Originally created by @jamess60 on GitHub (Jul 6, 2023).
Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/75

Description

Hi

I have just spun up a docker instance of Vikunja using the compose example (without any reverse proxy) - see here

When logging in for the first time, I get the following error:
An error occurred: AxiosError: Network Error Please check if the api url is correct.

The logs for the DB and FE containers look fine, but this is the output of the API container:

info: creating the new user vikunja with 1000:1000
usermod: no changes
2023/07/06 19:49:07 No config file found, using default or config from environment variables.
2023-07-06T19:49:07.351882121Z: CRITICAL ▶ migration/Migrate 002 Migration failed: dial tcp: lookup db on 127.0.0.11:53: no such host
^ Infinite loop of these lines

Vikunja Frontend Version

docker:latest

Vikunja API Version

docker:latest

Browser and version

Firefox Developer Edition 116.0b1 macOS

Can you reproduce the bug on the Vikunja demo site?

No

Screenshots

Screenshot 2023-07-06 at 21 55 11

Originally created by @jamess60 on GitHub (Jul 6, 2023). Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/75 ### Description Hi I have just spun up a docker instance of Vikunja using the compose example (without any reverse proxy) - see [here](https://vikunja.io/docs/full-docker-example/) When logging in for the first time, I get the following error: An error occurred: AxiosError: Network Error Please check if the api url is correct. The logs for the DB and FE containers look fine, but this is the output of the API container: info: creating the new user vikunja with 1000:1000 usermod: no changes 2023/07/06 19:49:07 No config file found, using default or config from environment variables. 2023-07-06T19:49:07.351882121Z: CRITICAL ▶ migration/Migrate 002 Migration failed: dial tcp: lookup db on 127.0.0.11:53: no such host ^ Infinite loop of these lines ### Vikunja Frontend Version docker:latest ### Vikunja API Version docker:latest ### Browser and version Firefox Developer Edition 116.0b1 macOS ### Can you reproduce the bug on the Vikunja demo site? No ### Screenshots ![Screenshot 2023-07-06 at 21 55 11](https://github.com/go-vikunja/api/assets/126415249/141afded-75da-47eb-8481-bb246b0c60c4)
GiteaMirror commented 2026-04-20 16:23:52 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Jul 6, 2023):

2023-07-06T19:49:07.351882121Z: CRITICAL arrow_forward migration/Migrate 002 Migration failed: dial tcp: lookup db on 127.0.0.11:53: no such host

That means in your config the api can't reach the database? Did you use the compose file verbantim?

When the api can't reach the DB it won't start up, hence the error message in the frontend.

<!-- gh-comment-id:1624252848 --> @kolaente commented on GitHub (Jul 6, 2023): > 2023-07-06T19:49:07.351882121Z: CRITICAL arrow_forward migration/Migrate 002 Migration failed: dial tcp: lookup db on 127.0.0.11:53: no such host That means in your config the api can't reach the database? Did you use the compose file verbantim? When the api can't reach the DB it won't start up, hence the error message in the frontend.
GiteaMirror commented 2026-04-20 16:23:53 -05:00
Author
Owner
Copy Link

@jamess60 commented on GitHub (Jul 6, 2023):

Hi

Changes made to the default:

  • Added "vikunja-" to each service name (and updated the api depends on to reflect the new name)
  • Updated VIKUNJA_API_URL to the IP of the host (as the instructions state)
  • DB password (its the same in API and DB so should be ok)
  • Host side of the volume path

I didnt make any changes that would cause issues as far as I can tell

My compose exert can be found in this pastebin, the password is github123, there is no expiration date
https://pastebin.com/d30P37NZ

<!-- gh-comment-id:1624257058 --> @jamess60 commented on GitHub (Jul 6, 2023): Hi Changes made to the default: - Added "vikunja-" to each service name (and updated the api depends on to reflect the new name) - Updated VIKUNJA_API_URL to the IP of the host (as the instructions state) - DB password (its the same in API and DB so should be ok) - Host side of the volume path I didnt make any changes that would cause issues as far as I can tell My compose exert can be found in this pastebin, the password is github123, there is no expiration date https://pastebin.com/d30P37NZ
GiteaMirror commented 2026-04-20 16:23:53 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Jul 6, 2023):

Added "vikunja-" to each service name (and updated the api depends on to reflect the new name)

That changes the name of the database service. You need to adjust the value of VIKUNJA_DATABASE_HOST in the api config.

<!-- gh-comment-id:1624258733 --> @kolaente commented on GitHub (Jul 6, 2023): > Added "vikunja-" to each service name (and updated the api depends on to reflect the new name) That changes the name of the database service. You need to adjust the value of `VIKUNJA_DATABASE_HOST` in the api config.
GiteaMirror commented 2026-04-20 16:23:53 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Jul 6, 2023):

Why did you prefix the name? Compose does that automatically?

<!-- gh-comment-id:1624258977 --> @kolaente commented on GitHub (Jul 6, 2023): Why did you prefix the name? Compose does that automatically?
GiteaMirror commented 2026-04-20 16:23:53 -05:00
Author
Owner
Copy Link

@jamess60 commented on GitHub (Jul 6, 2023):

Good spot - layer 8 issue afterall! Thank you so much - I do apologise!

I changed it because docker changed the prefix to the directory name the compose file was in which wasnt ideal for me.

<!-- gh-comment-id:1624263236 --> @jamess60 commented on GitHub (Jul 6, 2023): Good spot - layer 8 issue afterall! Thank you so much - I do apologise! I changed it because docker changed the prefix to the directory name the compose file was in which wasnt ideal for me.
GiteaMirror commented 2026-04-20 16:23:54 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Jul 6, 2023):

Glad to hear it's solved now!

I changed it because docker changed the prefix to the directory name the compose file was in which wasnt ideal for me.

You can change that with the COMPOSE_PROJECT_NAME environment variable. It only has to be set in your shell, but you can also put it in a .env file and docker compose will read and pick that up.

<!-- gh-comment-id:1624267101 --> @kolaente commented on GitHub (Jul 6, 2023): Glad to hear it's solved now! > I changed it because docker changed the prefix to the directory name the compose file was in which wasnt ideal for me. You can change that with the `COMPOSE_PROJECT_NAME` environment variable. It only has to be set in your shell, but you can also put it in a `.env` file and docker compose will read and pick that up.
GiteaMirror commented 2026-04-20 16:23:55 -05:00
Author
Owner
Copy Link

@jamess60 commented on GitHub (Jul 6, 2023):

Sweet - thanks for the tip!

Noticed it even supports 2FA, must say this is a really polished and well thought out tool, thanks guys! Good effort

<!-- gh-comment-id:1624272701 --> @jamess60 commented on GitHub (Jul 6, 2023): Sweet - thanks for the tip! Noticed it even supports 2FA, must say this is a really polished and well thought out tool, thanks guys! Good effort
GiteaMirror commented 2026-04-20 16:23:55 -05:00
Author
Owner
Copy Link

@Neurology0443 commented on GitHub (Jul 23, 2023):

Solved also my issue ! Thanks for your beautiful piece of software !

<!-- gh-comment-id:1646985598 --> @Neurology0443 commented on GitHub (Jul 23, 2023): Solved also my issue ! Thanks for your beautiful piece of software !
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
area/attachments
area/auth
area/avatars
area/backup-restore
area/caldav
area/calendar-view
area/comments
area/config
area/database
area/desktop
area/docker
area/email
area/favorites
area/filters
area/frontend
area/gantt
area/i18n
area/import-export
area/internal-code
area/kanban
area/labels
area/list-view
area/mobile
area/notifications
area/permissions
area/projects
area/pwa
area/recurring-tasks
area/reminders
area/search
area/shortcuts
area/subtasks
area/sync
area/table-view
area/task-editor
area/task-metadata
area/task-relations
area/teams
area/theming
area/time-tracking
area/typesense
area/views
area/webhooks
bug
changes requested
concern/accessibility
concern/performance
concern/regression
concern/ux
confirmed
db/mysql
dependencies
enhancement
good first issue
help wanted
integration/inbound
integration/outbound
kind/bug
kind/feature
needs reproduction
pull-request
Mirrored from GitHub Pull Request
 question
security
support
upstream issue
waiting for reply
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#5937
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?