Core FTP

---------------

1) -c config.json (does this need a full path?)

2) Try the call without the cmd.exe /c portion.

3) echo %ProgramFiles% out to a file to verify the environment variable is accurate.

If none of these helps then this will be tested further.

There is a global option (view - options - view/edit), "Update edited files on save".

If checked (may require restart), does it change the behavior?

------------------

-----------------

--------

------------------------

Cumulative updates from builds 753-761

This seems to only apply to Linux. Wouldn't be concerned until it is replicated in Windows.

CVE-2024-6387

The reason to use PGP is so nobody but the intended end user can access a file because it is encrypted.

PGP shouldn't be used on the server, its essentially removing the security it provides.

Try unchecking the "PASV" option. If that doesn't work, post the client log showing the error.

----------------

------------------------------

Option added to build 1987 and greater

Install right over your existing setup. As of this post all versions use the same configuration data. Before installing you can backup the following settings for peace of mind: CoreFTPServer\config.dat CoreFTPServer\certs\ -- (copy entire directory, location may also vary, and can be retrieved from ...

--------------------------

---------------------------------

Password should be in the Advanced -> ssh -> password

Check Advanced -> General -> Do'nt prompt for password when empty (checked)

What is the command line you are using....?

Not sure this is an option but it should use the password in your site profile (under advanced -> ssh)

-------------------------

---------------------------

----------------

Update: Build 752 and greater removes -etm hmacs for any default settings.

Cumulative updates from builds 749-752

The Terrapin attack tool indicates ChaCha20 should be avoided. It is not available by default in Core FTP Server and needs to be added manually, so in most cases no action will be needed. If already added, then it should be removed under the "cipher algorithms" settings (SSH/SFTP - "....

add -o for overwrite.

the HTTP protocol may not be available on the new server. Try FTP (with the "AUTH TLS" connection type) on port 21, or SSH/SFTP on port 22.

Did you mean the "Disconnect current connection" message?

There currently isn't but this option can be added.

Cumulative updates from builds 741-743
Corrects zlib/compression issue.

your log will need to demonstrate the error when trying to navigate to the directory in question. There are no obvious errors in this portion of the log.

site profile - advanced - transfers - delete source file after transfer.

or via cmd line: -delsrc

Cumulative updates from builds 735-740

for your log filename, use something similar to:

coreftp%Y%m%d.log

This will generate a new log each day. Select the "daily" or "monthly" option in the log settings.

Select "AUTH TLS" in the "connection type" field.

Select the connection type "AUTH SSL" or "AUTH TLS"

You need the "Force TLS" option checked. This requires at least build 705.

In the test setup here, port 2465 is being used.

www.coreftp.com/server/help/server_license.htm

It is located under "global options" under the system menu.

See the icon in the upper left corner of the GUI. Even if there is not an icon, the menu should still available by right clicking on the menu bar (top of app).

coreftp.com/forums/viewtopic.php?f=1&t=4033836

Upgrade to at least build 694. 711 or 733 (or the latest build) would be better.

Copy over the configuration as described here:

www.coreftp.com/server/help/moving_server.htm

The "certs" subdirectory contains the private key (no extension). You can use openssl with the password you used when creating the "self signed cert" to decrypt it.

Search found 944 matches