mirror of
https://github.com/go-vikunja/vikunja.git
synced 2026-03-09 07:13:35 -05:00
desktop app not used olter port #293
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/vikunja#293
Reference in New Issue
Block a user
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?
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
@kolaente commented on GitHub (Oct 7, 2024):
Which desktop version are you using?
@Vincenzoferrara commented on GitHub (Oct 7, 2024):
in aur 24.2.1 link https://aur.archlinux.org/packages/vikunja-desktop-bin
@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
@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
@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?
@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
@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.
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.