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

No ipv4 listening on new install #1930

New Issue
Closed
opened 2026-03-22 13:47:03 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-03-22 13:47:03 -05:00
Owner
Copy Link

Originally created by @jwynn6 on GitHub (Mar 18, 2024).

Description

Implementing exactly the traefik v2 example docker-compose, there is no listening port opened for ipv4. Modifying the VIKUNJA_SERVICE_INTERFACE to listen on 0.0.0.0:3456 has no effect either. Modifying it to listen on other ipv4 addresses (127.0.0.1:3456) does work however.

Vikunja Version

0.23 and unstable were both tested against

Browser and version

No response

Can you reproduce the bug on the Vikunja demo site?

No

Screenshots

No response

Originally created by @jwynn6 on GitHub (Mar 18, 2024). ### Description Implementing exactly the traefik v2 example docker-compose, there is no listening port opened for ipv4. Modifying the VIKUNJA_SERVICE_INTERFACE to listen on 0.0.0.0:3456 has no effect either. Modifying it to listen on other ipv4 addresses (127.0.0.1:3456) does work however. ### Vikunja Version 0.23 and unstable were both tested against ### Browser and version _No response_ ### Can you reproduce the bug on the Vikunja demo site? No ### Screenshots _No response_
GiteaMirror commented 2026-03-22 13:47:04 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Mar 19, 2024):

I was unable to reproduce this, it seems to work fine. The web interface listens on all adapters by default.

If you inspect the container, what IPs do you get? Does it work if you curl them on port 3456?

@kolaente commented on GitHub (Mar 19, 2024): I was unable to reproduce this, it seems to work fine. The web interface listens on all adapters by default. If you inspect the container, what IPs do you get? Does it work if you curl them on port `3456`?
GiteaMirror commented 2026-03-22 13:47:04 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Sep 13, 2024):

Closing as inactive, please ping or open a new issue with relevant information if you still have this problem.

@kolaente commented on GitHub (Sep 13, 2024): Closing as inactive, please ping or open a new issue with relevant information if you still have this problem.
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#1930
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?