AudioIgniter Tracks Not Playing

Ηello @philgnfla

There could be many things going wrong locally. Can you please share any errors or logs from the browser console https://firefox-source-docs.mozilla.org/devtools-user/browser_console/index.html

I should have been a little more specific. I am using WP Local, version 7.0.1+6387 on a Windows 10 system, using Google Chrome, to develop the site. I have WordPress 6.2.2, and Audioigniter version 2.0.0. Everything works fine on the development system, but when I enable a WP Local live link and login from a different (Windows 10) system, using Google Chrome, the display looks great, but when I select a track, it just doesn’t play the audio. I’m not sure what you mean by the “errors or logs from the browser console”? I don’t get any errors displayed.

Thanks,
Phil G.

Here are the last few lines from the WP Local logs:

2023/06/21 15:01:45 [warn] 5612#18264: *7163 a client request body is buffered to a temporary file C:\Users\Phillip\AppData\Roaming\Local\run\router\nginx/temp/client_body_temp/0000000029, client: 127.0.0.1, server: philg-wpfse.local, request: “POST /wp-admin/post.php HTTP/2.0”, host: “philg-wpfse.local”, referrer: “https://philg-wpfse.local/wp-admin/post.php?post=283&action=edit”
2023/06/21 15:03:52 [warn] 5612#18264: *7163 a client request body is buffered to a temporary file C:\Users\Phillip\AppData\Roaming\Local\run\router\nginx/temp/client_body_temp/0000000030, client: 127.0.0.1, server: philg-wpfse.local, request: “POST /wp-admin/post.php HTTP/2.0”, host: “philg-wpfse.local”, referrer: “https://philg-wpfse.local/wp-admin/post.php?post=283&action=edit”
2023/06/22 15:20:52 [warn] 1744#14908: *1006 an upstream response is buffered to a temporary file C:\Users\Phillip\AppData\Roaming\Local\run\router\nginx/temp/proxy_temp/1/00/0000000001 while reading upstream, client: 127.0.0.1, server: philg-wpfse.local, request: “GET /wp-content/uploads/18-WolfCreekPass.mp3 HTTP/2.0”, upstream: “https://127.0.0.1:10023/wp-content/uploads/18-WolfCreekPass.mp3”, host: “philg-wpfse.local”, referrer: “https://philg-wpfse.local/songs/”
2023/06/22 15:42:32 [warn] 1744#14908: *2007 an upstream response is buffered to a temporary file C:\Users\Phillip\AppData\Roaming\Local\run\router\nginx/temp/proxy_temp/2/00/0000000002 while reading upstream, client: 127.0.0.1, server: philg-wpfse.local, request: “GET /wp-content/uploads/18-WolfCreekPass.mp3 HTTP/2.0”, upstream: “https://127.0.0.1:10023/wp-content/uploads/18-WolfCreekPass.mp3”, host: “philg-wpfse.local”, referrer: “https://philg-wpfse.local/wp-admin/post.php?post=31&action=edit”
2023/06/22 15:46:57 [warn] 1744#14908: *2007 an upstream response is buffered to a temporary file C:\Users\Phillip\AppData\Roaming\Local\run\router\nginx/temp/proxy_temp/3/00/0000000003 while reading upstream, client: 127.0.0.1, server: philg-wpfse.local, request: “GET /wp-content/uploads/18-WolfCreekPass.mp3 HTTP/2.0”, upstream: “https://127.0.0.1:10023/wp-content/uploads/18-WolfCreekPass.mp3”, host: “philg-wpfse.local”, referrer: “https://philg-wpfse.local/songs/”

@philgnfla Can you play these audio files using WordPress default media player? Can you share your console log (browser instead) https://developer.chrome.com/docs/devtools/

I just set up a simple one page, “UnTrusted” site with a WP audio track. It played just fine. Here are the Client side Chrome console log:

Mixed Content: The page at ‘https://rebel-paintbrush.localsite.io/’ was loaded over HTTPS, but requested an insecure element ‘https://rebel-paintbrush.localsite.io/wp-content/uploads/2023/07/MyRoomLive01.wav’. This request was automatically upgraded to HTTPS, For more information see https://blog.chromium.org/2019/10/no-more-mixed-messages-about-https.html
rebel-paintbrush.localsite.io/:1 Mixed Content: The page at ‘https://rebel-paintbrush.localsite.io/’ was loaded over HTTPS, but requested an insecure audio file ‘https://rebel-paintbrush.localsite.io/wp-content/uploads/2023/07/MyRoomLive01.wav’. This content should also be served over HTTPS.
rebel-paintbrush.localsite.io/:1 Mixed Content: The page at ‘https://rebel-paintbrush.localsite.io/’ was loaded over HTTPS, but requested an insecure element ‘https://rebel-paintbrush.localsite.io/wp-content/uploads/2023/07/MyRoomLive01.wav’. This request was automatically upgraded to HTTPS, For more information see https://blog.chromium.org/2019/10/no-more-mixed-messages-about-https.html

Here is the Chrome console log from the Client side, trying to use AudioIgniter:

Mixed Content: The page at ‘https://ancient-plants.localsite.io/songs/’ was loaded over HTTPS, but requested an insecure element ‘https://philg-wpfse.local/wp-content/uploads/11-ExitPlan.mp3’. This request was automatically upgraded to HTTPS, For more information see https://blog.chromium.org/2019/10/no-more-mixed-messages-about-https.html

philg-wpfse.local/wp-content/uploads/11-ExitPlan.mp3:1     GET https://philg-wpfse.local/wp-content/uploads/11-ExitPlan.mp3 net::ERR_CONNECTION_REFUSED ancient-plants.localsite.io/:1 Uncaught (in promise) DOMException: Failed to load because no supported source was found.

Hi there,

you are trying to load a non secure element from a secure website

make sure both your site and audio URL have https:// in the URL, and of course you have SSL installed in both your site and audio location.

If you do not want to use SSL. make sure all URL’s have https:// and there is not redirect to https:// domains also.

<span class=”prokeys-snippet-text”>Let me know if this worked for you.</span>