Vikunja via Apache (Laragon) - localhost via "http://192.168.xx.x/..." does not work

Leslie · 18 September 2023 17:59

Hi.
I’m hosting Vikunja via Apache (Laragon), also Kanboard, and I’ve started the binaries of Vikunja before trying to gain access on “http://192.168.xx.x/…”. It does not work in my computer where binaries and Apache are installed and running and also locally on local devices connected to the same network. I’ve tried to run Vikunja from Apache (http://localhost) to android mobile. It needs to be "http://192.168.xx.x in browser. But when I will run this address, it shows nothing. With Kanboard it works as expected.
Kanboard works correctly with “http://192.168.xx.x” in all local devices in their browser. Vikunja does not work.

Does it work for anyone?

Leslie · 21 September 2023 10:18

Nobody has the same issue?

kolaente · 27 September 2023 08:22

Nothing or a “Cannot reach this address” error page from your browser?

Leslie · 27 September 2023 09:22

Nothing, just a blank page.

kolaente · 27 September 2023 15:41

Even in a private tab?

Leslie · 27 September 2023 16:37

Yes, the same problem.

kolaente · 27 September 2023 16:48

Anything in the browser console? (F12)

Leslie · 27 September 2023 16:50

kolaente · 29 September 2023 17:23

This looks like a rewrite or proxy issue. What is the response if you open the asset URL in the browser it complains in the console?

Leslie · 30 September 2023 12:06

The response is:

kolaente · 1 October 2023 11:35

That looks like you didn’t set up the asset hosting correctly. But it does work via localhost? Did you set a server name?

Leslie · 2 October 2023 15:29

Yes. I’ve tried rewrite the config file but nothing helps. It does work only on localhost, but only with Laragon “Vikunja.test” ServerName. 192.168.xx.x does not work at all (another tools such Kanboard) works correctly.

kolaente · 3 October 2023 09:10

But your ServerName is always Vikunja.test?

Leslie · 3 October 2023 09:19

Yes, only there it works

Leslie · 24 October 2023 19:13

It works now, thanks to Kolaente.

I’ve just needed to create a “config.yml” file in binaries folder with defining path
(
service:
staticpath: ‘/path/to/the/frontend/files’
)

to frontend (downloaded on PC) and run binaries. Now everything works flawlessly on IP:3456 port in browser locally. Without Laragon and Apache. Just running binaries (with Desktop or android app) or with running binaries+defined path to downloaded frontend on Windows.