-
-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't Open play Recording after transferring to S3 #6
Comments
Can you send me the original url of your deployed instance, so that I can take a look using console, maybe I can fine something useful. I am not using BBB since last few months, so it may happen because of new version but I am not sure. |
Thanks for reply, here is the original link |
I'm not sure if you are using the correct URL or if this is a new update from BBB because as I can use you are using 2.3 but still most of the universities are using 2.0 playback, usually the structure for playback urls is like this https://davy04.edunova.it/playback/presentation/2.0/playback.html?meetingId=905adca18d4eea6b84892915345c1c604dc29152-1615295466889 (I found this randomly) So, can you send me the screenshot of your writing.js file (Send me 2 screenshots, 1 before editing and 2nd after editing) If nothing works, maybe i need to install BBB myself and figure this out. |
@rohitcoder actually there are some changes in URL since the 2.3 update and it doesn't have the same files and playback logic as 2.2. If you can see below there is no lib/writing.js in 2.3 directory and 2.0 directory is also not located in Screenshot of 2.3 directoryScreenshot of
|
You need to verify 2 things here.
After these all things get fixed, we can see what happens next. |
Hi, @rohitcoder I have an issue playing the recording after transferring to S3 and keeping metadata.xml on the local server. while its getrecording API call is working fine but can't play it using the https://server.com/playback/presentation/2.3/meetingId.
when I try to play a recording it returns a 404 error.
please help to figure out what is the issue.
some additional information:
The text was updated successfully, but these errors were encountered: