H2-invent / jitsi-admin

Organize and fully controll your jitsi meet meetings. Make your meeting secure and be sure that only you and your fellows can join your meeting.
https://meetling.de
GNU Affero General Public License v3.0
133 stars 48 forks source link

An exception occurred while executing a query: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'jitsiadmin.fos_user' doesn't exist #331

Closed epigraphe closed 2 years ago

epigraphe commented 2 years ago

Describe the bug A clear and concise description of what the bug is.

To Reproduce Steps to reproduce the behavior:

  1. Clean install of jitsi-admin (docker-install)
  2. Reg user
  3. Trying to login
  4. See error

Screenshots image

Desktop (please complete the following information):

holema commented 2 years ago

Hello @epigraphe, Which Version do you use for the installation?

This error occurs, when the schema in the database is not created correctly. On which OS did you install the jitsi-admin?

did you setup the jitsi-admin in dev or prod mode?

holema commented 2 years ago

I think I found the error. It seems you are using the local dev environment. There were some breaking changes we did in the prod docker-compose file and we did not migrate this to the docker-compose test.

So 0.73.6 should fix this issue. Just make a git pull on the master branch and try to reinstall the jitsi-admin with bash installDocker.sh

epigraphe commented 2 years ago

Trying to reinstall anf got next erorr:


ERROR: Version in "./docker-compose.test.yml" is unsupported. You might be seeing this error because you're using the wrong Compose file version. Either specify a supported version (e.g "2.2" or "3.3") and place your service definitions under the `services` key, or omit the `version` key and place your service definitions at the root of the file to use version 1.
For more on the Compose file format versions, see https://docs.docker.com/compose/compose-file/

Ubuntu 20,04 dev mode

holema commented 2 years ago

what version of docker-compose do you use? I had to increase the docker-compose version to 3.8, because service healty is only support after 3.8

you can find out the docker-compose version with docker-compose -v

epigraphe commented 2 years ago

docker-compose version 1.25.0, build unknown

docker-compose-plugin is already the newest version (2.6.0~ubuntu-focal)

holema commented 2 years ago

The latest official docker-compose is 2.7.0 but ubuntu is not refreshing their repo so fast.

Can you try to set the version of the docker-compose.test.yml manually to 3.7 if this is working, I can revert the docker-compose version to 3.7

#docker-compose.test.yml
version: '3.7'

I just tested my internal installation with version 3.7 and it should work.

epigraphe commented 2 years ago

Changed to 3.7

ERROR: The Compose file './docker-compose.test.yml' is invalid because:
services.app-ja.depends_on contains an invalid type, it should be an array
services.keycloak-ja.depends_on contains an invalid type, it should be an array
holema commented 2 years ago

Which docker engine do you have installed? I use Docker version 20.10.14, build a224086

epigraphe commented 2 years ago

n# docker version Client: Docker Engine - Community Version: 20.10.17 API version: 1.41 Go version: go1.17.11 Git commit: 100c701 Built: Mon Jun 6 23:02:57 2022 OS/Arch: linux/amd64 Context: default Experimental: true

Server: Docker Engine - Community Engine: Version: 20.10.17 API version: 1.41 (minimum version 1.12) Go version: go1.17.11 Git commit: a89b842 Built: Mon Jun 6 23:01:03 2022 OS/Arch: linux/amd64 Experimental: false containerd: Version: 1.6.6 GitCommit: 10c12954828e7c7c9b6e0ea9b0c02b01407d3ae1 runc: Version: 1.1.2 GitCommit: v1.1.2-0-ga916309 docker-init: Version: 0.19.0 GitCommit: de40ad0

holema commented 2 years ago

The docker engine is correct. It must be >19.03.0

Could you install the latest docker-compose manually? This is the fastest way https://docs.docker.com/compose/install/compose-plugin/#install-the-plugin-manually I tested it with docker-compose 2.4 and 2.7 and then it is working.

epigraphe commented 2 years ago

Done, but have the same problems: v3.8

ERROR: Version in "./docker-compose.test.yml" is unsupported. You might be seeing this error because you're using the wrong Compose file version. Either specify a supported version (e.g "2.2" or "3.3") and place your service definitions under the `services` key, or omit the `version` key and place your service definitions at the root of the file to use version 1.
For more on the Compose file format versions, see https://docs.docker.com/compose/compose-file/

v.3.7

ERROR: The Compose file './docker-compose.test.yml' is invalid because:
services.app-ja.depends_on contains an invalid type, it should be an array
services.keycloak-ja.depends_on contains an invalid type, it should be an array
:/var/www/jitsi-admin# docker compose version
Docker Compose version v2.7.0
/var/www/jitsi-admin# docker-compose version
docker-compose version 1.25.0, build unknown
docker-py version: 4.1.0
CPython version: 3.8.10
OpenSSL version: OpenSSL 1.1.1f  31 Mar 2020
holema commented 2 years ago

I use in the bash script docker-compose. I haven`t installed it as a plugin.

with this you can directly download it into your bin directory. I did it this way.

curl -SL https://github.com/docker/compose/releases/download/v2.7.0/docker-compose-linux-x86_64 -o /usr/local/bin/docker-compose
chmod +x  /usr/local/bin/docker-compose
docker-compose -v
epigraphe commented 2 years ago

Finally it works Uninstalled docker-plugin and again trying with v3.8 Setup proccess was completed. Unfortunately, now when i try to open jitsi-admin and traefik in the browser, i get a 404 not found error and keycloak showing bad gateway. But I think this issue can be closed, because these are other problems. Thank you for your time. You are the greatest.

holema commented 2 years ago

It can take some minutes until the keycloak is up. sometimes when you are low on ram, the traefik is not registering the container. then try docker restart <traefik containerid>

can you send me the logs of the keycloak and the jitsi-admin?

you can get it with docker logs <containerid>

The development installation is quite instable, because there are so many dependencied and the conainers have to communicate which is not optimal without https. We only use this for the first prototyping.

So if you have any chance to install it with the prod environmant, then everything works much better. You just need a external domain or subdomain,

epigraphe commented 2 years ago

Basically, these were problems with my virtual machines. On your advice, I moved to the prod version. I don’t have a certificate yet, I need to forward port 80 for letsencrypt, I’ll add it a little later. keycloak works, lets me into the admin area. traefik also works, lets me into the dashboard I created a user in the keycloak admin panel and when I try to log in with his credentials I get an error 500.

https://vcs-adm.**********/login/keycloak_login/check?state=7a2610425343b0e88ce089c2c3f7a667&session_state=2bfa50b7-2e3d-472b-a6d0-0666b7cb0c54&code=934696ee-2b6f-426d-979a-b83242a4295a.2bfa50b7-2e3d-472b-a6d0-0666b7cb0c54.e0d7a685-a075-4834-a6ca-cb40d734f4af

I didn't see any errors in keycloak logs

https://pastebin.com/frmZpb5F

But there are errors in mariadb logs

2022-07-28 10:33:57 124 [Warning] Access denied for user 'root'@'localhost' (using password: NO)
2022-07-28 10:34:27 128 [Warning] Access denied for user 'root'@'localhost' (using password: NO)
2022-07-28 10:34:57 130 [Warning] Access denied for user 'root'@'localhost' (using password: NO)
2022-07-28 10:35:27 134 [Warning] Access denied for user 'root'@'localhost' (using password: NO)
2022-07-28 10:35:57 136 [Warning] Access denied for user 'root'@'localhost' (using password: NO)

I suppose this is due to the fact that I do not have a certificate yet?

h2Entwicklung commented 2 years ago

this happens, because the jitsi-admin wants to get the user information from the keycloak. This is plain OpenID-Connect. But this doesnt works, becaue you don`t have an valid certificate. So the 500 error is completly correct on the jitsi-admin side.