Manual Installation on Oracle Linux


We are trying to set up jitsi web server natively on Oracle Linux 8 without docker. I was able to follow this guide Jitsi Manual Installation and go through the installation and build all the components aside from requiring newer versions of some of the packages. But when I try to start a conference, I get a 502 Error http-bind BOSH connection failed in the console. I have tried some of the solutions mentioned in the forum including setting an appropriate timeout in Nginx config and enabling websockets but I still get a 502 error with websocket connection which makes me believe It’s a prosody issue. I have provided the appropriate config and log files.

Prosody Log:
prosody.log (12.1 KB)

Prosody config:

cross_domain_websocket = true;
consider_websocket_secure = true;

VirtualHost ""
    authentication = "anonymous"
    ssl = {
        key = "/var/lib/prosody/";
        certificate = "/var/lib/prosody/";
    modules_enabled = {
    smacks_max_unacked_stanzas = 5;
    smacks_hibernation_time = 60;
    smacks_max_hibernated_sessions = 1;
    smacks_max_old_sessions = 1;
    c2s_require_encryption = false

VirtualHost ""
    ssl = {
        key = "/var/lib/prosody/";
        certificate = "/var/lib/prosody/";
    authentication = "internal_hashed"

admins = { "" }

Component "" "muc"
Component ""
    component_secret = "secret1"
Component ""
    component_secret = "secret2"

Nginx config:

server_names_hash_bucket_size 64;

server {
    listen       443 ssl http2;
    listen       [::]:443 ssl http2;
    # tls configuration that is not covered in this guide
    # we recommend the use of
    # set the root
    root /srv/jitsi-meet;
    index index.html;

    ssl_certificate "/etc/pki/nginx/server.crt";
    ssl_certificate_key "/etc/pki/nginx/private/server.key";
    #ssl_session_cache shared:SSL:1m;
    #ssl_session_timeout  10m;
    #ssl_ciphers PROFILE=SYSTEM;
    #ssl_prefer_server_ciphers on;
    location ~ ^/([a-zA-Z0-9=\?]+)$ {
        rewrite ^/(.*)$ / break;
    location / {
        ssi on;

    location = /xmpp-websocket
        proxy_pass http://localhost:5280/xmpp-websocket;

        #shard & region that matches config.deploymentInfo.shard/region -  See [note 1] below
        add_header 'x-jitsi-shard' 'shard';
        add_header 'x-jitsi-region' 'us-east-2a';
        add_header 'Access-Control-Expose-Headers' 'X-Jitsi-Shard, X-Jitsi-Region';

        proxy_set_header X-Forwarded-For $remote_addr;
        proxy_set_header Host $http_host;

        proxy_http_version 1.1;
        proxy_buffer_size 128k;
        proxy_buffers 4 256k;
        proxy_busy_buffers_size  256k;
        proxy_set_header Connection "upgrade";
        tcp_nodelay on;
    # BOSH, Bidirectional-streams Over Synchronous HTTP
    location /http-bind {
        proxy_pass      http://localhost:5280/http-bind;
        proxy_set_header X-Forwarded-For $remote_addr;
        proxy_set_header Host $http_host;
	proxy_read_timeout 1800;
    # external_api.js must be accessible from the root of the
    # installation for the electron version of Jitsi Meet to work
    location /external_api.js {
        alias /srv/jitsi-meet/libs/external_api.min.js;


var config = {
    // Connection

    hosts: {
        // XMPP domain.
        domain: '',

        // When using authentication, domain for guest users.
        // anonymousdomain: '',

        // Domain for authenticated users. Defaults to <domain>.
        // authdomain: '',

        // Focus component domain. Defaults to focus.<domain>.
        focus: '',

        // XMPP MUC domain. FIXME: use XEP-0030 to discover it.
        muc: ''

    // BOSH URL. FIXME: use XEP-0156 to discover it.
    bosh: '//',

    // Websocket URL
    websocket: 'wss://',

    // The real JID of focus participant - can be overridden here
    // Do not change username - FIXME: Make focus username configurable
    // focusUserJid: '',


Please let me know if you need anything else and I greatly appreciate your assistance.

What happens when you visit the bosh URL directly?

Thank you for your response @saghul

So when I visit I get the following page

Hum is the proxying working ok for other routes? Is prosody up and listening on localhost?

Prosody seems to be up, not sure how to check if it is listening on localhost

Proxying seems to work when I visit

Check with netstat -tunapl what interfaces Prosody is listening on.