Recording URL unreachable!
See original GitHub issueHello,
We have installed the script as documented and tried to run it for our recordings but we are receiving the following error. We can access the URL manually so it should be correct.
~/bbb-recorder$ node export.js "https://<REMOVED>/playback/presentation/2.0/playback.html?meetingId=<REMOVED>" presentation.mp4 0 true
Recording URL unreachable!
We are using debian 10 with nodejs version v14.11.0
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Url for this recording format is unreachable - Google Groups
When I navigate to the meeting url, I am able to play the meeting. So it seems like although the link has been...
Read more >Why is my application or website hosted on Route 53 ...
1. Use the following command to check if the record value returned from the DNS resolver matches the value returned from the authoritative...
Read more >Unreachable Statement in url - Stack Overflow
When I enter the database url, I got error Unreachable Statement String url= "http://www.example.com/php.php";. This is my code:
Read more >Site is not reachable without www after DNS record edit
So I decided to get rid of the WP redirects and change DNS records to make WWW by default so WP doesn't have...
Read more >The URL is not reachable!
The URL is not reachable! To my (limited) understanding the domain is a FQDN. I think all the A and MX records are...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Hello, it looks like we had some problems with the proxy on google chrome regarding the SSL certificate.
As a workaround, we have added the chrome parameter in the export.js file on line 31 after that it worked:
'--ignore-certificate-errors',I used to get the same issue on my local/development machine, but on a production server everything was fine, and I blamed the internet connection. So make sure your proxy is configured properly on the machine facing the error. A good way to see what is happening inside the browser instance is to make screenshots using Puppeteer API at different stages and verify that everything is working ok. It’s like:
Another way to debug is to change the line: https://github.com/jibon57/bbb-recorder/blob/126e31d2103144c2473e559dfa5a61d54848733a/export.js#L96
to this (Be aware of
networkidle0):