• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Error ftp backup

migarcia

New Pleskian
When I try to backup and send it via ftp, tells me the following error

<?xml version="1.0" encoding="utf-8"?>
<execution-result status="error">
<object name="server" type="server">
<message severity="error" code="ApplicationException">
<description>Cannot parse output file 'ftp://[email protected]@ftp.internetdoor.es/' [URI no válido: no se puede analizar el nombre de host.]</description>
<message severity="error" code="UriFormatException">
<description>URI no válido: no se puede analizar el nombre de host.</description>
</message>
</message>
</object>
</execution-result>

I think it's the @ username ('ftp://[email protected]@ftp.internetdoor.es/' ), but if the change by 40%, then it will not let me create the ftp repository

My system:
OS Microsoft Windows 6.1;build-7601;sp1.0;suite1296;product3
Panel version 10.4.4 Update #41, last updated at Aug 4, 2012 04:15 AM
 
I have tried to translate "no se puede analizar el nombre de host" with Google Translate :)
Indeed, looks like problem in username. But I do not understand what do you mean "but if the change by 40%, then it will not let me create the ftp repository"? Could you please clarify a little bit?
 
My english

Sorry,I do not speak English and although the language of the panel is in English, it gives this message in Spanish
The translation of the message is "Invalid URI: The hostname Could not be parsed"

I think the problem may be with the use of two @, but not how to avoid it.
When I change @ with% 40 (URLEncoding), it gives me the error in "Personal FTP Repository Settings "
 
It seems to work ... is working

But I need another solution because my customers do not have the ability to change the form of the name of the ftp (user @ domain) ...

But.... thanks!!!!
 
Back
Top