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

[GH-ISSUE #2546] Viewing public link while logged in causes hang at login screen #6694

New Issue
Closed
opened 2026-04-20 17:16:48 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-20 17:16:48 -05:00
Owner
Copy Link

Originally created by @Neeko-iko on GitHub (Apr 5, 2026).
Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/2546

Pre-submission checklist

  • I have searched for existing open or closed issue reports with the same problem.

Description

if you have a project and you make a link to view that project for public use, then try it yourself, you will just hang at the login screen.

if you would like to test this yourself, you can follow these steps

  1. go to the demo site
  2. make a new project
  3. on that project, share it with a link share
  4. copy the link share you made and open it in a new tab
    instead of going to the board that you made publically viewable, it will just hang at the login screen.

this happens to people who both have access to the board, and to those who don't, as long as the user is logged in on the instance they will be unable to access the board through the public link.

to note, login options seem to be unavailable during this hang?

my assumption of whats happening (Without taking any peek at the code, so i may be wrong) is the authorization of the public URL is clashing with the authorization of the user, and somehow that ends up failing auth entirely.

Vikunja Version

demo & my personal instance on 2.2.2

Browser and version

happened with both firefox and vivaldi (both on their latest)

Can you reproduce the bug on the Vikunja demo site?

Yes

Screenshots

Image
Originally created by @Neeko-iko on GitHub (Apr 5, 2026). Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/2546 ### Pre-submission checklist - [x] I have searched for existing open or closed issue reports with the same problem. ### Description if you have a project and you make a link to view that project for public use, then try it yourself, you will just hang at the login screen. if you would like to test this yourself, you can follow these steps 1. go to the [demo site](https://try.vikunja.io) 2. make a new project 3. on that project, share it with a link share 4. copy the link share you made and open it in a new tab instead of going to the board that you made publically viewable, it will just hang at the login screen. this happens to people who both have access to the board, and to those who don't, as long as the user is logged in on the instance they will be unable to access the board through the public link. to note, login options seem to be unavailable during this hang? my assumption of whats happening (Without taking any peek at the code, so i may be wrong) is the authorization of the public URL is clashing with the authorization of the user, and somehow that ends up failing auth entirely. ### Vikunja Version demo & my personal instance on 2.2.2 ### Browser and version happened with both firefox and vivaldi (both on their latest) ### Can you reproduce the bug on the Vikunja demo site? Yes ### Screenshots <img width="1295" height="1028" alt="Image" src="https://github.com/user-attachments/assets/efcb57ea-c282-47fa-bdcc-c289c9b7a7b3" />
GiteaMirror commented 2026-04-20 17:16:50 -05:00
Author
Owner
Copy Link

@vikunja-bot-app[bot] commented on GitHub (Apr 9, 2026):

This issue has been fixed in #2561, please check with the next unstable build (should be ready for deployment in ~30min, also on the demo).

<!-- gh-comment-id:4213439620 --> @vikunja-bot-app[bot] commented on GitHub (Apr 9, 2026): This issue has been fixed in #2561, please check with the next unstable build (should be ready for deployment in ~30min, also on [the demo](https://try.vikunja.io)).
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#6694
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?