Strange FTP problems started occurring after Sep 28 **solved**

[dolfs]

I had not paid attention closely so don't know when this started exactly, but I am observing problems uploading files through FTP service. It seems that last successful upload happened on Sep 29.

I noticed this for a configured service to upload a template based file:
Every minute:
- Template: http://starreveld.com/weather_uploads/u ... ags.mb.txt
- Path: /starreveld.com/weather_uploads/uploadMB/tagsMB.txt
The error:
Error: 2022-11-30 14:43:22 ncftpput /starreveld.com/weather_uploads/uploadMB/tagsMB.txt: server said: /starreveld.com/weather_uploads/uploadMB/mb_tagsMB.txt: No such file or directory (no more tries):

This always worked fine. I have independently verified the username/password using an ftp client and uploading a file to the same directory.
The interesting detail in the error is that it refers to mb_tagsMB.txt (notice the leading mb_ that seems somehow manufactured). I have also verified a browser can download the template without issue.

Then I went to check my camera picture upload (also using ftp) and it fails too:
Cam configuration: <url to fetch an external picture>
Every Minute:
Path: /starreveld.com/Front Left/snapshot.jpg
The error:
Error: 2022-11-30 14:24:27 ncftpput /starreveld.com/Front Left/snapshot.jpg: server said: /starreveld.com/Front Left/mb_snapshot.jpg: No such file or directory (no more tries):

Notice here too is this, apparently manufactured, "mb_" prefix.
Here I manually tested the whole path by fetching the image in a browser, saving it in a file, and using ftp client to upload. It works manually.

[admin]

Looks to me as if something on your server side (new FTP daemon, etc) has changed.
Metrobridge uploads file at a temporary name (prefixed by "mb_") and the renames it to the final name. When the FTP server does not support this or the FTP user does not have necessary rights, this fails. Just uploading a file with a FTP client does not mimic what Meteobridge is doing via NCFTP.

[dolfs]

Thanks. Describing the behavior allowed me to mimic that behavior and find the actual problem. Sounds indeed the something changed in my provider because all my FTP paths were setup as absolute (starting with /) and had always worked until then. Removing the initial slash fixed the problem.