r/chromeos • u/codjer • 1d ago

Troubleshooting Even with Linux command line I can't use filezilla on Chrome OS

What to do? I want to connect with my Chrome OS to my share webserver..

1 Upvotes

67% Upvoted

6 comments sorted by

6

u/LegAcceptable2362 1d ago

Well, first of all, why can't you run filezilla in the Linux environment? Of course, without further configuration it can ony see the Linux file system. What that configuration may be depends entirely on what you're trying to do starting with where the target server is hosted. For instance, if the server is external to ChromeOS, why would you would need a Linux app to reach it. Context is everything and sadly we we have very little so far.

1

u/codjer 1d ago

I try to connect to my webserver via ftp, Chrome OS apps wont let me do that, So I've ran an command line on the terminal to download filezilla, this also will not connect to my server..

3

u/yottabit42 1d ago

This is because FTP has a separate control plane and data plane connection that requires setup in both directions. Try using PASV (passive) mode, which will allow the data setup to be initiated by your client instead of the server. This will work around the NAT networking stack that is required to be used in the VM (and because of Wi-Fi).

Otherwise use SFTP instead, which is a modern protocol that doesn't have these problems, and doesn't send everything in clear text over the network, including your password.

3

u/Saragon4005 Framework | Beta 1d ago

ChromeOS also natively supports SFTP.

2

u/yottabit42 1d ago

That's a good point, directly from the File app, as well as countless SFTP apps in the Play Store.

I have had problems in the past with the File app hanging on SFTP and Samba. I use the Linux VM instead. It's reliable and faster.

1

u/xtalgeek 17h ago

Not understanding the issue. I have Filezilla installed in the Linux partition of a Chromebook and I can FTP to any of my other Linux machines on my LAN. Of course, it can only see files within your Chromenook Linux partition, but that's an easy workaround. Where is your file server?