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

desktop app not used olter port #293

New Issue
Closed
opened 2025-11-01 20:53:02 -05:00 by GiteaMirror · 7 comments
GiteaMirror commented 2025-11-01 20:53:02 -05:00
Owner
Copy Link

Originally created by @Vincenzoferrara on GitHub (Oct 6, 2024).

Description

I installed the desktop app in manjaro (arch)

my server is stable debian, and i have caddy reverse proxy on http and httpsa port (since it provides acme)

but the desktop software tries to connect to the standard port 3456, instead of my 443, even if explicitly declared, using 'https://todo-list.local:443' ((it's my internal domain name, and it works from web)

I would like vikunja to try to look for the standard https port too, like jellyfin does

moreover when you connect you don't know if it has started, as there is no output

Vikunja Version

my server (Vikunja api version v0.24.4 Built with go1.23.1)

Browser and version

No response

Can you reproduce the bug on the Vikunja demo site?

Please select

Screenshots

No response

Originally created by @Vincenzoferrara on GitHub (Oct 6, 2024). ### Description I installed the desktop app in manjaro (arch) my server is stable debian, and i have caddy reverse proxy on http and httpsa port (since it provides acme) but the desktop software tries to connect to the standard port 3456, instead of my 443, even if explicitly declared, using 'https://todo-list.local:443' ((it's my internal domain name, and it works from web) I would like vikunja to try to look for the standard https port too, like jellyfin does moreover when you connect you don't know if it has started, as there is no output ### Vikunja Version my server (Vikunja api version v0.24.4 Built with go1.23.1) ### Browser and version _No response_ ### Can you reproduce the bug on the Vikunja demo site? Please select ### Screenshots _No response_
GiteaMirror added the bug label 2025-11-01 20:53:02 -05:00
GiteaMirror commented 2025-11-01 20:53:03 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Oct 7, 2024):

Which desktop version are you using?

@kolaente commented on GitHub (Oct 7, 2024): Which desktop version are you using?
GiteaMirror commented 2025-11-01 20:53:03 -05:00
Author
Owner
Copy Link

@Vincenzoferrara commented on GitHub (Oct 7, 2024):

in aur 24.2.1 link https://aur.archlinux.org/packages/vikunja-desktop-bin

@Vincenzoferrara commented on GitHub (Oct 7, 2024): in aur 24.2.1 link https://aur.archlinux.org/packages/vikunja-desktop-bin
GiteaMirror commented 2025-11-01 20:53:03 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Oct 9, 2024):

Does it work if you use one of Vikunja's built packages? https://dl.vikunja.io/desktop/0.24.4

@kolaente commented on GitHub (Oct 9, 2024): Does it work if you use one of Vikunja's built packages? https://dl.vikunja.io/desktop/0.24.4
GiteaMirror commented 2025-11-01 20:53:03 -05:00
Author
Owner
Copy Link

@Vincenzoferrara commented on GitHub (Oct 9, 2024):

I just downloaded the app image , and I have the same problem

error log:
Could not find or use Vikunja installation at "todo-list.local:443". Please check if the url has the correct format and you can reach it when accessing it directly and try again.

but using the opnsense log (firewall) I noticed that it always asks on port 3456

@Vincenzoferrara commented on GitHub (Oct 9, 2024): I just downloaded the app image , and I have the same problem error log: Could not find or use Vikunja installation at "todo-list.local:443". Please check if the url has the correct format and you can reach it when accessing it directly and try again. but using the opnsense log (firewall) I noticed that it always asks on port 3456
GiteaMirror commented 2025-11-01 20:53:03 -05:00
Author
Owner
Copy Link

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

Are you sure it is the port that's the issue here? I was able to connect to a Vikunja instance running on a non-standard port without problems.

Did you enable cors on your instance?

@kolaente commented on GitHub (Oct 13, 2024): Are you sure it is the port that's the issue here? I was able to connect to a Vikunja instance running on a non-standard port without problems. Did you [enable cors](https://vikunja.io/docs/desktop-packages#installation) on your instance?
GiteaMirror commented 2025-11-01 20:53:04 -05:00
Author
Owner
Copy Link

@Vincenzoferrara commented on GitHub (Oct 13, 2024):

yes it worked, I read all the documentation before writing but that part is missing sorry for the inconvenience.

I would like to add 1 detail that I noticed

  • I would like to add that if you do not specify https vikunja does not try to connect (it would be useful if it was added automatically if it is not specified)
@Vincenzoferrara commented on GitHub (Oct 13, 2024): yes it worked, I read all the documentation before writing but that part is missing sorry for the inconvenience. I would like to add 1 detail that I noticed - I would like to add that if you do not specify https vikunja does not try to connect (it would be useful if it was added automatically if it is not specified)
GiteaMirror commented 2025-11-01 20:53:04 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Oct 14, 2024):

No worries, I've added the specific part on the page I linked to after your issue. It was mentioned elsewhere before, but rather hard to find.

I would like to add that if you do not specify https vikunja does not try to connect (it would be useful if it was added automatically if it is not specified)

The problem here is that browsers won't allow connecting between different protocols, and thus this won't work in most cases - except the electron app. Will take a look if there's a way to solve this.

Closing this as solved now, since the original issue is solved, please ping or open a new issue if you have any other problems.

@kolaente commented on GitHub (Oct 14, 2024): No worries, I've added the specific part on the page I linked to after your issue. It was mentioned elsewhere before, but rather hard to find. > I would like to add that if you do not specify https vikunja does not try to connect (it would be useful if it was added automatically if it is not specified) The problem here is that browsers won't allow connecting between different protocols, and thus this won't work in most cases - except the electron app. Will take a look if there's a way to solve this. Closing this as solved now, since the original issue is solved, please ping or open a new issue if you have any other problems.
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 bug
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#293
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?