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

[GH-ISSUE #1849] Unathorized to create a new account in the Vikunja Selfhost deployment (docker compose) #6494

New Issue
Closed
opened 2026-04-20 17:05:47 -05:00 by GiteaMirror · 10 comments
GiteaMirror commented 2026-04-20 17:05:47 -05:00
Owner
Copy Link

Originally created by @Luigipie on GitHub (Nov 19, 2025).
Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/1849

Description

Hello, i'm having an issue trying to deploy Vikunja on docker, deployed successfully i can reach the webpage but every time i try to create an account, the system give me an "Unauthorized" response, what can be the reason?

Actually i'm going to share my docker compose setting file in the screenshot

Image

Vikunja Version

latest

Browser and version

No response

Can you reproduce the bug on the Vikunja demo site?

No

Screenshots

No response

Originally created by @Luigipie on GitHub (Nov 19, 2025). Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/1849 ### Description Hello, i'm having an issue trying to deploy Vikunja on docker, deployed successfully i can reach the webpage but every time i try to create an account, the system give me an "Unauthorized" response, what can be the reason? Actually i'm going to share my docker compose setting file in the screenshot <img width="524" height="562" alt="Image" src="https://github.com/user-attachments/assets/99ca3dcb-a89e-4f3b-bedc-13af428ea2f6" /> ### Vikunja Version latest ### Browser and version _No response_ ### Can you reproduce the bug on the Vikunja demo site? No ### Screenshots _No response_
GiteaMirror commented 2026-04-20 17:05:48 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Nov 19, 2025):

Are you accessing the frontend from the same url you put into the publicurl?

<!-- gh-comment-id:3554548273 --> @kolaente commented on GitHub (Nov 19, 2025): Are you accessing the frontend from the same url you put into the publicurl?
GiteaMirror commented 2026-04-20 17:05:48 -05:00
Author
Owner
Copy Link

@Luigipie commented on GitHub (Nov 19, 2025):

Are you accessing the frontend from the same url you put into the publicurl?

yes of course, otherway for me was impossible reach the WebUI, i put a screenshot for test

Image
<!-- gh-comment-id:3554581260 --> @Luigipie commented on GitHub (Nov 19, 2025): > Are you accessing the frontend from the same url you put into the publicurl? yes of course, otherway for me was impossible reach the WebUI, i put a screenshot for test <img width="1205" height="969" alt="Image" src="https://github.com/user-attachments/assets/ef22a75d-cbbf-4fdd-b3e6-084d98c3c482" />
GiteaMirror commented 2026-04-20 17:05:49 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Nov 19, 2025):

How are you using https without a domain?

<!-- gh-comment-id:3554596258 --> @kolaente commented on GitHub (Nov 19, 2025): How are you using https without a domain?
GiteaMirror commented 2026-04-20 17:05:49 -05:00
Author
Owner
Copy Link

@Luigipie commented on GitHub (Nov 19, 2025):

How are you using https without a domain?

Honestly the https was just a test, i've seen in other issue (#1303) they've resolved using the https protocol, but pratically in mine setup, everything is accesible locally and when not at home, trought tailscale

<!-- gh-comment-id:3554787418 --> @Luigipie commented on GitHub (Nov 19, 2025): > How are you using https without a domain? Honestly the https was just a test, i've seen in other issue (#1303) they've resolved using the https protocol, but pratically in mine setup, everything is accesible locally and when not at home, trought tailscale
GiteaMirror commented 2026-04-20 17:05:50 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Nov 19, 2025):

okay, but are you accessing it via https or http at the ip+port in your publicurl? Because if you're accessing via http, the publicurl is a different thing and thus the request is blocked.

<!-- gh-comment-id:3554816255 --> @kolaente commented on GitHub (Nov 19, 2025): okay, but are you accessing it via https or http at the ip+port in your publicurl? Because if you're accessing via http, the publicurl is a different thing and thus the request is blocked.
GiteaMirror commented 2026-04-20 17:05:51 -05:00
Author
Owner
Copy Link

@Luigipie commented on GitHub (Nov 19, 2025):

okay, but are you accessing it via https or http at the ip+port in your publicurl? Because if you're accessing via http, the publicurl is a different thing and thus the request is blocked.

only with my.IP:3456, with http/s://my.IP:3456 it says that is not possible complete the request and blocked the access

<!-- gh-comment-id:3554839279 --> @Luigipie commented on GitHub (Nov 19, 2025): > okay, but are you accessing it via https or http at the ip+port in your publicurl? Because if you're accessing via http, the publicurl is a different thing and thus the request is blocked. only with my.IP:3456, with http/s://my.IP:3456 it says that is not possible complete the request and blocked the access
GiteaMirror commented 2026-04-20 17:05:51 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Nov 19, 2025):

Then you'll need to adjust the publicurl to match that.

The other option would be to disable cors alltogether or extend the cors.origins option with the other publicurl.

<!-- gh-comment-id:3554870811 --> @kolaente commented on GitHub (Nov 19, 2025): Then you'll need to adjust the publicurl to match that. The other option would be to disable cors alltogether or extend the [`cors.origins`](https://vikunja.io/docs/config-options/#1-cors-origins) option with the other publicurl.
GiteaMirror commented 2026-04-20 17:05:51 -05:00
Author
Owner
Copy Link

@Luigipie commented on GitHub (Nov 20, 2025):

Then you'll need to adjust the publicurl to match that.

The other option would be to disable cors alltogether or extend the cors.origins option with the other publicurl.

Wait, the publicURL that is listed in the screenshot is just a test, i've already tried also with the https (without s) but also doesn't work, you'ave an example also how can i work with the cors.origins?

thank you

<!-- gh-comment-id:3559674489 --> @Luigipie commented on GitHub (Nov 20, 2025): > Then you'll need to adjust the publicurl to match that. > > The other option would be to disable cors alltogether or extend the [`cors.origins`](https://vikunja.io/docs/config-options/#1-cors-origins) option with the other publicurl. Wait, the publicURL that is listed in the screenshot is just a test, i've already tried also with the https (without s) but also doesn't work, you'ave an example also how can i work with the cors.origins? thank you
GiteaMirror commented 2026-04-20 17:05:52 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Nov 20, 2025):

If you put https, you need to configure your Vikunja instance so that it is accessible via https. If you only access Vikunja via http, the url should be configured to be accessed via http.

<!-- gh-comment-id:3559959143 --> @kolaente commented on GitHub (Nov 20, 2025): If you put `https`, you need to configure your Vikunja instance so that it is accessible via `https`. If you only access Vikunja via http, the url should be configured to be accessed via http.
GiteaMirror commented 2026-04-20 17:05:52 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Nov 21, 2025):

I'll close this as it seems to be more of a configuration issue than an actual bug. Please ping if you still need assistance.

<!-- gh-comment-id:3563140335 --> @kolaente commented on GitHub (Nov 21, 2025): I'll close this as it seems to be more of a configuration issue than an actual bug. Please ping if you still need assistance.
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#6494
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?