Navigation

    Kopano
    • Register
    • Login
    • Search
    • Categories
    • Get Official Kopano Support
    • Recent
    Statement regarding the closure of the Kopano community forum and the end of the community edition

    Can't get login to Meet: No Access

    Kopano Meet & WebMeetings
    3
    26
    1274
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • mniehren
      mniehren last edited by mniehren

      maybe 1 last problem left.

      I try to configure guest support in meet according to the description in
      “Special configuration”

      Everything works until i create an config.json file. If i call the Meet-Link in the browser,
      i only see “prepare (Vorbereiten)” and nothing more happens.

      First i copy from config.json.in:

      {
        "apiPrefix": "/api/gc/v1",
        "oidc": {
          "iss": "",
          "clientID": ""
        },
        "kwm": {
          "url": ""
        },
        "guests": {
                "enabled": true,
                "default": null
        },
        "disableFullGAB": false
      }
      

      But i don’t know, what other value has to be there (iss is clear).

      so i tried only

      {
        "guests": {
          "enabled": "true"
        }
      }
      

      same result, even if i put an empty config.json nothing is changed.

      As soon as i delete the file, the login prompt arrives.

      I put the file under /usr/share/kopano-meet/config/kopano/meet.json as my
      web_root in kwebd is /usr/share/kopano-meet. Is that right ?

      Again, nothing in the logs.

      Could you help ?

      best regards
      Michael

      1 Reply Last reply Reply Quote 0
      • mniehren
        mniehren last edited by

        i see in the request-log of kwebd the following:

        192.168.70.10 - - [07/May/2020:08:52:25 +0200] "GET /api/config/v1/kopano/meet/config.json HTTP/2.0" 200 158 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/81.0.4044.114 Safari/537.36"
        192.168.70.10 - - [07/May/2020:08:52:26 +0200] "GET /api/config/v1/kopano/meet/config.json HTTP/2.0" 200 158 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/81.0.4044.114 Safari/537.36"
        192.168.70.10 - - [07/May/2020:08:52:28 +0200] "GET /api/config/v1/kopano/meet/config.json HTTP/2.0" 200 158 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/81.0.4044.114 Safari/537.36"
        192.168.70.10 - - [07/May/2020:08:52:31 +0200] "GET /api/config/v1/kopano/meet/config.json HTTP/2.0" 200 158 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/81.0.4044.114 Safari/537.36"
        192.168.70.10 - - [07/May/2020:08:52:36 +0200] "GET /api/config/v1/kopano/meet/config.json HTTP/2.0" 200 158 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/81.0.4044.114 Safari/537.36"
        192.168.70.10 - - [07/May/2020:08:52:41 +0200] "GET /api/config/v1/kopano/meet/config.json HTTP/2.0" 200 158 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/81.0.4044.114 Safari/537.36"
        192.168.70.10 - - [07/May/2020:08:52:46 +0200] "GET /api/config/v1/kopano/meet/config.json HTTP/2.0" 200 158 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/81.0.4044.114 Safari/537.36"
        192.168.70.10 - - [07/May/2020:08:52:51 +0200] "GET /api/config/v1/kopano/meet/config.json HTTP/2.0" 200 158 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/81.0.4044.114 Safari/537.36"
        192.168.70.111 - - [07/May/2020:08:52:53 +0200] "GET /.well-known/openid-configuration HTTP/1.1" 200 524 "-" "Go-http-client/1.1"
        192.168.70.111 - - [07/May/2020:08:52:53 +0200] "GET /konnect/v1/jwks.json HTTP/1.1" 200 410 "-" "Go-http-client/1.1"
        192.168.70.10 - - [07/May/2020:08:52:56 +0200] "GET /api/config/v1/kopano/meet/config.json HTTP/2.0" 200 158 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/81.0.4044.114 Safari/537.36"
        192.168.70.10 - - [07/May/2020:08:53:01 +0200] "GET /api/config/v1/kopano/meet/config.json HTTP/2.0" 200 158 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/81.0.4044.114 Safari/537.36"
        192.168.70.10 - - [07/May/2020:08:53:06 +0200] "GET /api/config/v1/kopano/meet/config.json HTTP/2.0" 200 158 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/81.0.4044.114 Safari/537.36"
        
        
        1 Reply Last reply Reply Quote 0
        • fbartels
          fbartels Kopano last edited by

          Hi @mniehren,

          did you have a look at the example deployment I’ve linked to above?

          The document you have pasted here looks ok and also parses as valid json. It would be interesting to know what your browser reports (in the network console) when loading it. are there any others errors in there?

          This is the config we are using for the public service: https://use.meet-app.io/api/config/v1/kopano/meet/config.json

          Regards Felix

          Resources:
          https://kopano.com/blog/how-to-get-kopano/
          https://documentation.kopano.io/
          https://kb.kopano.io/

          Support overview:
          https://kopano.com/support/

          1 Reply Last reply Reply Quote 0
          • mniehren
            mniehren last edited by mniehren

            in the Web-Console of Firefox i see

            Strict-Transport-Security: The connection to the site is untrustworthy, so the specified header was ignored.  config.json
            failed to fetch config: Error: unexpected Content-Type, retrying in 5000ms actions.js:111:22
            Strict-Transport-Security: The connection to the site is untrustworthy, so the specified header was ignored.  config.json
            failed to fetch config: Error: unexpected Content-Type, retrying in 5000ms actions.js:111:22
            

            Network show’s only

            	config.json	fetch	plain	636 B	237 B	2 ms  200	GET kopano2.tuxlan.de
            	config.json	fetch	plain	636 B	237 B	8 ms200 	GET kopano2.tuxlan.de
            	config.json	fetch	plain	636 B	237 B	2 ms
            

            and so on

            nothing else

            I tried it with Firefox under Linux and Win7 and with Vivaldi unter Linux

            fbartels 1 Reply Last reply Reply Quote 0
            • mniehren
              mniehren last edited by

              here are some screenshots from the vivaldi console …vivaldi1.png
              vivaldi2.png vivaldi3.png vivaldi4.png

              1 Reply Last reply Reply Quote 0
              • fbartels
                fbartels Kopano @mniehren last edited by fbartels

                @mniehren said in Can't get login to Meet: No Access:

                The connection to the site is untrustworthy

                Why is the connection untrustworthy?

                @mniehren said in Can't get login to Meet: No Access:

                failed to fetch config: Error: unexpected Content-Typ

                The kweb package has a dependency on the mailcap package. this package provides identification for the various mime types. you seem be be missing this.

                PS: your screenshots are tiny and not really readable. but copy pasting error messages from screenshots is a pain anyways. https://birdeatsbug.com/ produces a nice browser extension to more easily debug web applications. for one it offers the ability to record what is exactly going on on the screen.

                Regards Felix

                Resources:
                https://kopano.com/blog/how-to-get-kopano/
                https://documentation.kopano.io/
                https://kb.kopano.io/

                Support overview:
                https://kopano.com/support/

                longsleep 1 Reply Last reply Reply Quote 0
                • longsleep
                  longsleep Kopano @fbartels last edited by

                  @fbartels said in Can't get login to Meet: No Access:

                  The kweb package has a dependency on the mailcap package. this package provides identification for the various mime types. you seem be be missing this.

                  Technically kweb serves static file content type by looking at the extension and then resolving a mime type by looking at the /etc/mime.types file. So make sure that file exists and includes json.

                  cat /etc/mime.types|grep json
                  application/json                                json
                  

                  On Debian and its derivates this can for example be achieved by installing the mime-support package.

                  1 Reply Last reply Reply Quote 0
                  • mniehren
                    mniehren last edited by

                    Great, now i got an login again.

                    thanks for you help
                    Michael

                    1 Reply Last reply Reply Quote 0
                    • mniehren
                      mniehren last edited by mniehren

                      Hi, me again,

                      now it run’s nearly. I try to configure public guest account according the documentation.

                      I can create public rooms, but when i try to come in as a guest into the the room, i got an
                      “Failed to create guest session”

                      In the console log, i see the following error:
                      index.js:8 ResponseValidator._validateIdToken: No key matching kid or alg found in signing keys

                      could you please help once again with this problem ?

                      best regards
                      Michael

                      1 Reply Last reply Reply Quote 0
                      • mniehren
                        mniehren last edited by

                        found it, forget to generate the encryption secret key

                        mniehren 1 Reply Last reply Reply Quote 0
                        • mniehren
                          mniehren @mniehren last edited by

                          This post is deleted!
                          1 Reply Last reply Reply Quote 0
                          • mniehren
                            mniehren last edited by

                            not at all, i now got the following error in the browser console:
                            kwm.js:4709 Uncaught TypeError: Cannot read property ‘onconnectionstatechange’ of undefined
                            at t.getPeerConnection (kwm.js:4709)
                            at t.handleWebRTCMessage (kwm.js:4974)
                            at e.handleWebSocketMessage (kwm.js:5532)

                            The same error occurs if i do an call between 2 regular Kopano-Users.

                            The turnserver-Log show’s no connection

                            best regards
                            Michael

                            mniehren 1 Reply Last reply Reply Quote 0
                            • mniehren
                              mniehren @mniehren last edited by

                              that seems to be an issue with the vivaldi Browser,

                              I got an successfully connect from another internal Windows machine with Firefox.

                              Then i also see entries in the turnserver log

                              1 Reply Last reply Reply Quote 0
                              • fbartels
                                fbartels Kopano last edited by fbartels

                                Hi @mniehren,

                                thanks for the feedback regarding Vivaldi. On first look it seems it does not support all features of WebRTC that Meet requires. I have put on my list to test his locally as well.

                                Edit: just gave this a quick try with the default installation of Vivaldi against our internal system and I was able to make a call.

                                Regards Felix

                                Resources:
                                https://kopano.com/blog/how-to-get-kopano/
                                https://documentation.kopano.io/
                                https://kb.kopano.io/

                                Support overview:
                                https://kopano.com/support/

                                1 Reply Last reply Reply Quote 0
                                • First post
                                  Last post