Error during FTP change directory

[LunarDerrick]

Website URL

https://filemanager.ai
ftp username: if0_37135633

Error Message

Error during FTP change directory
Unable to change directory
Could not retrieve directory listing
No such file or directory

Other Information

I am cleaning up my remote directory, but there are 2 particular folder(shown in screenshot) I am unable to do anything. Both folders have 0777 permission. I believe these folders the remains of last time when my laravel /bootstrap/cache was configured to my local machine rather than remote directory.(just a guess, not certain)

My concern is, those ghost folders, do they consume my inode usage? As I have no use for them, I would like to remove them if possible: (full path below for convenience)

htcdocs/public/C:\laravel_little_smart_website\storage\framework\views
htcdocs/public/C:\laravel_little_smart_website\storage\logs

[Oxy]

@LunarDerrick I hid the previous screenshots and replaced them

Never take a screenshot from the Monsta file manager so the address is visible
because anyone who sees/writes it can access your FTP

---

@LunarDerrick

I am unable to do anything

The problem is that the file path has a backslash in it, which is an invalid path character and then Monsta goes crazy.

If it really irritates you
make a backup of everything you need as well as the DB

then

You can install Laravel through Softaculous and then uninstall it again via Softaculous and it might go away

OR

You can remove your domain from the current hosting account, backup the files that you do want, then, you can create a new hosting account and add the domain back.

@LunarDerrick

do they consume my inode usage

Yes

[LunarDerrick]

Never take a screenshot from the Monsta file manager so the address is visible
because anyone who sees/writes it can access your FTP

Understood, I’ll be more mindful next time. Thank you for the advice~

[Admin]

Instead of rebuilding the website on a new account, you can also delete the file through PHP code. After all, if PHP code can create it, then PHP code can delete it.

I wrote about that in another topic a few months ago here:

I can't delete a sqlite file

It seems you created a file with a backslash in the name. That’s not an acceptable character for file names, and behavior surrounding such files may be inconsistent. And it seems that while PHP lets you create such files without any problems, FTP (and the file manager) do not. I think the best way to remove this file is through PHP. To do so, create a PHP file in the same folder as this file, say, deletefile.php with the following contents: <?php if (unlink('utils\gallery.sqlite')) { ech…

[LunarDerrick]

This solution works for me. By directly using PHP code, I can properly access the target files, which I found out they are folders/directories, with remaining files within them. So, after running recursive function of unlink() followed by rmdir(), I have successfully removed the folders.

This pair of issue & solution deserves more attention.