MGStage downloader fails to start download

    • Bbubbikins

        Lv. 1
        Topic starter
      • Lv. 1
      • Post #1

      MGStage downloader is not functioning properly. It goes through webpage, webplayer, stream selection and media info fetching before stuck analysing, and eventually quoting a loss of internet . The streaming of MGStage works normally in web browsers. The failure occurs irrespective of program version(in so much as 6.2.1.3, 6.2.1.2, 6.2.1.1, 6.2.1.0 and 6.2.0.8)

      The problem was not yet present on Dec 30, but occurs consistently since.

      I've tried deleting content in %username%...\temp\ and %AppData%...\taskdata\, but to no avail.

      The log file, which I will append, shows the rooting error to be "error curl post: Couldn't connect to server", but I don't know the nature of this message.


      This screenshot shows video playing back normally in Firefox


      These screenshots show the progression of the failure




      StreamFab.log

      • Created

        a year ago

      • Last reply

        a year ago
      • 5

        Replies

      • 197

        Views

      • 2

        Users

      • B

      • Bbubbikins

          Lv. 1
          Topic starter
        • Lv. 1
        • Post #2

        Wording correction: The log file shows the error that gives rise to this failure to be...

        • Bbubbikins

            Lv. 1
            Topic starter
          • Lv. 1
          • Post #4

          The available download counter is certainly a tell-tale sign, I haven't been able to download anything for weeks. MGStage is geo-restricted, access from regions outside Japan requires proxy, and SF does exhibits perculiar behaviours working with proxies.
          When SF is set to communicate with local proxy client in HTTP, proxy client retures "app/proxyman/inbound: connection ends > proxy/HTTP: failed to read http request > malformed HTTP request "\x05\x02\x00\x02"", and SF fails to make any internet connection.
          When set to refer to system proxy settings, SF's ad prompts don't load properly, with only the prompt but no pictures.
          It is only when set to communicate with local proxy client in SOCKS5, does SF seem to work, but in all cases, the available download counter don't load.
          I fail to make sense of these loose pieces of information, I still think it's an SF problem, as I've not encountered any other programs with these issues, but if the problem cannot be resolved, I will try to proxy from a local server, set up a VPN tunnel and direct all traffic coming out of the PC to it as a last resort.

          • Cats4U

              Lv. 5
            • Lv. 5
            • Post #5

            What did they say when you sent a Feedback and filed a ticket with the StreamFab staff about their proxy?

            • Bbubbikins

                Lv. 1
                Topic starter
              • Lv. 1
              • Post #6

              I never got to discuss the networking issues with the support team, they didn't seem concerned with the nature of the problem or referring the matter out. I had a ticket running for ten days, and after an initial suggestion of deleting content in /Documents/DVDFab/StreamFab/, replies came only to ask to try a new version, even though neither the failure itself nor its underlining issues were reflected in change log. I suppose they are betting on reinstalling, after a sufficient number of times, would wipe a problem away.

              • Bbubbikins

                  Lv. 1
                  Topic starter
                • Lv. 1
                • Post #7

                I've come onto an intervention to resolve this issue. It is indeed a networking issue, IE proxy sits too high in the networking stack, and SF fails to properly observe proxy settings in its operations.

                In an elevated command line, enter the following commands:
                netsh winhttp import proxy source =ie
                setx http_proxy socks5://localhost:
                setx https proxy socks5//localhost:

                These settings prepare the ground for SF to operate in a proxy environment. I still don't know why this issue suddenly occurred, but in this way, it can be worked around.