Announcement

Collapse
No announcement yet.

6.2.0.3 Unable to analyze

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Netflix 6.2.0.3 Unable to analyze

    After uninstalling the old version according to the forum's instructions, I downloaded the 6.2.0.3 offline package and installed it, but Netflix remained in analysis mode. I even formatted the C drive and reinstalled Windows 10 because of this, but the problem still persists. Attached is the log file, please help me see how to solve it.

    Thank you!​
    Attached Files

    #2
    I can't currently test (at work there is proxy and Port-filter) ..
    .. but I see in (truncated) log:
    Code:
    [Critical]: KeyHandshake
    [Critical]: GetInitializationFileEx status :403, url: https://www.netflix.com/nq/website/memberapi/ ..
    [Critical]: "[Netflix]" meta analyze failed. fetch meta response data empty.
    So you have no access to info in API because the handshake error ..
    .. looks for me often same in 1st try - so cancel and refresh with F5 or here

    Comment


      #3
      Thank you, refreshing still doesn't work

      Comment


        #4
        No problem with 6203 and analyzing your title detected (1st try - without refresh)

        Click image for larger version

Name:	nf_love_village.jpg
Views:	0
Size:	63.7 KB
ID:	453065
        -= click pic to enlarge =-

        Otherwise I know handshake error only when using bad/known VPN
        If you don't use vpn, perhaps a temporary ip block ..
        .. so try router reconnect (if dynamic ip)
        and/or try a vpn server near your location​

        Comment


          #5
          Thank you for your answer. The VPN I am currently using can be analyzed by other websites, only Netflix cannot. However, Netflix videos can be played normally, but it cannot be analyzed.

          Comment


            #6
            > However, Netflix videos can be played normally, but it cannot be analyzed.

            Originally posted by Germania View Post
            Otherwise I know handshake error only when using bad/known VPN
            Try a different vpn server - I've without vpn no problem with successfully nf api access

            Can you analyze other nf titles without vpn ??

            Comment


              #7
              I am in China and can only access through VPN. Before the API issue occurred on 6.1.9.7, I was able to analyze Netflix. After fixing Netflix on 6.1.9.8, I saw that everyone was working normally, but I have been unable to analyze it. I thought it was an issue with uninstalling it, so I directly reinstalled the Windows system, but it still doesn't work. I am not sure if other software such as Pazu and Cleverget need to call APIs, but they can be analyzed and downloaded when I use VPN.

              Comment


                #8
                Originally posted by zwj1218 View Post
                I am in China and can only access through VPN. Before the API issue occurred on 6.1.9.7, I was able to analyze Netflix. After fixing Netflix on 6.1.9.8, I saw that everyone was working normally, but I have been unable to analyze it. I thought it was an issue with uninstalling it, so I directly reinstalled the Windows system, but it still doesn't work. I am not sure if other software such as Pazu and Cleverget need to call APIs, but they can be analyzed and downloaded when I use VPN.
                May you can also wait for the new version and try it again.

                Wilson
                Please post your logs the default location is:
                For DVDFab 13: C:\Users\User Name\My Documents\DVDFab\DVDFab13\Log
                For StreamFab: C:\Users\User Name\My Documents\DVDFab\StreamFab\log
                Please use attachment button and attach your most recent, Internal log and post right here.
                If it's the burning issue, please also attach burn log.

                Thanks!

                Comment


                  #9
                  Okay, I've been waiting for several versions, that's why I came to the forum for help. I hope the next version can solve this problem. Thanks again.

                  Comment

                  Working...
                  X