-
Notifications
You must be signed in to change notification settings - Fork 13
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
[BUG] S3 Cloud recording #90
Comments
@BrainRift Cloud recording could be failing for a number of reasons. To ensure you are properly set up on the Agora side, did you set up cloud recording on your Agora Project (as outlined in this guide)? |
@BrainRift just checking to see if the guide helped resolve your issue or are you still facing this issue? |
I also encountered this problem. I set up aliyun OSS, and other functions were normal. Only when I clicked to record, the same error message as BrainRift appeared @digitallysavvy |
PHP Fatal error: Uncaught ArgumentCountError: Too few arguments to function WP_Agora_Public::generateNewToken(), 2 passed in /www/wwwroot/wp-content/plugins/wp-agora-io/includes/class-wp-agora-cloud-recording.php on line 186 and exactly 3 expected in /www/wwwroot/wp-content/plugins/wp-agora-io/public/class-wp-agora-io-public.php:122 |
What value are you passing for the bucket name? If you are using S3, the ARN is listed as |
Hi @digitallysavvy - I am facing the same issue and I get the same error "There has been a critical error on your website". I followed the guide you provided in an earlier reply and enabled recording for the Agora project. I created an S3 bucket, blocked all public access, created an IAM user with all S3 access rights, and used that user's access + secret key for the recording. The S3 bucket is in US East Coast 2. For the Bucket name, I am not providing As a quick test, I set up a new, dummy installation of WordPress and the same error occurs there as well. I am using DigitalOcean btw and all other functionalities with WordPress and Agora work fine. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed because it was marked as stale and did not have any activity since. Thank you for your contributions. |
After ensuring the proper S3 credentials and bucket write, I am unable to record a session. I receive an error, but after turning debugging in Wordpress, the error is never displayed or logged....
Desktop (please complete the following information):
I am running the webserver via AWS Lightsail on a bitnami Wordpress instance
Everything else appears to work just fine.
The text was updated successfully, but these errors were encountered: