myds.synology.com down and DDNS not working

[klieber]

I have a synology.me DDNS account set up for easy remote access. However, twice now, my DS411j has "lost" the credentials I have stored for the DDNS account. I started getting email notifications saying:

DDNS service failed to register IP address <my ip address> to <my ddns name>.synology.me

The thing is, I never touched this setting. This is a "set it and forget it" sort of thing for me and I never, ever go into the control panel where it's set. (ezCloud) To fix it, I enter the exact same password again, hit 'apply' and then all is well. So the password isn't being changed. The diskstation just seems to lose it somehow.

So....what's causing the credentials to get fubar'd?

[mikercol]

I'm getting the same thing. Tried "Disable/Reinable", "Retype Password". Status Authentication Failed. Funny thing is the DDNS appears to be working. I don't know much about the details of this process, if perhaps the prior external ip is still registered and never really needed to be updated??? It does look like there are some real issues at synology re DDNS this appears to be a recurring issue. the older threads (last week) regarding this issue are locked for some reason. I may have to switch back to no.ip.

HEY in the time it took to write this - Status NORMAL. I'm going to disable the notification email for this message a wait for a real access failures my phone has been tweeting all morning with the notifications. I hope they fix it soon!

[rock15478]

The DDNS server is temporarily out of service

Same thing other people are getting!!

Quit locking these threads out and FIX the problem or offer some explanation or prepare to lose a ton of business.

[Arjan]

I got this problem as well.
Last week for at least a day, and today again for several hours. I'm getting crazy from all the spam sent to me by three NAS stations (at different locations and ISP's!!!) constantly about being unable to register their IP.

[mike42dk]

Hi

When the other tread was locked by ADMIN DanielP there was a guide to follow !!!

Plz do that instead of posting new post's.

Dear All,

The problem you've all encountered has been identified as a system glitch on Synology DDNS server. If you are still receiving this notification from our DDNS service, please follow the steps below to solve the problem:

1. Disable and then enable DDNS service
2. If the status remains "Authentication failed", please re-type the password and apply the setting.
3. If the problem is still not resolved, please contact Synology Technical Support for help.

Support Form

We apologize for the inconvenience.

[zandhaas]

I think it's a "MYDS Center" problem.

When trying to login to MYDS center I get following message:

Warning: pg_connect(): Unable to connect to PostgreSQL server: could not connect to server: Connection timed out Is the server running on host "127.0.0.1" and accepting TCP/IP connections on port 8432.


It seems like the postgresql server is overloaded.

[cjthebrave]

Yeah Michael,

You shouting at customers doesn't really help either

Following the instructions does indeed fix the problem for a little while, but as Zandaas identifies, there seems to be something struggling to take the strain, as a few minutes later (15 or so) the mails start again, grrrrrr!

I suspect that your systems can't cope with the number of DDNS requests it is receiving and only occasionally manages to acknowlege the request.

Your 'Fix' just makes a couple of requests in a short period of time and hence the odds are more likely that an acknowledgement will be received

Please go and get it sorted instead of implying that it's something the end user is actually in control of

[Hansel]

Yep, same problem again this morning

[ethuesen]

I'm getting the same problem...

My NAS is still accessable, when i type the DNS adress, but my system log get's pretty messed up..
I have already tried the posted solution, but i didn't help..

Here's a example of my log

[Hansel]

How about you stop closing threads about this and actually respond to the problem? It's clearly an issue at your end, and the "fix" that was posted in one of the other closed threads isn't a fix at all.

One little statement that you're aware of the issue and a reason it's happening and we'll be good.

[_Johnito_]

Yep, i keep receiving emails from noreply[,at,]synology.com telling me there is issues about my .dscloud.me DDNS. The thing seems alive and living its own life, thats fine, but i begin to feel a bit tired of getting those useless emails.

Is there a cleaner option than just put them in the junk bin ? I would feel bad to junk/filter mails from Synology.

[3r3rc3]

Today is another day (since yesterday) that DDNS service doesn't work properly. My NAS keeps sending me emails about failed registering attempts (quite annoying as there are too many of them every hour) and then when I am trying to login to myds.synology.com there is a failure in database (as per locked topic):

Warning: pg_connect(): Unable to connect to PostgreSQL server: FATAL: sorry, too many clients already in /volume1/web/support/adodb/drivers/adodb-postgres64.inc.php on line 662 Database connection failed

Can someone at Synology fix the problem once for good and stop giving excuses stop/start service etc? This is problem on Synology db server side and this is why we are getting these errors.

[Nullius]

Same here ... it's driving me nuts.
I temporarily disabled the notifications because my IP only changes each 3 months but it looks like they have some issues at their end

[Nullius]

Go to Control Panel -> Notifications -> Advanced -> System.
(Temporarily) Disable the DDNS notification until they've fixed the problem

[cjthebrave]

SYNOLOGY - Stop hiding from the fact that the DDNS service is failing!!

You have not only locked previous threads relating to this, but now it appears you are deleting them too - the last one on this subject miraculously dissappeared whilst I was replying.

You clearly have an issue with the DDNS service, as multiple users are pointing out that they are being bombarded with notifications etc warning them of their systems inability to register. I personally received about 12 last night, my unit is failing to register 1 in every 3-4 attempts.

Your alleged 'fix' was nothing other than a sham, it was merely an increased chance that it might register if you tried a couple of times in quick succession.

You clearly have a capacity issue, which is continuing as I type. (Last failure 09:21 BST)

How about you fix it rather than hide from the problem by blocking users from discussing it??

This is a forum for users right?? We are allowed to raise issues here?? You are an open and honest company?? Own up, we all make mistakes!!

Yours, one grumpy, e-mail bombarded and now ignored Synology user