![]() ![]() |prosody_1 | runnervx_ZCRGf debug|changed state from waiting to ready| |prosody_1 | mod_bosh debug|Request destroyed: table: 0x55f7835544b0| |prosody_1 | mod_bosh debug|We have an open request, so sending on that| |prosody_1 | meet.jitsi:saslauth debug|sasl reply: could not obtain public key| |prosody_1 | general warn|Error verifying token err:not-allowed, reason:could not obtain public key| ![]() |prosody_1 | net.connect debug| No more connection targets to try| |prosody_1 | net.connect debug| Connection attempt failed: closed| |prosody_1 | server_epoll debug|TLS handshake on FD 15 (192.168.48.3, 37324) to wait until readable| |prosody_1 | adns debug|Reply for evacloud.io (thread: 0x55f7835d5c00)| |prosody_1 | adns debug|Reply for evacloud.io (thread: 0x55f783264e30)| |prosody_1 | mod_bosh debug|Have nothing to say, so leaving request unanswered for now| |prosody_1 | mod_bosh debug|and there are 0 things in the send_buffer:| |prosody_1 | runnervx_ZCRGf debug|changed state from ready to waiting| |prosody_1 | adns debug|Records for evacloud.io not in cache, sending query (thread: 0x55f783264e30).| |prosody_1 | adns debug|Sending DNS query to 127.0.0.11| |prosody_1 | adns debug|Records for evacloud.io not in cache, sending query (thread: 0x55f7835d5c00).| |prosody_1 | net.connect debug| Checking for targets.| |prosody_1 | meet.jitsi:auth_token debug|Fetching public key from: |prosody_1 | http debug|Making HTTPS GET request '55f7835ea880' to |prosody_1 | net.connect debug| Starting connection process| |prosody_1 | meet.jitsi:auth_token debug|Cache miss for key: HZ圜HLJzbP97PpaEhh5r0qDWOQWle7gDtHk2wR-4K6o| MIIBCgKCAQEAtjEX+kvOIyWFouO2X7avsurz+/9srEg47U/Jtq5iAGeSl7wldtOBVp2gPOoe89KRRHz4wfvy470km9kr7+EEbTMgKnNoHN1oIyZMelxQoDSw7xmpfymSE//svfd72Jrw37jweM+KXGmtMp4h3BI2oZEHrw+cNVvy1fAGmjbolBQRtQFQvS2aIfAbQyYHaI4of+qNc8cRf4N311F5vZieuYrjCdd3R65r+SpJPyKaiIaPy+zXHEIznfXWrB5U/BGKWODFvZLHgnmy6/7OcmgbC01F1tSm+/r+/uc9m+BtNdu0GhU2hfCSURwa26+Ty/vwW80Y9Mm6bt/ajq6TAC/R0QIDAQABĭo we need to send any response headers or does the response need to in any special format?įull stack trace |prosody_1 | runnervx_ZCRGf debug|creating new coroutine| ![]() Hi I have tried the same thing but I am getting an error saying Error verifying token err:not-allowed, reason:could not obtain public key curl -i HTTP/2 200Įtag: W/"168-ZXCAFNhQfw4pHo5DeWiebJIOwaw" How to fix the promblem Authentication failed? Prosody trunk nightly build 1222 (, a9c975a0f113) Key = “/var/lib/prosody/” Ĭertificate = “/var/lib/prosody/” Ĭonference_duration_component = “conference_”Ĭomponent “ ” “muc” – Note that old-style SSL on port 5223 only supports one certificate, and will always – Assign this host a certificate for TLS, otherwise it would use the one – and authentication above is switched to “token” – Properties below are modified by jitsi-meet-tokens package config – enabled = false – Remove this line to enable this hostĪpp_id = “xxxx” – application identifierĪpp_secret = “xxxx” – application secret known only to your token If user doesn’t use JWT to create room, will be appear login Anyone can help me to solve my problem? I want to config jitsi with JWT token to create or join room. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |