DVDFab 13.0.6.3 authorization fails despite HTTPS connection

中年のおっさん

Hello,

I am experiencing an authorization problem with DVDFab 13.0.6.3.

Environment:

Windows 10 Pro 22H2
DVDFab 13.0.6.3
Internet connection is working normally

Problem:
When I click “Authorize” after entering my account, DVDFab displays:

“Failed to connect to server. Please check your network.”

However, I have verified that this does not appear to be a normal network problem.

What I have already checked:

• Clean uninstall and reinstall of DVDFab.
• Removed all DVDFab folders from Program Files, AppData, ProgramData, Documents, Temp, etc.
• Rebooted Windows.
• Firewall and Windows Defender are not blocking DVDFab.
• Browser can access DVDFab websites normally.
• HTTPS works correctly.
• curl GET and POST requests to the DVDFab authentication server both return HTTP 200 OK.
• netstat confirms DVDFab64.exe establishes an HTTPS connection (ESTABLISHED) to the DVDFab server.
• Product information can be downloaded successfully.
• Installation completed successfully.
• Log files have been checked.

My DVDFab Member Center account shows:

DVDFab DVD Ripper
Status: Registered
License: Never Expire

So my account and license are recognized correctly on the Member Center website.

The only operation that fails is the authorization inside DVDFab 13.

Has anyone experienced this problem?

Could this be an issue with the authorization service rather than a normal network problem?

Any suggestions would be appreciated.

Thank you.

中年のおっさん

Update: I found something interesting.

I did not make any changes to Windows or DVDFab.

The only thing I did was reboot my NTT Docomo home 5G router (HR02).

After the router restarted, DVDFab authorized successfully on the first attempt.

Before rebooting the router, I had already confirmed:

HTTPS connectivity was working.
curl GET/POST requests returned HTTP 200.
DVDFab64.exe established an HTTPS connection to the server.
My license was correctly shown in the Member Center.

At the moment, the issue appears to be resolved.

I’m not sure whether the router reboot cleared a network-related issue or whether the timing was coincidental, but I wanted to share the result in case it helps others or the developers investigate similar cases.

Thank you to everyone who offered suggestions.

Mona

Thank you for your detailed troubleshooting – it’s very helpful.

You’re absolutely right that this isn’t a normal network issue. Since basic HTTPS (curl), browser access, and even the ESTABLISHED connection all worked, the problem was almost certainly at the router level – specifically, cached NAT session table or DNS routing that interfered with the authorization handshake.

Restarting your HR02 router cleared that temporary state, which is why authorization succeeded afterward. That was the correct fix.

For future reference, if this happens again, you can try:

Flushing DNS cache first (ipconfig /flushdns)
Or restarting the router as you did

We’ll pass your feedback to our dev team to consider adding clearer error messages for this scenario.

Thanks again for sharing your solution – it will certainly help other users!