MacBook Pro M1

Need help with FileZilla Client? Something does not work as expected? In this forum you may find an answer.

Moderator: Project members

Message
Author
pminx
500 Command not understood
Posts: 1
Joined: 2021-01-06 17:00
First name: Patrick
Last name: Minx

MacBook Pro M1

#1 Post by pminx » 2021-01-06 17:09

I have a new MacBook Pro M1 with Big Sur v11.1. I got Filezilla to work fine on my PC and my old MacBook Pro, but the MacBook M1 gives the Error: fzsftp could not be started Error: Could not connect to server. I was wondering if anyone else has had issues with the latest M1 chip? Thanks.

Sabrina520
500 Command not understood
Posts: 1
Joined: 2021-01-06 17:11
First name: Sabrina
Last name: Montenegro

Re: MacBook Pro M1

#2 Post by Sabrina520 » 2021-01-06 17:16

I'm having the same issue, I've been using the same mac book. Was able to get on before.

User avatar
boco
Contributor
Posts: 25500
Joined: 2006-05-01 03:28
Location: Germany

Re: MacBook Pro M1

#3 Post by boco » 2021-01-06 22:10

M1 chip is an entirely different architecture (ARM-based). There is no native FileZilla for ARM, and there possibly never will be.

Of course, there's Rosetta 2, looks like there are still some problems and incompatibilities. If they can be resolved needs to be determined by the dev, but probably, Apple needs to take action. Should they at one point decide to remove the Rosetta emulator completely (as they've done before with Rosetta 1), FileZilla on Mac would vanish.
### BEGIN SIGNATURE BLOCK ###
No support requests per PM! You will NOT get any reply!!!
FTP connection problems? Do yourself a favor and read Network Configuration.
FileZilla connection test: https://filezilla-project.org/conntest.php
### END SIGNATURE BLOCK ###

User avatar
botg
Site Admin
Posts: 33424
Joined: 2004-02-23 20:49
First name: Tim
Last name: Kosse
Contact:

Re: MacBook Pro M1

#4 Post by botg » 2021-01-07 01:15

Make sure to update to the most recent version of FileZilla.

A native build for ARM-based Macintosh PCs will come soon after such devices are available in stores that accept SEPA payments.

shydul
500 Command not understood
Posts: 1
Joined: 2021-01-16 07:38

Re: MacBook Pro M1

#5 Post by shydul » 2021-01-16 07:43

I'm running FileZilla without issue on macOS 11.1 on a Mac mini m1.

User avatar
boco
Contributor
Posts: 25500
Joined: 2006-05-01 03:28
Location: Germany

Re: MacBook Pro M1

#6 Post by boco » 2021-01-16 23:27

Try connecting to an SFTP server. Does it work?
### BEGIN SIGNATURE BLOCK ###
No support requests per PM! You will NOT get any reply!!!
FTP connection problems? Do yourself a favor and read Network Configuration.
FileZilla connection test: https://filezilla-project.org/conntest.php
### END SIGNATURE BLOCK ###

joeyre
500 Command not understood
Posts: 1
Joined: 2021-01-20 08:49
First name: Jo
Last name: Eyre

Re: MacBook Pro M1

#7 Post by joeyre » 2021-01-20 08:51

I had this issue on my mac mini M1 (specifically with sftp not ftp), but I closed down Filezilla, then opened it again and it connected this time.

dbdulin
500 Command not understood
Posts: 1
Joined: 2021-02-01 17:44
First name: Don
Last name: Dulin

Re: MacBook Pro M1

#8 Post by dbdulin » 2021-02-03 17:50

Hi All, I have a Mac Mini with M1 running 11.2 and FileZilla Pro 3.52.2. I can connect just fine, but there are a few files that consistently fail to upload. My experience with this, thus far, is limited to Wordpress uploads. The files that fail consistently are:

public_html/wp-admin/admin.php
public_html/wp-includes/js/tinymce/plugins/hr/plugin.js

On the same network, I can, with no issues, upload the entire WP file set using my 2009 Mac Pro running 10.14.6

User avatar
TalkShowGhost
504 Command not implemented
Posts: 6
Joined: 2021-03-20 14:19

Re: MacBook Pro M1

#9 Post by TalkShowGhost » 2021-03-20 14:46

Out of curiosity I tried making an arm64 build of FileZilla myself and it works perfectly fine using homebrew for the dependencies (except for libfilezilla of course) and the latest svn trunk source code. Built with no issues at all, the only tricky bit was working around an extremely annoying code signing bug (it's happened to me before) which will cause codesign_allocate to crash. All you have to do to work around it is copy the file that's causing it to crash to another directory, sign it there, delete the original file, and then move the signed copy back in. I had to do that with libidn.12.dylib, libfilezilla.12.dylib, and libwx_osx_cocoau_adv-3.0.0.5.0.dylib.

If you don't want to bother with all that, I uploaded the version I made here (using itself, of course): https://shermanikk.net/stuff/FileZilla-macos-arm64.zip

Usual caveats with untested builds applies, I don't promise this won't set your dog on fire and turn the sun into a black hole or cause diabetes, etc.

Image Image

User avatar
botg
Site Admin
Posts: 33424
Joined: 2004-02-23 20:49
First name: Tim
Last name: Kosse
Contact:

Re: MacBook Pro M1

#10 Post by botg » 2021-03-22 09:45

Your build does not seem fine, various texts in the UI are truncated.

User avatar
TalkShowGhost
504 Command not implemented
Posts: 6
Joined: 2021-03-20 14:19

Re: MacBook Pro M1

#11 Post by TalkShowGhost » 2021-03-22 16:03

botg wrote:
2021-03-22 09:45
Your build does not seem fine, various texts in the UI are truncated.
Where? The only one I can see is the compiled on/for lines in the about dialog, and that's just because it's longer. Checked all the context menus, preferences, etc. and it all looks fine. Some screenshots for comparison would help. Also what scaled resolution are you running? I took all those screenshots at 1680x1050 on an M1 MacBook Air.

User avatar
TalkShowGhost
504 Command not implemented
Posts: 6
Joined: 2021-03-20 14:19

Re: MacBook Pro M1

#12 Post by TalkShowGhost » 2021-03-22 21:11

sorry for the double post, I went back and looked and you are right. There's something very odd about the font rendering for some UI elements, note the tabs for the file transfer lists at the bottom of the window:

Original Intel Build:
Image

My Apple Silicon Build:
Image

For some baffling reason, my build is using some random serif font that doesn't match the rest of the UI, while the Intel one does. That's what's causing the truncating issue, as seen on the "Successful transf..." tab. I think it may have something to do with using the Homebrew build of wxWidgets so I'm going to do a manual build of version 3.0.5.1 (same as the official release uses) following the wiki and see if that fixes it.

edit: and this rabbit hole seems to go deeper, checking the About box in the official build says it's using wxWidgets 3.0.6 which doesn't fucking exist. Latest stable version is 3.0.5.1 and development is 3.1.4 (and also doesn't work with FZ at all). I went and grabbed the source to the same build, 3.53.1 and it still has the same font issue as the svn trunk version. I'm 100% sure this is a problem with wxWidgets but unless I'm insane, there's something very odd going on.

User avatar
botg
Site Admin
Posts: 33424
Joined: 2004-02-23 20:49
First name: Tim
Last name: Kosse
Contact:

Re: MacBook Pro M1

#13 Post by botg » 2021-03-23 08:49


User avatar
TalkShowGhost
504 Command not implemented
Posts: 6
Joined: 2021-03-20 14:19

Re: MacBook Pro M1

#14 Post by TalkShowGhost » 2021-03-28 06:54

Sorry it took me a while to try this out, just been busy. Finally had some free time though. It seems to have fixed the incorrect font usage in the transfers area that was causing the truncated tab labels, but the "About" page seems even more messed up. Other than that one issue, everything else looks good to me. Here's my latest build that includes this magic patch: https://shermanikk.net/stuff/FileZilla-macos-arm64.zip

Hopefully that's done it for you as well!

Image

User avatar
TalkShowGhost
504 Command not implemented
Posts: 6
Joined: 2021-03-20 14:19

Re: MacBook Pro M1

#15 Post by TalkShowGhost » 2021-03-31 05:27

Here's what the about page looks like for me, does it look like this for others? I'm running at 1680x1050 scaled resolution on a 13" MBA.
O43GsZ6.png
O43GsZ6.png (597.15 KiB) Viewed 886 times

Post Reply