webrtc-as-rtmp-re-publishing-not-working

Max

Administrator
Staff member
when we use https://wcs:8443/rest-api/push/startup we get following error message "SSL certificate problem: unable to get local issuer certificate", Although we have already imported SSL from webcall server admin dashboard. Can you please let us know what's the issue
This message can be displayed by browser in two cases:
1. You are using self-signed certificate.
2. You are using Certificate Authority which is not trusted by the browser.
So please do the following:
1. Check if you have succesfully imported the certificate using WCS dashboard. Is dashboard itself marked by browser as secure when opening via HTTPS https://wcs:8444/admin/? If not, and you have imported certificate successfully, please check if it is a wildcard certificate *.yourdomain.com. If not, you're probably opening the page with a different servers name (for example, you have certificate for wcs.yourdomain.com, but opening as staging.yourdomain.com.
2. Check if browser displays connection as secure
1658193412216.png

If not, and you are using a right name to open, and certificate is not self-signed, check if browser claims for CA in certificate details
1658193777878.png

If something wrong with the CA (is not trusted), please ask the certificate issuer about the problem.
 

Max

Administrator
Staff member
Sometimes during webcam streaming our stream not play good on Facebook like please check below screenshot
This is definitely the publisher channell quality issue. Please use TCP transport when publishing WebRTC stream from webcam
Code:
session.createStream({
    name: streamName,
    display: localVideo,
    constraints: {
        ...
    },
    transport: "TCP"
    ...
}).publish();
If this does not help, use a lower resolution and bitrate for publishing
Code:
session.createStream({
    name: streamName,
    display: localVideo,
    constraints: {
        video: {
            width: 640,
            height: 360,
            maxBitrate: 500
        },
        audio: true
    },
    transport: "TCP"
    ...
}).publish();
 
Hi @Max

We have noticed flashphoner server takes too much of cpu usage even though we have not published any stream and when we publish stream then its take more cpu due to which our other services stop responding and sometimes flashponer server itself stop responding too.

1658325232770.png


Thanks,
Faraz
 

Max

Administrator
Staff member
and further can we set it on auto update whenever new version available?
No. You can only check for updates manually
Code:
sudo /usr/local/FlashphonerWebCallServer/bin check_update
and update if needed
Code:
sudo /usr/local/FlashphonerWebCallServer/bin update
But it is not recommended to update server in production unless it's not working as expected.
 

Max

Administrator
Staff member
Sorry, it's a mistype.
Should be
Code:
sudo /usr/local/FlashphonerWebCallServer/bin/webcallserver check_update
and
Code:
sudo /usr/local/FlashphonerWebCallServer/bin/webcallserver update
respectively. Please see the doc here.
 
Top