Skip to content
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

Open
hamza3055 opened this issue Aug 11, 2021 · 6 comments
Open

Can't Open play Recording after transferring to S3 #6

hamza3055 opened this issue Aug 11, 2021 · 6 comments

Comments

@hamza3055
Copy link

hamza3055 commented Aug 11, 2021

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.
image
please help to figure out what is the issue.
some additional information:

  • BBB version is 2.3
  • I have checked my writing.js and the URL is fine
  • Bucket is public and files are accessible through URL
  • I have followed all instructions of the closed issue Playing recordings from S3 #2.
@rohitcoder
Copy link
Owner

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.

@hamza3055
Copy link
Author

@rohitcoder
Copy link
Owner

@hamza3055

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.

@hamza3055
Copy link
Author

hamza3055 commented Aug 11, 2021

@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 /var/bigbluebutton/playback/presentation/ instead it is in /var/bigbluebutton/playback/presentation/0.9.0.

Screenshot of 2.3 directory

image

Screenshot of /var/bigbluebutton/playback/presentation/ directory

image

So I edited the writing.js file of 0.9.0/2.0/lib/writing.js as was mentioned in your guide.
here are the screenshots of the file before and after editing

before

image

after

image

there is only one change that I inserted the s3 Url in it and if you want then I can share the whole 2.3 directory so that you can see the playback logic.
Here is the URL of recording that is currently on local server its working fine.
https://topit.live/playback/presentation/2.3/a72b20062ec2c47ab2ceb97ac1bee818f8b6c6cb-1628592543516

@rohitcoder
Copy link
Owner

https://topit.live/playback/presentation/2.3/a72b20062ec2c47ab2ceb97ac1bee818f8b6c6cb-1628585318179
I checked again your previous supplied URL and i noticed it's not fetching meta files from s3 server it's still sending requests to your own server.

image

You need to verify 2 things here.

  1. You are sure files are getting uploaded to your s3 bucket and it's public? You can check this by visiting this URL https://topitdata.s3.us-east-2.amazonaws.com/MEETING_ID_HERE/presentation_text.json
  2. If the above s3 URL is opening properly now move to the next step, and see if the playback tool is sending requests to s3 or your own server, some times playback still sends requests to your own server because of caching issues, be sure to purge cache if using Cloudflare and then clear browser cache.

After these all things get fixed, we can see what happens next.

@hamza3055
Copy link
Author

hamza3055 commented Aug 14, 2021

Thank you for your response.
I followed the steps and here what I found:

  • the bucket is public and files are uploading
    image

  • S3 URL is working properly
    image

  • I cleared all the server cache and browser cache and it still gives an error 404.

I am new to BBB so I don't know how to check the request status of BBB

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants