Kopano Meet with Kopano Web Daemon
-
Hi,
does anyone have some experience with the kopano-kwebd. I configured everything like the manuals, but there are still a few issues.
First one is, that the kwebd can not find the api for users:
Request URL: https://domain.de/api/gc/v1/users?$top=1&$skip=100&$select=id Request Method: GET Status Code: 403 Remote Address: 10.0.1.12:443 Referrer Policy: no-referrer
Second issue is, that the legacy_reveres_proxy isn’t doing anything. I changed the apache for webapp, z-push, and autodiscover back to http and switched the port to 8000, but the kwebd is still not delivering the pages.
Request URL: https://domain.de/webapp/ Request Method: GET Status Code: 404 Remote Address: 10.0.1.12:443 Referrer Policy: no-referrer
webapp is running under 10.0.1.12:8000 and works fine.
-
Hi @ansib ,
which version are you running at the moment?
While the 403 usually does not hint towards it, but is grapi actually running?
-
Hi @fbartels,
systemctl status grapi shows running. Is for grapi a .cfg file necessary?
● kopano-grapi.service - Kopano Groupware REST API Loaded: loaded (/lib/systemd/system/kopano-grapi.service; enabled; vendor preset: enabled) Active: active (running) since Do 2019-02-28 09:50:38 CET; 2s ago Process: 24207 ExecStartPre=/bin/chown -R kapi:kopano $socket_path (code=exited, status=0/SUCCESS) Process: 24202 ExecStartPre=/bin/mkdir $socket_path (code=exited, status=1/FAILURE) Main PID: 24212 (grapi master) Tasks: 11 Memory: 83.0M CPU: 1.940s CGroup: /system.slice/kopano-grapi.service ├─24212 grapi master ├─24220 grapi rest 0 ├─24221 grapi rest 1 ├─24222 grapi rest 2 ├─24223 grapi rest 3 ├─24224 grapi rest 4 ├─24225 grapi rest 5 ├─24226 grapi rest 6 ├─24227 grapi rest 7 └─24228 grapi notify Feb 28 09:50:39 domain kopano-grapi[24212]: INFO: 2019-02-28 09:50:39,264 - 24212 - starting kopano-mfr Feb 28 09:50:39 domain.de kopano-grapi[24212]: INFO: 2019-02-28 09:50:39,319 - 24228 - starting notify worker: unix:/var/run/kopano-grapi/notify.sock Feb 28 09:50:40 domain.de kopano-grapi[24212]: INFO: 2019-02-28 09:50:40,057 - 24220 - starting rest worker: unix:/var/run/kopano-grapi/rest0.sock Feb 28 09:50:40 domain.de kopano-grapi[24212]: INFO: 2019-02-28 09:50:40,068 - 24221 - starting rest worker: unix:/var/run/kopano-grapi/rest1.sock Feb 28 09:50:40 domain.de kopano-grapi[24212]: INFO: 2019-02-28 09:50:40,074 - 24222 - starting rest worker: unix:/var/run/kopano-grapi/rest2.sock Feb 28 09:50:40 domain.de kopano-grapi[24212]: INFO: 2019-02-28 09:50:40,078 - 24223 - starting rest worker: unix:/var/run/kopano-grapi/rest3.sock Feb 28 09:50:40 domain.de kopano-grapi[24212]: INFO: 2019-02-28 09:50:40,088 - 24224 - starting rest worker: unix:/var/run/kopano-grapi/rest4.sock Feb 28 09:50:40 domain.de kopano-grapi[24212]: INFO: 2019-02-28 09:50:40,091 - 24227 - starting rest worker: unix:/var/run/kopano-grapi/rest7.sock Feb 28 09:50:40 domain.de kopano-grapi[24212]: INFO: 2019-02-28 09:50:40,087 - 24225 - starting rest worker: unix:/var/run/kopano-grapi/rest5.sock Feb 28 09:50:40 domain.de kopano-grapi[24212]: INFO: 2019-02-28 09:50:40,094 - 24226 - starting rest worker: unix:/var/run/kopano-grapi/rest6.sock
Here are the versions:
kopano-backup/stable,now 8.7.0.0-0+1.1 amd64 [Installiert,automatisch] kopano-client/stable,now 8.7.0.0-0+1.1 amd64 [Installiert,automatisch] kopano-common/stable,now 8.7.0.0-0+1.1 amd64 [Installiert,automatisch] kopano-contacts/stable,now 8.7.0.0-0+1.1 amd64 [Installiert,automatisch] kopano-dagent/stable,now 8.7.0.0-0+1.1 amd64 [Installiert,automatisch] kopano-gateway/stable,now 8.7.0.0-0+1.1 amd64 [Installiert,automatisch] kopano-grapi/stable,now 8.7.0.0-0+1.1 amd64 [Installiert,automatisch] kopano-ical/stable,now 8.7.0.0-0+1.1 amd64 [Installiert,automatisch] kopano-kapid/stable,stable,now 0.9.0-0+1.1 amd64 [Installiert,automatisch] kopano-konnectd/stable,stable,now 0.18.0-0+2.1 amd64 [Installiert,automatisch] kopano-kwebd/stable,now 0.5.0-0+1.1 amd64 [Installiert,automatisch] kopano-kwmserverd/stable,now 0.14.0-0+1.1 amd64 [Installiert,automatisch] kopano-lang/stable,now 8.7.0.0-0+1.1 all [Installiert,automatisch] kopano-meet/stable,now 0.17.0-0+1.1 all [Installiert,automatisch] kopano-meet-packages/stable,now 0.17.0-0+1.1 all [installiert] kopano-meet-webapp/stable,now 0.17.0-0+1.1 all [Installiert,automatisch] kopano-monitor/stable,now 8.7.0.0-0+1.1 amd64 [Installiert,automatisch] kopano-python-utils/stable,now 8.7.0.0-0+1.1 amd64 [Installiert,automatisch] kopano-python3-extras/stable,now 0.0.6+0-0+36.1 amd64 [Installiert,automatisch] kopano-search/stable,now 8.7.0.0-0+1.1 amd64 [Installiert,automatisch] kopano-server/stable,now 8.7.0.0-0+1.1 amd64 [Installiert,automatisch] kopano-server-packages/stable,now 8.7.0.0-0+1.1 all [installiert] kopano-spooler/stable,now 8.7.0.0-0+1.1 amd64 [Installiert,automatisch] kopano-utils/stable,now 8.7.0.0-0+1.1 amd64 [Installiert,automatisch] kopano-webapp/stable,now 3.5.2.2146+87.1 all [installiert] kopano-webapp-plugin-files/stable,now 2.1.5.305+93.1 all [installiert] kopano-webapp-plugin-mattermost/stable,now 0.1+21.1 all [installiert] kopano-webapp-plugin-mdm/stable,now 2.1.0.97+29.3 all [installiert] kopano-webapp-plugin-smime/stable,now 2.2.1.223+22.1 all [installiert] libgsoap-kopano-2.8.74/stable,now 2.8.74-0+1.1 amd64 [Installiert,automatisch] libvmime-kopano1/stable,now 0.9.2.50+12.1 amd64 [Installiert,automatisch] php-kopano-smime/stable,now 1.0.00+3.1 amd64 [Installiert,automatisch] python3-kopano/stable,now 8.7.0.0-0+1.1 all [Installiert,automatisch] python3-kopano-rest/stable,now 8.7.0.0-0+1.1 all [Installiert,automatisch] python3-kopano-search/stable,now 8.7.0.0-0+1.1 all [Installiert,automatisch] python3-kopano-utils/stable,now 8.7.0.0-0+1.1 all [Installiert,automatisch] z-push-backend-kopano/stable,now 2.4.5+0-0 all [installiert] z-push-kopano/stable,now 2.4.5+0-0 all [installiert] z-push-kopano-gabsync/stable,now 2.4.5+0-0 all [installiert]
Thanks
-
@ansib said in Kopano Meet with Kopano Web Daemon:
Hi,
does anyone have some experience with the kopano-kwebd. I configured everything like the manuals, but there are still a few issues.
First one is, that the kwebd can not find the api for users:
This shows status code 403. It means that kapi did not grant access via access token. Assume you have set up Konnect and can sign in just fine there, the most likely reason is that your Kopano Groupware Server was not configured to validate access tokens. Check the KCOIDC configuration settings in server.cfg and also make sure to have SSO. The server will also log authentication errors or other erros related to OIDC if running at least with info log level.
Second issue is, that the legacy_reveres_proxy isn’t doing anything. I changed the apache for webapp, z-push, and autodiscover back to http and switched the port to 8000, but the kwebd is still not delivering the pages.
webapp is running under 10.0.1.12:8000 and works fine.
It seems that the parameter to enable the reverse proxy is not passed properly from the kwebd.cfg to the service. So assuming you have set
legacy_reverse_proxy
it has no effect. Will be fixed in the next version - thanks for complaining :). In the meanwhile you can grab the fixed binscript https://stash.kopano.io/projects/KGOL/repos/kweb/commits/1a6298af54b0241c264abb37cd0f210cc66b0623 (replace /usr/sbin/kopano-kwebd).Thanks for reporting!
-
@longsleep said in Kopano Meet with Kopano Web Daemon:
It seems that the parameter to enable the reverse proxy is not passed properly from the kwebd.cfg to the service. So assuming you have set legacy_reverse_proxy it has no effect. Will be fixed in the next version - thanks for complaining :). In the meanwhile you can grab the fixed binscript https://stash.kopano.io/projects/KGOL/repos/kweb/commits/1a6298af54b0241c264abb37cd0f210cc66b0623 (replace /usr/sbin/kopano-kwebd).
Thanks for reporting!Works! You are welcome and thank you for the fast fix!
@longsleep said in Kopano Meet with Kopano Web Daemon:
This shows status code 403. It means that kapi did not grant access via access token. Assume you have set up Konnect and can sign in just fine there, the most likely reason is that your Kopano Groupware Server was not configured to validate access tokens. Check the KCOIDC configuration settings in server.cfg and also make sure to have SSO. The server will also log authentication errors or other erros related to OIDC if running at least with info log level.
You are right. I changed konnectd to authentication with ldap, which does not seem to work correctly. I switched back to KC and added the needed informations from here
https://documentation.kopano.io/kopanocore_administrator_manual/configure_kc_components.html#id2and it works now perfectly.
Another question:
The button in the top right corner with the nine squares has links to kopano mail, calender and contacts, but these three apps does not exists, is that right or i am missing a few packages? Does these three apps replace the not mobile ready webapp?
-
@ansib said in Kopano Meet with Kopano Web Daemon:
I changed konnectd to authentication with ldap, which does not seem to work correctly.
Yes, indeed at this moment (definitely for the packages in the “final” repo) Meet only really works with everything set to the Kopano backend. The goal for Meet (and the other apps you have spotted) is that they will in the future also work with other backends.
@ansib said in Kopano Meet with Kopano Web Daemon:
Does these three apps replace the not mobile ready webapp?
yes, eventually these app will replace the current WebApp in general. These apps are not yet public, since they just exist as simple proof of concepts. But we are making good progress on them. Have a look at https://www.youtube.com/watch?v=sz2iDNHu9JI to get some impressions how these apps will look in the future.