Windows Client - 5.3.0 | won't authenticate login credentials Windows Client - 5.3.0 | ...

Topic: Windows Client - 5.3.0 | won't authenticate login credentials

Post Windows Client - 5.3.0 | won't authenticate login credentials
by jgarcia69 on Thursday, June 7, 2018

I've been using the Windows Client for the IP Address update for some time now. It's been a couple months since I've logged into the client to update IP's and generally, ensure all is well. As of 6/7/2018, I'm now no longer able to log into the Dynu.Client via my login credentials. It always throws a "invalid user name of password" error. These same credentials are used to log into the web portal, which is how I am able to post. I've also uninstalled and re-installed the latest from the web portal Control Panel, but no avail.

Is there something that has changed recently preventing the client from working?

Thanks in advance!

-J

Reply with quote | Report
Post Re: Windows Client - 5.3.0 | won't authenticate login credentials
by jdidi on Friday, June 15, 2018

1. Make sure you are using the username instead of the email address.
2. Check if you have assigned a Location name to your hostnames. Not using the correct location name or not using the location name at all may also cause an authentication error.

Reply with quote | Report
Post Re: Windows Client - 5.3.0 | won't authenticate login credentials
by Ptochos on Friday, January 25, 2019

I'm using my username (not enail) and password. I can log into the Dynu website and do everything in the control panel, but the Dynu.Client continually responds "Unable to authenticate."

I have updated the "update IP update password" to be the same as the site password (as it originally was), and uninstalled and reinstalled the Dynu.Client, but it still fails to authenticate.

I can't be sure that it will update my IP anymore.

What can I do?

Reply with quote | Report
Post Re: Windows Client - 5.3.0 | won't authenticate login credentials
by Ptochos on Saturday, January 26, 2019

Resolved: Enable TLS 1.0

I disabled TLS 1.0 on my server for PCI compliance, and it broke the Dynu.Client

Reply with quote | Report
Sunday, May 19, 2019 11:52 PM