after the oputage that’s have been resoloved, I see that I can reach the directories (all files gone!) trough Filemanager, but If I try to connect trough ftp, filezilla is replying a strange message:
18:31:57 Status: Disconnected from server
18:31:57 Status: Resolving address of ftpupload.net
18:32:09 Status: Connection attempt failed with "EAI_NONAME - Neither nodename nor servname provided, or not known".
18:32:09 Error: Could not connect to server
18:32:09 Status: Waiting to retry...
18:32:14 Status: Resolving address of ftpupload.net
18:32:14 Status: Connection attempt failed with "EAI_NONAME - Neither nodename nor servname provided, or not known".
18:32:14 Error: Could not connect to server
If I do a tracert from my computer Host can not be reolved:
Microsoft Windows [Versión 10.0.19045.3324]
(c) Microsoft Corporation. Todos los derechos reservados.
C:\Users\xxxxx>tracert ftpupload.net
No se puede resolver el nombre del sistema de destino ftpupload.net.
C:\Users\xxxx>
come back to confirm that If I try the ftp server ip (I saw it on the Infoof the file manager) I can login using filezilla, so it’s a mtter of using the ip instead of ftpupload.onet çin my case the ip is 185.27.134.11)
EDIT: @wackyblackie why unlist this topic? others might have same issue and come here to check… tghere is no info on this specific symptom on the outage thread so this might help someone
There was an issue yesterday where both the control panel as well as the nameservers were down for about an hour.
Because the nameservers were down, user websites may also have been difficult to access for some people
FTP itself was unaffected. However, since the FTP hostname ftpupload.net is also using the nameservers, FTP clients would have had trouble resolving the FTP server hostname because of the nameserver issue. Using the FTP server IP directly circumvented this.