Filemanager not working - No such file or directory

20 posts / 0 new
Last post
#1 Thu, 08/17/2017 - 00:16
Vipul.K

Filemanager not working - No such file or directory

Hi, I've installed Virtualmin GPL for the first time and created two virtual servers. When I log into either of these sub-accounts, I cannot access file manager in Virtualmin > Edit Web Content. The error I get is

"Error opening directory /home/test/home/test/public_html No such file or directory"

and

"Error opening directory /home/newserver/home/newserver/public_html No such file or directory"

Clearly it's looking for an invalid location appending "/home/newserver" twice. But why is this happening and how do I solve it?

Fri, 08/18/2017 - 06:57
GimN

I have identical problem as Vipul.K. Would be nice if someone can point to fix.

Thank you

Fri, 08/18/2017 - 07:43
Joe
Joe's picture

The regular link to File Manager (in Webmin->Others) should still work. This link is new, and it seems like it's not quite right. I'll have to check in with Ilia and Jamie about why it's misbehaving.

--

Check out the forum guidelines!

Fri, 08/18/2017 - 07:58
Joe
Joe's picture

I also noticed that if you add a new tab, and click on it, it'll load up in the user home directory (you still have to click through to public_html to be in the right place to edit web content thought).

--

Check out the forum guidelines!

Fri, 08/18/2017 - 14:01
Joe
Joe's picture

Should be fixed sometime tomorrow. Ilia is working on a fix for it. Until then, a workaround is provided above.

--

Check out the forum guidelines!

Wed, 09/13/2017 - 05:44
amityweb

Also getting this. If its fixed, do you know when the next release is please? Thanks

Thu, 09/14/2017 - 03:43 (Reply to #6)
Joe
Joe's picture

It should have been fixed by the most recent Webmin version several days ago. Do you have Webmin 1.852 installed?

--

Check out the forum guidelines!

Fri, 09/15/2017 - 04:32 (Reply to #7)
amityweb

Yes I have 1.852. Yum update shows no updates to come.

Error still there Following errors occured while performing operation Error opening directory /home/mysite/home/mysite/public_html No such file or directory

Fri, 09/15/2017 - 15:33 (Reply to #8)
Joe
Joe's picture

Huh. That's weird. What theme version is showing in the system information page?

You can manually update to the latest version of the theme by clicking the "Configurable Options for Authentic Theme" (the little gear that appears when you hover over the theme version in the System Information page, and then scroll to the bottom of the page and click the "Force Update Theme" (choose "latest release version").

--

Check out the forum guidelines!

Tue, 09/19/2017 - 03:58 (Reply to #9)
amityweb

I have Authentic Theme 18.49-9. I just did a force update to this version, and the problem still persists. Webmin version 1.852.

Here's the system information:

Operating system CentOS Linux 6.9
Webmin version 1.852
Usermin version 1.720
Virtualmin version 6.00
Theme version Authentic Theme 18.49-9
Firewall version ConfigServer Security & Firewall 10.25   
Time on system Tuesday, September 19, 2017 9:57 AM
Kernel and CPU Linux 4.6.5-x86_64-linode71 on x86_64
Processor information Intel(R) Xeon(R) CPU E5-2680 v3 @ 2.50GHz, 4 cores
System uptime 384 days, 8 hours, 33 minutes
Running processes 248
CPU load averages 0.85 (1 min) 0.86 (5 mins) 0.86 (15 mins)
Real memory 7.61 GB total / 2.42 GB used
Virtual memory 250 MB total / 250 MB used
Local disk space 94.19 GB total / 45.69 GB free / 48.50 GB used


Operating system CentOS Linux 6.9
Perl version 5.010001
Path to Perl /usr/bin/perl
Postfix version 2.6.6
Mail injection command /usr/lib/sendmail -t
Apache version 2.2.15
PHP versions 5.3.3, 5.4.40, 5.6.25, 7.0.10
Logrotate version 3.7.8
MySQL version 5.1.73
SpamAssassin version 3.3.1
ClamAV version 0.99.2
Wed, 09/20/2017 - 04:29 (Reply to #10)
Joe
Joe's picture

I can't reproduce this problem.

Note that it tries to open your prior tabs every time you visit. Close any tabs failing to load, and try it again.

--

Check out the forum guidelines!

Thu, 09/28/2017 - 18:30
goodname

I've got the same problem with repeating dirs; same vers #s for the 4. Solution for me was clicking "return to previous page" to open up the file manager.

Thu, 09/28/2017 - 20:04
Joe
Joe's picture

I was able to reproduce the problem I believe. Are you seeing it only for domain owner users (and not for the root user)?

--

Check out the forum guidelines!

Fri, 09/29/2017 - 02:27 (Reply to #13)
goodname

ya you're right; root works perfectly fine while domain users have this problem.

Fri, 09/29/2017 - 03:55
amityweb

Yes its the domain owner. I have not tried using root. I have a customer reporting this issue, so they have logged in using their webmin account.

Fri, 09/29/2017 - 07:02
Joe
Joe's picture

OK, great, we're on the same page and we have reproduced the issue. It should be fixed in Virtualmin 6.01 coming in a day or two.

--

Check out the forum guidelines!

Tue, 10/03/2017 - 08:57 (Reply to #16)
AlaHashesh

I'm having the same issue. Any updates?

Tue, 10/03/2017 - 14:05 (Reply to #17)
Joe
Joe's picture

It'll be fixed in the next Virtualmin release coming soon.

--

Check out the forum guidelines!

Wed, 01/30/2019 - 12:07
PauloBoaventura

any news? I have this problem, which is the way to solve it? I even tried Validate Virtual Servers And gave this error ... Beginning validation of selected virtual servers. Any problems found will be displayed in red ..

Paulo B

Thu, 07/18/2019 - 10:36
cmarabate

I started having this issue after uninstalling WordPress version 5.2..2 which I installed using the Virtualmin "Install Scripts" page. I installed it inside my public_html folder for my Virtual Server and then I went back to the "Install Scripts" page and uninstalled it. Ever since uninstalling it, every time I click on "File Manager" from the Virtualmin menu, it displays the following error about not being able to find the wordpress folder. I don't understand why it is looking for it in the first place because clicking "File Manager" should take me to into the public_html folder for the VS I have selected, so It shouldn't even be worried about the wordpress folder considering that it should not be trying to enter that directory. It doesn't seem to cause any issue but it is one of those things that is going to drive me nuts until I figure out how to make that error go away...

Screenshot of error: https://i.imgur.com/4TC8Hsb.jpg