EtreCheck Report - FTP problems

tomniama wrote:

So, deleting Malwarebytes will resolve all my FTP problems magicly?

It is such a simple test to find out, it would not make any sense to proceed further without uninstalling to see if it makes a difference. I would also be curious to know if the Configuration profile warning in the report goes away when it is uninstalled. Make sure you use the uninstaller and not just turn it off, and would follow up with another EtreCheck report just to confirm.

I don't have a problem with MalwareBytes and use it myself for one time scans, but would never recommend installing it to run on every startup.

Once that is eliminated, then you can dig deeper into the problems you are experiencing with FTP.

Unfortunately, that update report did not identify what the possible configuration profiles might be.

--------

Consider un-installing Warsaw and testing FTP without Warsaw installed.

you can always re-install Warsaw later if you can not do all your banking by iPhone app.

my first thought was that you have a VPN installed. It does not matter whether it is active or not, merely installing it messes up internet service in a profound way.

sure enough::

System Extensions:

[Running] Malwarebytes Engine - version 5.19.0 (Malwarebytes Corporation - installed 2025-11-21)

Application: /Applications/Malwarebytes.app - version 5.19.0 (Malwarebytes Corporation - installed 2025-11-21)

Description: The Malwarebytes Engine extension manages your connection to the Malwarebytes VPN service.

tomniama wrote:

I use FTP in Adobe Dreamweaver to upload files to my websites. The problems started some weeks ago, sometimes de FTP access works and sometimes not. I have a dedicated server where I host my websites, but the company off course say that it has to be some problem on my side ...

Do you want the website filled with malware and illegal content? Yes, FTP is really that bad. And it’s busted.

FTP is quite literally older than IP networking, and the connections used by FTP are fundamentally incompatible with modern networks, and it openly exposes connection credentials.

Select and test with SFTP: https://helpx.adobe.com/dreamweaver/using/connect-remote-server.html

You have a Samsung 1TB drive, formatted as older and slower MacOS HFS Extended connected, but have Not enabled TRIM to allow it to run at full speed. Also, that disk is too full at 931.86 used out of 999.86 leaving only 6.8 percent free. That number should be closer to 20 percent.

You do not appear to have allowed Etrecheck to have Full Disk Access, so some discovery is limited.

¿What is the date of your most recent backup, and by what method?

tomniama: to use ftp software it has to be configured with the right info to handshake with the host: I use Fetch Softworks as my ftp software to upload my web site to the host. The host changed its hostname recently and also changed the port number and the connection. Only the user name was unchanged. Contacting the host produced the new info and after updating fetch, success in uploading and downloading. Make sure you are using the correct password. The host did not offer a choice in using ftp or sftp, the host tells what it is to connect, so you need to check your settings in Dreamweaver ftp and match what your host specifies.

If having the website spontaneously loaded with garbage or illegal content or defaced is acceptable, then yes do definitely confirm the settings for the server credentials, and also check both passive and active transfers, and check that the security at the inevitable intervening firewalls can allow passage of the credentials-leaking and insecure FTP connection.

Or for less network hassles and as is supported by Dreamweaver and most any web server host, use sftp.

Yes, I am very much an FTP detractor, as the FTP protocol really needs to become an outcast everywhere.

The scan you posted at 1:07 Eastern time is just a small fragment.

The idea that a third party, with no special knowledge of the inner workings of MacOS, can somehow find a simple way to protect or speed up your computer — that is not already being done by MacOS itself — suggests that the MacOS developers are somehow "holding out on you". That is absurd.

You should remove any and all (other than Apple built-in) virus scanners, speeder uppers, optimizers, cleaners, App deleters or VPN packages you installed yourself, or anything of that ilk.

Your exceptionally well-crafted Macintosh computer does not accumulate filth that needs any third-party anything to clean it. Everything needed to run it efficiently was included in the box, except ONE: a drive on which to store a second copy of your files in case the first copy is damaged or deleted by accident. The backup software, Time Machine, is already present -- integrated deeply into MacOS.

Effective defenses against malware and ot… - Apple Community

I am aware that there are FTP problems here, but not what the FTP problems are.

What are the issues with FTP?

I’ll here assume you are aware that FTP is utterly insecure, and uses a design fundamental incompatible with modern networks, and that intervening firewalls can need to be configured to both allow it to pass and preferably also to inspect the connections to avoid opening up vast swaths of the target network port space to contemporaneous shenanigans.

One usual replacement for FTP is SFTP, which shares three letters with and a completely different implementation with FTP, occasionally involves FTPS, and sometimes FTP via a VPN*.

*This would be the traditional business or organization VPN or SDN software-defined network used for connecting directly into the target network of an affiliated organization, and not the over-hyped metadata-collecting “coffee shop” VPNs.

What kind of FTP problems are you having?

FTP is not included in the operating system any more. So by default, any FTP problems are 3rd party software problems.

Furthermore, FTP is crazy complicated. There are many different versions. FTP was designed many, many years ago. It is completely unsuitable for the modern internet. And I'm not just talking about potential security problems. It's very design and how it makes connections is unique.

It's really not surprising that FTP isn't working. It far more surprising that you had it working at any time in the past 20 years. Any kind of system update from your computer, your ISP modem, your Internet connection, your ISP's internet connection, your server, your server's connection could easily break FTP. And when you call all of those people up to complain, not a single one of them will care. They will all tell you to stop using FTP.

This is simply a non-starter. You must find another way.

you are running Warsaw, which I am not familiar with, and it is crashing:

2025-11-29 08:03:17 core Crash (4 times)

    First occurrence: 2025-11-28 10:40:50

    Executable: /usr/local/bin/warsaw/core

FTP is an add-on app, and no longer part of macOS.

In this case, it’s part of Dreamweaver.

And I’d be very surprised if the web server host did not support sftp.

MacOS shares a lot of the lock-down mechanisms developed for the iPhone. Applications are all sand-boxed with a list of the resources they require, and they cannot ask for anything outside their sandbox without crashing. Signed Applications are checked that they are from legitimate Developers, and Notarized Applications are delivered with the assurance that they have NOT been modified since their release by the Developer.

From MacOS 11 Big Sur onward, the system is on a Separate, cryptographically—signed ‘sealed System Volume’. The Mac runs off read-only snapshots of this volume, which is not writeable using ordinary means. Any unauthorized changes to the crypto-signed volume are very quickly detected and you are alerted.

So you could store just about every malware known to mankind on your Mac, and your Mac would not get infected spontaneously. Scanning for virus-like patterns might make you feel a little better now, but non-stop scanning is outdated nonsense, and a tremendous waste of resources.

Nothing can become Executable Unless/Until you supply your Admin password to "make it so".

About the read-only system volume in macOS Catalina or later - Apple Support

About the read-only system volume in macOS Catalina or later - Apple Support

What is a signed system volume? - Apple Support

What is a signed system volume? - Apple Support

Signed system volume security in iOS, iPadOS, and macOS - Apple Support

Signed system volume security - Apple Support

The host sets the rules, when followed, good results happen. Whether there is a better or safer and more secure way is a separate discussion and not a solution and not the question asked.

From what tomniama reported and my own experience, it appears there is a handshake problem and not a software problem. Moving to a new computer should not cause this problem, but there likely has been a change in the OS version, so it's possible there are other elements in play including software compatibility and I hope tomniama will report back.