Audio player blocked because of SSL certificate set in apache directives

Discussion in 'Plugins/Modules/Addons' started by Keoz, Dec 1, 2018.

  1. Keoz

    Keoz Member

    Hello,

    My website runs from a remote VPS.
    The mp3 track was manually set in WIMPY script (installed in website root directory) and is streamed from MEGA.NZ audio storage online server : https://mega.nz/#.........

    Since I installed a self-signed SSL certificate in the "apache directives" section of my website, the WIMPY PLAYER (one mp3 track only) is still correctly displayed, but does not launch. Beside the URL field, an “information“ icon when clicked, explains to the visitor that some contents were prevented to run because this site is not fully secured.

    *** SSL CERTIFICATE SETTING ***
    RewriteEngine On
    RewriteCond %{HTTPS} off
    RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI}

    *** WIMPY PLAYER SCRIPT ***
    (website html head section)

    <!-- Wimpy Engine (you only need one of these) -->
    <script src="/wimpy/wimpy.js"></script>
    (website page html body section)
    <!-- Wimpy Player -->
    <div data-wimpyplayer data-skin="/wimpy/wimpy.skins/038.tsv" data-autoPlay=1 data-media='[{"title":"Tick tack","file":"https://mega.nz/#!KDQxQIqA!WP......"}]'></div>

    *** QUESTIONS ***
    How can I make the self-signed SSL certificate to accept the audio player ?
    Is there a proper way to do so, adding something in the apache directive ?


    Regards,
     
  2. Taleman

    Taleman Well-Known Member HowtoForge Supporter

    Means you have http links. Replace them with httpS.
     
  3. Keoz

    Keoz Member

    Not at all ! the page URL already contains “https“
    This means that problem is else where... ??
     
  4. Taleman

    Taleman Well-Known Member HowtoForge Supporter

    I mean http links in the contents of that page.
     
  5. nhybgtvfr

    nhybgtvfr Active Member

    it may be the self-signed certificate. to eliminate that as a potential problem, you could try using a full, authenticated certificate. if you don't want to pay for one, you can use a letsencrypt one. just apply it to that website instead of the self-signed one.
    obviously, there's traffic back and forth between your vps and the mega.nz server. it could be your vps is waiting for the mega.nz server to accept the self-signed certificate, which it can't do.
     
  6. Keoz

    Keoz Member

    Thanks for both your replies.
    The player works fine now, and a green lock shows up beside the URL address in SSL mode “https“ !
     

Share This Page