Expected behaviour
Sync between local folder and remote folder
Actual behaviour
[url]/status.php - server replied: Not Found.
Steps to reproduce
- Install ownCloud client on headless Linux Server
- Follow directions from here to sync: hxxxs://doc.owncloud.com/desktop/next/advanced_usage/command_line_client.html
Server configuration
Operating system: Debian 11
Web server: Apache2
Database: MariaDB/MySql
PHP version: 7.4
ownCloud version: 10.11.0.6
Storage backend (external storage): None (local storage)
Client configuration
Client version: owncloudcmd ownCloud 3.1.0.9872
Operating system: Debian 11
OS language: US English
Qt version used by client package (Linux only, see also Settings dialog): Command line only - client installed on headless server. QT not used with CLI
Client package (From ownCloud or distro) (Linux only): From Owncloud Debian Repository per the instructions here: hxxxs://download.owncloud.com/desktop/ownCloud/stable/latest/linux/download/
(choosing Debian at that page, could not link directly to the Debian page)
Installation path of client: /usr/bin/owncloudcmd
Logs
- Client logfile: Unable to locate. If someone can direct me where to find it on a headless install, I will gladly provide it. This is a headless installation - no GUI. The command run is:
owncloudcmd --trust /tmp/radiopa hxxxs://[user]:[pass]@[server]/remote.php/webdav/Production/RadioPA/News
The response is:
gui.platform: adding plugin directory â/opt/ownCloud/ownCloud/bin/âŚ/lib/x86_64-linux-gnu/pluginsâ
23-02-03 20:55:59:789 [ warning sync.checkserverjob ]: error: status.php replied 404
23-02-03 20:55:59:789 [ fatal default ]: Failed to resolve hxxxs://[server]/remote.php/webdav/Production/RadioPA/News Error: Error transferring hxxxs://[server]/remote.php/webdav/Production/RadioPA/News/status.php - server replied: Not Found.
Aborted
Note that I am able to connect to the server using another machine with a GUI and the desktop client, using the same credentials, with no issue. The path does exist. It looks like the command line client is asking for a file called âstatus.phpâ, which is not in that directory. I do know it is connecting to the correct server, as I get an SSL error without the --trust option. The information in the error matches exactly what I would expect - the certificate is for external access to the server instead of internal (different hostname), this connection is internal as is the PC client I also tested with.
An example server log entry from a connection attempt:
{âreqIdâ:âd2a38cf2-5db7-49ee-9f42-f65d884ec471â,âlevelâ:2,âtimeâ:â2023-02-04T02:05:25+00:00â,âremoteAddrâ:â[address]â,âuserâ:âRadioPANewsâ,âappâ:âno app in contextâ,âmethodâ:âGETâ,âurlâ:â/remote.php/webdav/Production/RadioPA/News/status.phpâ,âmessageâ:âFile with name Production/RadioPA/News/status.php could not be locatedâ}
If I use the GUI client on another PC, I have no problem putting the file in the same location I am trying to with the command line client. By looking in the data directory on the server, I can confirm the file did sync from the desktop GUI client to the server.
What I am working towards is a script to run via cron that will download the current news file from our provider, put it in a local folder, sync that folder with ownCloud then remove the local file. The folder in ownCloud is also synchronized with the automation system, which monitors the folders for an audio file then imports it according to a defined set of rules in the automation system. I can download the file with no problem. The problem comes when I attempt to sync to ownCloud to put the file there for automation to grab.
I have tried a number of things related to the path;
/remote.php/webdav/production/radiopa/news
/remote.php/webdav/production/radiopa/news/
/remote.php/webdav/Production/RadioPA/News (capitalization matches the folder appearance in the web interface or a GUI client)
/remote.php/webdav/Production/RadioPA/News/
All return the same error - the path I supply with status.php tacked on the end and a not found message.
If you would like additional information, please ask. I am going to ask that you also be specific, as this is my first foray into using a headless box with the client. Also, note that the client is actually on the ownCloud server - attempts using localhost instead of the IP address in the server URL have the same result.
I am guessing that writing the file directly to the appropriate directory in /data/ would be ill advised and not work. Of course, if it would work, I can ditch the client and do it that way. I would prefer to get the client to work, as eventually this portion will move to a different server (still headless, still Debian 11) and I would like to be able to simple move the script and configure cron on that box to run it.