docker
docker copied to clipboard
After upgrading 28.0.1 ftp module missing
After upgrading to 28.0.1, files app stopped showing user files.
It took me a while to discover the error message:
"File":"/var/www/html/apps/files_external/lib/Lib/Storage/FtpConnection.php","Line":37,"message":"Call to undefined function OCA\\Files_External\\Lib\\Storage\\ftp_connect()","exception":{},"CustomMessage":"Call to undefined function OCA\\Files_External\\Lib\\Storage\\ftp_connect()"}}
External storage support is a core app, shipped with nextcloud itself and we were using it to add external ftp server to the nextcloud instance. Out of blue everything stopped after upgrade. Thanks god, it's Sunday.
Interim solution is:
docker-php-ext-install ftp
docker-php-ext-enable ftp
apache2ctl restart
But its effect will be lost upon container restart.
Please re-add php ftp support into the nextcloud image.
P.S.: I'm using nextcloud:latest for quite a long period of time (i.e. for years ) and external ftp was working like a charm all the time
Also, I've hit #2118
Duplicate of https://github.com/docker-library/php/issues/1488
@J0WI , they're not planning to bring it back by default. So, to my understanding, it is not a duplicate - now it's an issue of the nextcloud image.
thx @aol-nnov for bringing this ticket up. I also lost all my external shares.
This issue persists also in Nextcloud version 28.0.2.
So it seems we have two choices per upstream:
- live without it (which would be a regression) but maybe document it with an example Dockerfile for local customization
- add it to our base builds ourselves (example) since we can no longer inherit it from upstream
Hi everyone,
Experienced this one also. On my side, not that inconvenient to just manually install it using the suggested solution. However, even with this it's still failing:
The config of the mount points in settings are all green ticked as they were before and I couldn't find any error details. Has anyone found a solution for that?
Thanks!
Suggested solution works for me.
SFTP does still work. Do you have a special requirement that depends on plain FTP?
I do not need encryption on my isolated network, but I need to transfer high volumes of data, thus plain ftp.
Also, changing my infra due to nextcloud regressions is the last thing to dream on, to be frank...
The right question is why we can't just add the module back? It is not like the FTP option was removed from nextcloud, but the FTP module that not included by default from the upstream image. Samba module also had the same treatment for years.
I vote for adding it back directly in our images, primarily since it's a sudden regression (that no one expected).
My feelings these days about the old FTP protocol though are merely nostalgic though so I don't have a test environment for this.
Does one of you that has tested the Dockerfile adjustment (based on the one here and drawn from the steps in docker-library/php#1482) feel up to submitting a PR?