I’m using sonaar pro plugin. After updating the plugin, I can’t play the external mp3 files(I’m using AWS), only those mp3 files are getting played which are uploaded on my website. It looks like I’m getting a CORS error. Been using the pro plugin for almost 2 years, never faced this kind of error. The free version works fine but when I activate the pro sonnar plugin, it doesn’t work. So, I think it not my server error, if it was then nothing should work with the free version too. I've contacted my hosting, they say that there is no problem with their hosting.
edit: PS, after disabling the pro plugin and using the free plugin only, everything works fine.
Thanks for the quick reply. Actually, after searching a lot on the internet, I found out that I need to add CORS policy in my AWS S3 bucket. Idk why this problem showed after 2 years of using AWS S3 with Sonaar. Also, I'm confused that this CORS error was only with the paid plugin and not with the free plugin.
Anyways, I added the CORS policy to the S3 bucket and everything is working now. So, I think if any of you are using the Sonaar plugin and facing this kind of issue, just add the CORS policy to your S3 bucket. You need to add your website to the policy.
I’m using sonaar pro plugin. After updating the plugin, I can’t play the external mp3 files(I’m using AWS), only those mp3 files are getting played which are uploaded on my website. It looks like I’m getting a CORS error. Been using the pro plugin for almost 2 years, never faced this kind of error. The free version works fine but when I activate the pro sonnar plugin, it doesn’t work. So, I think it not my server error, if it was then nothing should work with the free version too. I've contacted my hosting, they say that there is no problem with their hosting.
edit: PS, after disabling the pro plugin and using the free plugin only, everything works fine.
Also, this is what my console shows.
Uncaught (in promise) DOMException: The element has no supported sources.
play @ 00.wavesurfer.min.js…2.3.2:formatted:756
play @ 00.wavesurfer.min.js…2.3.2:formatted:100
playAudio @ sonaarPlayer.js?ver=2.3.2:128 play @ sonaarPlayer.js?ver=2.3.2:123
setPlayer @ sonaarPlayer.js?ver=2.3.2:287
setPlaylist @ sonaarPlayer.js?ver=2.3.2:209
click @ iron-audioplayer.js?ver=2.3.2:338
dispatch @ jquery.js?ver=1.12.4-wp:3 r.handle @ jquery.js?ver=1.12.4-wp:3
Also, sometimes when the website loads slow, it shows {{PLAYLISTTITLE}} at the top.
here is one of the page I'm talking about, https://soundbankmusic.com/soca/
I'm using external mp3 from AWS S3. Please don't say this is some server error, as everything works fine when I deactivate the paid plugin.
Hi,
I cant seem to reproduce the be able to replicate your issue. See video I have recorded: https://d.pr/v/zRSwgp
Could you please elaborate on steps to reproduce the issue on my end?
Make sure you are visiting https version of your website ( https://soundbankmusic.com/soca/) and not the non https: ( http://soundbankmusic.com/soca/)
Thanks,
Max from the Sonaar.io Crew
Hi,
Thanks for the quick reply. Actually, after searching a lot on the internet, I found out that I need to add CORS policy in my AWS S3 bucket. Idk why this problem showed after 2 years of using AWS S3 with Sonaar. Also, I'm confused that this CORS error was only with the paid plugin and not with the free plugin.
Anyways, I added the CORS policy to the S3 bucket and everything is working now. So, I think if any of you are using the Sonaar plugin and facing this kind of issue, just add the CORS policy to your S3 bucket. You need to add your website to the policy.
(Thread can be closed now. Thanks)