Using (beta.)meet.jit.si with low-level API

Hello.

I’m developing web app based on Jitsi. At least for development, I would prefer to use this global instances of Jitsi and for various reasons, I need to use low level API.

I made some progress and it has been working, hovewer, I didn’t touch the project since last Tuesday and tried it today - and it does not work more due to CORS limitations.

So, I would like to ask two questions:

  1. Does something changed or I’ve just broke something?
  2. Can I use global jitsi instance for this purpose?

Thanks,
S.

No one knows? :frowning:

I am also struggling with CORS to use lib-jitsi-meet.
I put in a proxy (http-proxy-middleware) but still get CORS issues even seeing the connection (localhost/http-bind) redirected to my test server.

Is there an example proxy setup that works for lib-jitsi-meet? the setup in jitsi-meet seems excessively complex to replicate.

Sukovec,

I’m very interested in the progress you’ve made. I’m looking to create headless audio conferences using lib-jitsi-meet with my hosted Jitsi server. Are you willing to share what you’ve done?

Hello. I cannot send you anything as it is basically little bit “filtered” jitsi example

1 Like

I managed to get the connections by adding
add_header ‘Access-Control-Allow-Origin’ ‘’;
add_header ‘Access-Control-Allow-Headers’ '
’;
to the NGINX setup on the server

BOSH

    location = /http-bind {
     add_header 'Access-Control-Allow-Origin' '*';
     add_header 'Access-Control-Allow-Headers' '*';
        proxy_pass      http://localhost:5280/http-bind;
        proxy_set_header X-Forwarded-For $remote_addr;
        proxy_set_header Host $http_host;
    }