web disk not working

[JamieD]

I thought I would try out the web disk feature but have found that it is not working. I have opened up the ports 2077 & 2078 on the firewall, I even disabled the firewall temporarily just to make sure, but I can not connect.

I am using OS X 10.4.9 and have tried downloading the web disk script through cPanel and also connecting to http://domain.com:2077 & https://domain.com:2078 through the finders "connect to server" and also in the browser.

Looks like the server is not responding for some reason.

[cpanelkenneth]

What error is returned when attempting to conenct?

[JamieD]

Hi kenneth,

No error is returned, its as if the server is not responding or the web disk service is not running. When running the OS X setup I get an error saying I must accept the certificate but no certificate acceptance dialogue pops up, after looking at the script I think this is probably due to the server not responding.

[cpanelnick]

Sounds like a firewall problem.

[mitgib]

Actually I have a server running FC4 that web disk works perfect on after opening ports 2077 and 2078, but on another server running FC5 I cannot get it working

[JamieD]

Hi Nick,

Its not a firewall problem, I completely disabled the firewall and still had the same response. I have now updated to the latest current release and I am able to get a bit further that with the previous release.

When I run the script now I am prompted to accept the certificate then for my user-name and password, after which I am told I must accept the certificate.

If I try to connect directly through the finder I enter my user-name and password and then get the message "You cannot connect to this server because it cannot be found on the network.... This happens no matter if I have turned the firewall off or not.

[cpanelnick]

1) Is cpdavd running ??

ps uxaww|grep cpdavd


2) Do you have 2077 or 2078 blocked on your server with iptables?

[mitgib]

1) Is cpdavd running ??

ps uxaww|grep cpdavd


2) Do you have 2077 or 2078 blocked on your server with iptables?

I do not have cpdavd, and get the following errors trying to restart

]# /etc/init.d/cpanel restart
Stopping cPanel services:  Waiting for cpsrvd to shutdown......Done
Waiting for cpsrvd-ssl to shutdown......Done
                                                           [  OK  ]
Stopping cPanel dav services:  Waiting for cpdavd to shutdown......Done
Waiting for cpdavd-ssl to shutdown......Done
                                                           [  OK  ]
Stopping cPanel brute force detector services:  Name "Cpanel::Hulkd::ERRLOG" used only once: possible typo at  line 86.
Waiting for cphulkd.pl to shutdown......Done
Waiting for cPhulkd to shutdown......Done
                                                           [  OK  ]
Stopping pop3 services:  Waiting for cppop to shutdown......Done
Waiting for cppop-ssl to shutdown......Done
                                                           [  OK  ]
Stopping cPanel log services:                              [FAILED]
Stopping cPanel Chat services:                             [  OK  ]
Stopping Melange Chat services:                            [FAILED]
Stopping InterChange services:                             [FAILED]
Stopping cPanel ssl services:                              [  OK  ]

Stopping mailman services: Shutting down Mailman's master qrunner

Starting eximstats:                                        [  OK  ]
Starting cPanel services:                                  [  OK  ]
Starting cPanel brute force detector services:             [  OK  ]
Starting cPanel dav services:                              [FAILED]
Starting cPanel Log services: (internal death) Mon May 14 17:48:34 2007 [15817] error: (internal death) Mon May 14 17:48:34 2007 [15817] error: (internal death) Mon May 14 17:48:34 2007 [15817] error: (internal death) Mon May 14 17:48:34 2007 [15817] error: (internal death) Mon May 14 17:48:34 2007 [15817] error: (internal death) Mon May 14 17:48:34 2007 [15817] error: (internal death) Mon May 14 17:48:34 2007 [15817] error: (internal death) Mon May 14 17:48:34 2007 [15817] error: Can't locate YAML/Syck.pm in @INC (@INC contains: /usr/local/cpanel /usr/local/cpanel/3rdparty/lib/perl /usr/lib/perl5/site_perl/5.8.8/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.7/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.6/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.4/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.3/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.8 /usr/lib/perl5/site_perl/5.8.7 /usr/lib/perl5/site_perl/5.8.6 /usr/lib/perl5/site_perl/5.8.5 /usr/lib/perl5/site_perl/5.8.4 /usr/lib/perl5/site_perl/5.8.3 /usr/lib/perl5/site_perl /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.7/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.6/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.4/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.3/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.8 /usr/lib/perl5/vendor_perl/5.8.7 /usr/lib/perl5/vendor_perl/5.8.6 /usr/lib/perl5/vendor_perl/5.8.5 /usr/lib/perl5/vendor_perl/5.8.4 /usr/lib/perl5/vendor_perl/5.8.3 /usr/lib/perl5/vendor_perl /usr/lib/perl5/5.8.8/i386-linux-thread-multi /usr/lib/perl5/5.8.8 .) at /usr/local/cpanel/Cpanel/DataStore.pm line 11.
BEGIN failed--compilation aborted at /usr/local/cpanel/Cpanel/DataStore.pm line 11.
Compilation failed in require at /usr/local/cpanel/Cpanel/NotifyDB.pm line 10.
BEGIN failed--compilation aborted at /usr/local/cpanel/Cpanel/NotifyDB.pm line 10.
Compilation failed in require at /usr/local/cpanel/Cpanel/BandwidthMgr.pm line 11.
BEGIN failed--compilation aborted at /usr/local/cpanel/Cpanel/BandwidthMgr.pm line 11.
Compilation failed in require at /usr/local/cpanel/cpanellogd line 26.
BEGIN failed--compilation aborted at /usr/local/cpanel/cpanellogd line 26.
[a fatal error or timeout occurred while processing this directive][a fatal error or timeout occurred while processing this directive][a fatal error or timeout occurred while processing this directive][a fatal error or timeout occurred while processing this directive][a fatal error or timeout occurred while processing this directive][a fatal error or timeout occurred while processing this directive][a fatal error or timeout occurred while processing this directive][a fatal error or timeout occurred while processing this directive]   [FAILED]
Starting pop3 services: Waiting for cppop to shutdown......Done
Waiting for cppop-ssl to shutdown......Done
                                                           [  OK  ]
Starting cPanel Chat services: Listening on port 2084...
                                                           [  OK  ]
Starting Melange Chat services:
Starting cPanel ssl services: Using Native SSL support (stunnel not needed)
                                                           [  OK  ]
Starting mailman services: Starting Mailman's master qrunner.

This is after running upcp --force as well

[mitgib]

I managed to solve my troubled on the FC5 server, I have compat-gcc-32 installed to get mod_gzip to work in apache, reverting back to gcc 4.1.1 and running upcp --force one more time set all the perlmods straight

[upsforum]

In my case I enable port 2078 in conf.apf

# Common inbound (ingress) TCP ports
IG_TCP_CPORTS="20,2..........,3306,6666,2077,2078"

# Common outbound (egress) TCP ports
EG_TCP_CPORTS="2...........89,3306,2077,2078"


I think that this secure!!!??

[stepper]

hi - I have managed to get osx finder working with webdisk after opening ports 2077/2078 as described above - thanks..

it works fine for
- opening files
- renaming files
- moving files

however I am getting some errors when trying to do the following
- delete a file
- rename a directory
- delete a directory

I have tested with another app (transmit using dav) so I know its not finder that is causing the problem. Transmit reports the error as "Could not read status line: connection was closed by server". Finder just freaks out and hangs for 10 minutes. this happens both on a secure and unsecure connection.

Tested with winxp too and get non-descriptive errors too so its either a cpanel dav, apache or firewall issue??


ps - I wasn't able to get it working with Iptables, I disabled that and installed apf on my server to get it working.

[mdechgan]

I have the same problem with web disk.

I turned off all firewalls, even using the dmz.

I tried http://domain:2077 and https://domain:2078
It just doesn't connect.

ie could not open http://domain:2077 as a web folder. would you like to see its default view instead?

I click yes and its says there is a problem connecting to the webdisk service make sure ports 2077 and 2078 are open.

These ports are open tcp and udp. I even turned off all firewalls entered a dmz.
by the way I'm using windows xp and cp11 host server.

[Silver_2000]

hi - I have managed to get osx finder working with webdisk after opening ports 2077/2078 as described above - thanks..

it works fine for
- opening files
- renaming files
- moving files

however I am getting some errors when trying to do the following
- delete a file
- rename a directory
- delete a directory

I have tested with another app (transmit using dav) so I know its not finder that is causing the problem. Transmit reports the error as "Could not read status line: connection was closed by server". Finder just freaks out and hangs for 10 minutes. this happens both on a secure and unsecure connection.

Tested with winxp too and get non-descriptive errors too so its either a cpanel dav, apache or firewall issue??


ps - I wasn't able to get it working with Iptables, I disabled that and installed apf on my server to get it working.

Im using windows and ALSO cant delete files once I put them in the web folder

[myusername]

I too cannot delete files using WinXP.

My understanding is you are also supposed to be able to "save as" files directly to webDAV (I guess not available in webdisk?) not just drag and drop them in. You are also supposed to be able open them from the network drive so that editing operations can be performed.

In other words, it is supposed to be read/write from the local PC to the server.

I have not tinkered around on other OS yet, but it definitely does not work in XP.

I thought I saw a link in the control panel at some point that lead to a MS patch for webDAV. Can't seem to find it now but, not sure if it would help though as I do not know if it will even solve the issue.

So is there a plan for full webDAV support or is the plan to only offer drag and drop / copy and paste, or is this an OS issue?

Anyone from cPanel have any contributions on this?

[NilsGN]

Hi,
I'we hawe done some testing now for a couple of days and this is wath I came up to;

- On My LapTop, with OS WinXP MCE and NIS 2006: In explorer - "attach network server" - i wrote: http://domain.com:2077 and hit enter. The cPanel WebDisk login appear. I set the foldername and then I was in!

- On My wifes PC, with OS W2K SP3 and NIS 2003 i get the same result. Some little difference. NIS notice that the rundll32.exe want TCP out. After that it all works fine

- On my Workstation with OS WinXP HE SP2 and NIS 2004. I get in touch with My account via the WebBrowser IE6, no problem when i wrote: http://domain.com:2077 - login appear - and I'm in.
From explorer and "attach network server" I got problem. After I write: http://domain.com:2077 I get de cPanel WebDisk login, but affter that i get an 'error'. I says: "Den angivna mappen verkar inte vara giltig. Välj en annan mapp." That is swedish, i translate: "The staded folder do not seems to be valid. Try another one."

And there I am now.

The conclusion so far is that the problem is not in the FireWall (NIS). The problem seems to be in some part of the OS WinXP HE SP2.

In the writing moment i try to see if I can set some trusts to the file rundll32.exe and see if that helps...

... it's take a while.

OK, now I have set rules to rundll32.exe to allow TCP out communication specific wirh my domain.com and port 2077.

Now it is exciting...

...damned!

OK, folks... any ideas?