Fresh desktop install cannot connect to any servers

Question

Fresh desktop install cannot connect to any servers

codevski opened this issue 10 months ago · 17 comments

Description

So I have a docker selfhosted instance which works fine in the browser but when I try to setup desktop app I cannot seem to get it to connect. I have also tried connecting to official (saw someone say to test it regarding another issue someone was having and I still cannot connect.

Vikunja Version

"v0.23.0"

Browser and version

Desktop: Both Flatpak and AUR bin 0.23.0-1

Can you reproduce the bug on the Vikunja demo site?

No

Screenshots

Answer 1 · 2024-02-27T09:17:41.000Z

Can you check what the API response is when you set the url? (CTRL+Shift+I and then "network")

Answer 2 · 2024-03-01T08:03:29.000Z

Here a Screenshot from my desktop app. I experience the same issue.
(Replaced the domain name with ---- after the request of couse)

It worked perfect until the update where backend and frontend were moved into one docker container.
Frontend works well in Firefox aswell as android app.

Answer 3 · 2024-03-01T08:04:40.000Z

Did you enable cors?

Answer 4 · 2024-03-01T08:06:50.000Z

Let me check. It stopped working, when I updated from the seperate frontend/backend containers to the new integrated one.

Answer 5 · 2024-03-01T08:11:25.000Z

As mentioned in the release notes, the cors settings were changed in that release.

Answer 6 · 2024-03-01T08:19:44.000Z

I am playing around with cors and port settings a bit, maybe the issue lies there.

This is the exact step in the code where it stops.

Answer 7 · 2024-03-01T08:24:29.000Z

The network error from the screenshot you sent before said "CORS Error". That's a pretty strong indication that you didn't enable CORS. Does it work if you enable it?

Answer 8 · 2024-03-01T08:33:04.000Z

No, but I think the issue may lie within reverse proxy and ports settings.
Only strange that Vikunja App connects without any issue.

Answer 9 · 2024-03-01T08:43:49.000Z

In the dev tools, what's the value of the access-control-allow-origin header in the response of the request to /info?

Answer 10 · 2024-03-01T09:28:58.000Z

Protarios commented 10 months ago

Answer 11 · 2024-03-03T21:12:34.000Z

Hey! I have the same issue. I have a self-hosted instance running and working fine in the browser but when I try to setup desktop app I cannot seem to get it to connect. I tried my instance and the official one with both having same access problem.

Answer 12 · 2024-03-03T21:21:30.000Z

@cerealconyogurt What do you see in the dev tools? (ctrl + shift + I)

Answer 13 · 2024-03-20T16:49:05.000Z

I have the same issue. I have a self-hosted instance running and working fine in the browser and in the android app, but when I try to setup desktop app I cannot seem to get it to connect. I tried my instance (flatpak and .RPM) and the official one with both having same access problem.
In the dev tools, there is this error message:

I tried to create the file in the server folder where the Vinkunja container is installed, but I was unsuccessful in activating this cors.

cors:
enable: true
origins:
- "*"

I put it this way, as suggested in the documentation, am I doing something wrong?

Answer 14 · 2024-03-21T16:20:53.000Z

I tried to move the config.yml to /etc/vikunja in the server, but without success

Answer 15 · 2024-03-28T20:44:03.000Z

@brunotenisi Does it work if you set VIKUNJA_CORS_ENABLE? The default value for origins is *.

Answer 16 · 2024-04-02T12:48:00.000Z

@brunotenisi Does it work if you set VIKUNJA_CORS_ENABLE? The default value for origins is *.

Hello @kolaente, thank you for reply. I found the answer in a post in the vikunja community, here.

The fix was to add VIKUNJA_CORS_ENABLE: true to the docker compose environment.

After this, had to take the dockers down, and put them up again.