Cumulus Support

Has anyone got ftp from CumulusMX working with 1and1 (Ionis) Web Hosting (Windows Package)

i.e., FTPS from Cumulus to Ionis Webspace?

regards
Dave

(New thread created with more specific details than those in my earlier thread . . .
viewtopic.php?f=40&t=18132)

I'm with Ionos but have a server not a hosting package. And it is on Linux. So I definitely can't answer yes to your question

I would suggest the following:

• Check and double-check (and check again) your username and password you are putting in Cumulus.
• Ensure you have selected passive mode.
• Post MXDiags files on here so we can look at the errors. Ditto the FTP log.

Hi,

I have checked and tested different logins and see the expected responses when the credentials are and aren't correct, so I think that I know that the login details are correct and working.

From searching the forums and wiki, I found the .ini file setting DisableFtpsExplicit=0 to use Implicit mode, this has helped a little, in the sense that I can see more meaningful messages in the logs now.

With the current configuration, I can see the user being logged in successfully, but the expected files cannot be found and there are "500" access denied messages when trying to create them.

After log in, I can see PBSZ 0 and PROT P commands with "200" responses
Then FEAT OPTS and SYST commands with expected returns

The next message is about not being able to find /index.htm, so it sounds like a target directory problem.

I have tried just about every combination that I can think of in the Hostname and Remote Directory fields (including by IP address) and can't get a working combination. That's why feedback from someone who has it working with 1&1/Ionis would be really helpful. It would also be helpful if there was a specific debug option to do an FTP PWD to confirm the current working directory.

The logs are currently quite full of stuff that may be confusing as I have tried various combinations. I think that I will delete the logs, create new configuration then generate new logs to upload.

regards
Dave

stevendt wrote: ↑Tue 26 May 2020 11:42 amthen generate new logs to upload.

Good plan. From what you've described so far it doesn't appear to be an Ionos-sepcific problem, more a configuration problem. Your logs will tell us much more.

OK, reduced size log files attached . . .

As I said, I'm not sure that they will tell you anything other than it is likely a target directory problem, but the logs don't confirm where the transfer is being attempted to

regards
Dave

You should really upload the full MXDiags log. With respect, you may be removing some pertinent detail.

Also - could you upload a screenshot of your "Internet Settings" -> "Web/FTP site" settings screen?

I would try uploading without the leading forward slash. That will be sending to the FTP root folder, which may or may not be your web site root folder.

Screen captures

As I said though, these details are likely correct, Cumulus is resolving the hostname to IP address and successfully logging in

The Directory is blank, 1&1 can specify the log in directory when the FTP user is configured, but I have tried creating users with access to the upload root and have entered both the root and specified log on directory in Cumulus - to no effect

regards
Dave

Hi Mark,

thanks for the input. I thought that might be something to do with it, but can't see how to stop the forward slash being added by Cumulus?

regards
Dave

stevendt wrote: ↑Tue 26 May 2020 11:42 am From searching the forums and wiki, I found the .ini file setting DisableFtpsExplicit=0 to use Implicit mode, this has helped a little, in the sense that I can see more meaningful messages in the logs now.

DisableFtpsExplicit=0 (ie Explicit mode) is the default. Did you mean you have set it "1" and you are using Implicit mode and connecting over port 990?

But as Freddie said, from the log snippets there is not enough information, we need to see the full logs.

The slash will be coming from your Remote FTP Directory setting.

stevendt wrote: ↑Tue 26 May 2020 2:17 pmAs I said though, these details are likely correct, Cumulus is resolving the hostname to IP address and successfully logging in

Yes, there's nothing wrong with your credentials. It appears that you do not have write permission to the location that you "land" in when logged on.

stevendt wrote: ↑Tue 26 May 2020 2:17 pmThe Directory is blank, 1&1 can specify the log in directory when the FTP user is configured, but I have tried creating users with access to the upload root and have entered both the root and specified log on directory in Cumulus - to no effect

When you tried specifying a login directory did you get exactly the same response code and message back in the FTP log?

On the surface this looks like an issue on the remote server rather than a Cumulus issue.

Hi Mark,

yes, Port 990 is required by 1&1. I was not getting anywhere without adding that entry to the .ini file. That was when I restarted the server this morning after reading the wiki last night.

I will check the remote directory again, but in the configuration at the 1&1 end, there is no trailing slash. If it is being added by 1&1, it is being done automatically, I don't see a way of turning it off.

I will upload the full log. I had not restarted the server, so this log contains lots of entries while I tried different options again today. The only relevant one is the last session at 14:30.

Please tell me what extra information you think relevant - I don't see any?

regards
Dave

When entering the directory in Cumulus, the errors are the same, except the file names in the log are prepended by the directory that I enter

regards
Dave

I think I might have fixed it

more in a minute . . . .

I can't wait