WebFM Functionality works, while at the same time giving "server is unreachable" error in file browser
| Project: | Web File Manager |
| Version: | 6.x-2.11 |
| Component: | User interface |
| Category: | support request |
| Priority: | critical |
| Assigned: | negiti |
| Status: | active |
Jump to:
Hello all,
I have a Drupal 6.13/PHP5/MySQL5 environment using WebFM 2.11. Early on, there were problems with the file browser alternately working, and then coming up as "server is unreachable". I was working with an associate on bringing the site up at that time, and frankly forget what if anything we did to correct the problem - if anything, it would have been directory assignments.
The site and WebFM has been working perfectly for almost a month, and no updates have been done recently. Today, I tried to access the file browser/manager and am getting the "server is unreachable" message, although the files being managed by WebFM are fully accessible, and access is very fast.
I have seen a number of posts regarding this issue, but (and maybe it's me) have not seen a solid course of action to 'make the pain go away'.
Any insights are gratefully received.
-Joe
#1
ADDENDUM: I attempted to use the File Upload function in an effort to feel out the symptoms and extent to which this issue is/was occurring.
The Filre Browser is now as a result perpetually displaying "Working... please wait".
As one might expect, disabling the module interrupts the file hosting, causing a "content not found" error. Reenabling the module brings the hosting functionality online (again, as expected), but the "Working,,, please wait" error message comes back with it.
Again, any help . . .
#2
ADDENDUM 2: I am running IE8 and FireFox 3.5 on my primary computer. I logged into my remote, running FFox 3.0x, and the File Browser works fine.
?!?
#3
Oddly enough I've seen a similar problem with one of my sites and fixed by simply going to the settings page and re-saving the configuration. The behaviour isn't consistent and I haven't had the time to find a solution. Next time I see it happen I'll try to debug.