On Frontend no Registration #1742

New Issue

DrAg0n141 · 2020-09-04T10:37:30Z

DrAg0n141 commented

2020-09-04 10:37:30 +00:00

Hi,

when i am start the Frontend there is no Registration Button when i go to /register then registration not working. What i am doing wrong i have installed the .deb package and create the systemd service it says by start:

Sep 03 20:39:11 Vikunja systemd[1]: Started Vikunja.
Sep 03 20:39:11 Vikunja vikunja[1344]: 2020/09/03 20:39:11 No home directory found, not using config from ~/.config/vikunja/. Error was: $HOME is not defined
Sep 03 20:39:11 Vikunja vikunja[1344]: 2020/09/03 20:39:11 Using config file: /etc/vikunja/config.yml
Sep 03 20:39:11 Vikunja vikunja[1344]: 2020-09-03T20:39:11.918039404+02:00: WARNING <96> [DATABASE] 004 Table migration Column id db default is 'NULL', struct default is
Sep 03 20:39:11 Vikunja vikunja[1344]: 2020-09-03T20:39:11.918173472+02:00: WARNING <96> [DATABASE] 005 Table migration Column description db default is 'NULL', struct default is
Sep 03 20:39:11 Vikunja vikunja[1344]: 2020-09-03T20:39:11.921908093+02:00: INFO <96> migration/Migrate 028 Ran all migrations successfully.
Sep 03 20:39:11 Vikunja vikunja[1344]: 2020-09-03T20:39:11.922192271+02:00: INFO <96> cmd/func2 029 Vikunja version 0.14.1
Sep 03 20:39:11 Vikunja vikunja[1344]: <87> http server started on [::]:3456

i think this is all fine

when i do curl http://vikunja...:3456/api/v1/info this comes:

{"version":"0.14.1","frontend_url":"","motd":"","link_sharing_enabled":true,"max_file_size":"20MB","registration_enabled":true,"available_migrators":null,"task_attachments_enabled":true,"enabled_background_providers":["upload"],"totp_enabled":true}

What i am doing wrong?

Hi, when i am start the Frontend there is no Registration Button when i go to /register then registration not working. What i am doing wrong i have installed the .deb package and create the systemd service it says by start: Sep 03 20:39:11 Vikunja systemd[1]: Started Vikunja. Sep 03 20:39:11 Vikunja vikunja[1344]: 2020/09/03 20:39:11 No home directory found, not using config from ~/.config/vikunja/. Error was: $HOME is not defined Sep 03 20:39:11 Vikunja vikunja[1344]: 2020/09/03 20:39:11 Using config file: /etc/vikunja/config.yml Sep 03 20:39:11 Vikunja vikunja[1344]: 2020-09-03T20:39:11.918039404+02:00: WARNING <E2><96><B6> [DATABASE] 004 Table migration Column id db default is 'NULL', struct default is Sep 03 20:39:11 Vikunja vikunja[1344]: 2020-09-03T20:39:11.918173472+02:00: WARNING <E2><96><B6> [DATABASE] 005 Table migration Column description db default is 'NULL', struct default is Sep 03 20:39:11 Vikunja vikunja[1344]: 2020-09-03T20:39:11.921908093+02:00: INFO <E2><96><B6> migration/Migrate 028 Ran all migrations successfully. Sep 03 20:39:11 Vikunja vikunja[1344]: 2020-09-03T20:39:11.922192271+02:00: INFO <E2><96><B6> cmd/func2 029 Vikunja version 0.14.1 Sep 03 20:39:11 Vikunja vikunja[1344]: <E2><87><A8> http server started on [::]:3456 i think this is all fine when i do curl http://vikunja...:3456/api/v1/info this comes: {"version":"0.14.1","frontend_url":"","motd":"","link_sharing_enabled":true,"max_file_size":"20MB","registration_enabled":true,"available_migrators":null,"task_attachments_enabled":true,"enabled_background_providers":["upload"],"totp_enabled":true} What i am doing wrong?

konrad commented

2020-09-04 11:55:33 +00:00

Have you configured the api url in the frontend?

Have you configured the [api url in the frontend](https://vikunja.io/docs/install-frontend/#api-url-configuration)?

DrAg0n141 commented

2020-09-04 12:00:52 +00:00

Yes i have both on the same server, but have tested with the ip of the server http://192.168.250.54:3456/api/v1 buth nothing helps me.

konrad commented

2020-09-04 12:07:04 +00:00

If you did not configure a reverse proxy, http://192.168.250.54/api/v1 will likely only give you the frontend.

You will likely need to set the api url in the index.html file of the frontend to http://vikunja...:3456/api/v1/info.

Can you show the requests of the console network tab in you browser (F12 -> Network) when loading the frontend? (Just open the browser console network tab, then reload the page and send me a screenshot of the requests happening)
It should try to make a request to the api/v1/info endpoint which is likely to fail, given the symtomes you described. We now just have to figure out why and how to fix it :)

If you did not configure a reverse proxy, `http://192.168.250.54/api/v1` will likely only give you the frontend. You will likely need to set the api url in the `index.html` file of the frontend to `http://vikunja...:3456/api/v1/info`. Can you show the requests of the console network tab in you browser (F12 -> Network) when loading the frontend? (Just open the browser console network tab, then reload the page and send me a screenshot of the requests happening) It should try to make a request to the `api/v1/info` endpoint which is likely to fail, given the symtomes you described. We now just have to figure out why and how to fix it :)

DrAg0n141 commented

2020-09-04 12:26:48 +00:00

Ok i dont know what i have done wrong the request to the api is in http the frontend with https that is not working. And the Api needs to be accesible from outside? With reverse proxy to api backend and frontend it is now working, but the backend is not protected from outside.

konrad commented

2020-09-04 14:39:30 +00:00

Yes, the api needs to be accessible from the outside. When you're using the frontend, your browser makes the requests to the api.

but the backend is not protected from outside.

What do you mean?

Yes, the api needs to be accessible from the outside. When you're using the frontend, your browser makes the requests to the api. > but the backend is not protected from outside. What do you mean?

DrAg0n141 commented

2020-09-04 15:03:16 +00:00

Ok than is now all right.

I mean that the API Url can use from everony someone can use my API with his URL he writes in his index.html my api url. Or is there something what i can do for protection?

Ok than is now all right. I mean that the API Url can use from everony someone can use my API with his URL he writes in his index.html my api url. Or is there something what i can do for protection?

konrad commented

2020-09-04 19:08:37 +00:00

There's two things you could do:

CORS - Take a look at the docs
Disable registration (I guess you're the only one who wants to use that installation of Vikunja?)

Also, even if the api would not be accessible from the outside, your frontend still would. Therefore, people could still use your installation if they know the url which they would need to know if they intended to use it with their frontend installation.

There's two things you could do: 1. CORS - [Take a look at the docs](https://vikunja.io/docs/config-options/) 2. Disable registration (I guess you're the only one who wants to use that installation of Vikunja?) Also, even if the api would not be accessible from the outside, your frontend still would. Therefore, people could still use your installation if they know the url which they would need to know if they intended to use it with their frontend installation.

konrad commented

2020-09-05 13:37:31 +00:00

Closing this as the issue seems to be resolved.

konrad closed this issue

2020-09-05 13:37:31 +00:00

konrad referenced this issue from a commit

2024-02-07 14:00:33 +00:00

chore(deps): update dependency vite to v2.9.0 (#1742)

Sign in to join this conversation.