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

Desktop app does not accept all top level domains #201

New Issue
Closed
opened 2025-11-01 20:50:32 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2025-11-01 20:50:32 -05:00
Owner
Copy Link

Originally created by @CyberTechArmor on GitHub (Feb 28, 2024).

Description

It does not seem that the desktop app recognizes .app as a domain. When I attempted to use .com it tried to connect. Because there is no way for to trigger a manual connect I'm unable to use my.website.app or https://my.website.app.

Vikunja Version

0.22.1

Browser and version

Chrome Version 122.0.6261.70 (Official Build) (64-bit)

Can you reproduce the bug on the Vikunja demo site?

No

Screenshots

No response

Originally created by @CyberTechArmor on GitHub (Feb 28, 2024). ### Description It does not seem that the desktop app recognizes .app as a domain. When I attempted to use .com it tried to connect. Because there is no way for to trigger a manual connect I'm unable to use my.website.app or https://my.website.app. ### Vikunja Version 0.22.1 ### Browser and version Chrome Version 122.0.6261.70 (Official Build) (64-bit) ### Can you reproduce the bug on the Vikunja demo site? No ### Screenshots _No response_
GiteaMirror commented 2025-11-01 20:50:33 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Feb 28, 2024):

Vikunja does not look for a domain ending. Can you reach the api at https://my.website.app/api/v1/info? Do you have cors enabled?

@kolaente commented on GitHub (Feb 28, 2024): Vikunja does not look for a domain ending. Can you reach the api at `https://my.website.app/api/v1/info`? Do you have [cors](https://vikunja.io/docs/config-options/#cors) enabled?
GiteaMirror commented 2025-11-01 20:50:33 -05:00
Author
Owner
Copy Link

@CyberTechArmor commented on GitHub (Feb 28, 2024):

Adding /api/v1 resolved the issue:

my.website.app/api/v1

Side note, it defaulted to http:// and not https://. I was able to resolve to my site once I updated to https://my.website.app/api/v1

I appreciate the quick response.

@CyberTechArmor commented on GitHub (Feb 28, 2024): Adding /api/v1 resolved the issue: my.website.app/api/v1 Side note, it defaulted to http:// and not https://. I was able to resolve to my site once I updated to https://my.website.app/api/v1 I appreciate the quick response.
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#201
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?