You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I must first state that this may or may not be a Cyberduck issue - but I am in a VERY big argument with my webhost that claims that this is a CyberDuck problem.
Infrequently, about 30 files show up in the root/www dir of my hosting account. The filenames are identical each time and have names like 1.jpg (up to 11.jpg), and (humm1.jpg up to humm10.jpg). The odd thing (other than they mysteriously show up) is that they are size 0 bytes.
I have searched my computer, and have no files with such names. The webhost claims that the only way they could show up is via CyberDuck, and recommend that I stop using it. (I do not share this view.)
Is there any way that I might have accidentally put Cyberduck into a debug mode of some sort to cause this issue? Otherwise, is there anyway Cyberduck could be sending files without my initiating the action?
The text was updated successfully, but these errors were encountered:
I must first state that this may or may not be a Cyberduck issue - but I am in a VERY big argument with my webhost that claims that this is a CyberDuck problem.
Infrequently, about 30 files show up in the root/www dir of my hosting account. The filenames are identical each time and have names like 1.jpg (up to 11.jpg), and (humm1.jpg up to humm10.jpg). The odd thing (other than they mysteriously show up) is that they are size 0 bytes.
I have searched my computer, and have no files with such names. The webhost claims that the only way they could show up is via CyberDuck, and recommend that I stop using it. (I do not share this view.)
Is there any way that I might have accidentally put Cyberduck into a debug mode of some sort to cause this issue? Otherwise, is there anyway Cyberduck could be sending files without my initiating the action?
The text was updated successfully, but these errors were encountered: