Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. MiroTalk
  3. Enabling the MiroTalk meetings API (success!)

Enabling the MiroTalk meetings API (success!)

Scheduled Pinned Locked Moved MiroTalk
guides
1 Posts 1 Posters 15 Views 1 Watching
  • 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.
  • canadaduaneC Offline
    canadaduaneC Offline
    canadaduane
    App Dev
    wrote last edited by canadaduane
    #1

    In case this is useful to anyone else:

    I wanted to gain access to the full meetings and token APIs at my-server.com/api/v1/docs/:

    9f0b4e5d-b62e-4a55-be88-9b62a224918c-image.png

    Since I was able to access the page above, it looked at first like everything was already set and ready to go!

    However, I soon learned that this was not the case:

    {"error":"This endpoint has been disabled. Please contact the administrator for further information."}

    This made me think that I needed to use the secret in /app/data/api_secret to access the API. But it didn't work (same error message as above).

    It turns out I needed to add the following to the /app/data/env file:

    API_ALLOW_MEETINGS=true
    API_ALLOW_TOKEN=true

    Once I restarted the server, I was rewarded with a new error!

    {"error":"Unauthorized!"}

    This unauthorized error shows up because, I believe, the /app/data/api_secret is not used for the meetings or token APIs. You need to ALSO add the following to your /app/data/env file:

    API_KEY_SECRET=yourVerySpecialSecret

    Finally, you can click the Authorize button in the swagger / MiroTalk SFU API page (shown above), and add yourVerySpecialSecret to the input box there. After that, you have access to your own MiroTalk SFU API!

    Update to add: You can find a complete list of possible env settings here:

    https://github.com/miroslavpejic85/mirotalksfu/blob/main/.env.template

    1 Reply Last reply
    4
    Reply
    • Reply as topic
    Log in to reply
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes


    • Login

    • Don't have an account? Register

    • Login or register to search.
    • First post
      Last post
    0
    • Categories
    • Recent
    • Tags
    • Popular
    • Bookmarks
    • Search