The error message Error creating configuration directory: No such file or directory started appearing in the frame where the file manager resides upon trying to access it by a virtual server owner user (not the root-like admin).
Here is how it happened:
I have a virtual server created with Virtualmin named “xyz.com”. I want to move it to be under a common name so as to host other sites next to it. The idea is to have ACME then xyz.com and abc.com under it.
Renamed it to “ACME” from Virtualmin’s Change Domain Name page. I changed all the options on that page to point to the new name ACME: Admin username, home dir, suffix and group.
Edited ACME’s virtual server, and disabled all features except for “MariaDB database enabled” and “Webmin login enabled”
The File Manger option is not available on the left side for ACME. Possibly because the “Apache website” option is not enabled.
But the File Manger option is available for xyz.com under ACME. However, when clicked the error message is shown: Error creating configuration directory: No such file or directory
The URL looks something like: https://host.my.net:10000/filemin/index.cgi?path=%2Fdomains%2Fxyz.com%2Fpublic_html%2Fwordpress&xnavigation=1
Enabling the “Apache website” option for ACME lets the File Manager option to appear for ACME, but gives the same error, with the path in the URL being path=%2Fpublic_html%2Fwordpress
The mentioned paths exist on the system btw. I tried being creative with this URL, but nothing worked.
I looked in the logs to see if i could find a reason for the error, but could not see anything which might have pointed me in the right direction.
I have searched for a solution without success.
My doubt is that the File Manager has stored some path somewhere and it’s trying to open it by default then it fails. I couldn’t find where such a “recently used list” could be stashed.
As you can probably tell, i am starting to get desperate. Any ideas?
@ilia sounds like a bug in how File Manager handles its config…shouldn’t it be storing in the user’s home? (And not be hardcoded anywhere so a rename breaks everything.)
This is not a bug but a feature, because File Manager remembers the previously used paths for each tab, and then tried to re-open them when File Manager is re-opened. If the path is missing (i.g. was deleted) it drops an error message to the bottom-right of the screen, alerting the user that this path no longer exists.
As you can probably tell, i am starting to get desperate. Any ideas?
What do you mean by that? Does it happen everytime you visit the File Manager module? It should only happen once.
Although, you could most probably fix that by going to the right side slider, clicking cog icon button and clicking Clear Cache from the dropdown. Does it solve your problem then?
@ilia sounds like a bug in how File Manager handles its config…shouldn’t it be storing in the user’s home? (And not be hardcoded anywhere so a rename breaks everything.)
Yes, ideally it should store it on the disk in the home directory somewhere. However, currently it stores it in the browser’s storage. It should never be the problem though, because each storage unit is hostname and username dependent. I am not sure exactly what the problem would be exactly on such domains rename but I expect that it just throws the warning once and that’s it. I will have to have a look at this, as one ever reported a problem in that area.
As an admin (root-like), a different error message appears once and then I click “go back to previous page” and it works; the File Manager gets loaded ok.
Yes, exactly. A server reboot didn’t help. Logging out and in makes no difference.
As a Virtual Server owner I found the relevant button and tried it, but still the same.
Disabling and reenabling fixed it.
So… something in the chroot config probably got stuck and causes issues after renaming, or perhaps after recreating the same domain under a different path… idk.
