How it works

A FTP server provides interactive access for DOOR users to beamtime directories using the FTP protocol. It allows you to browse and download beam time data using any suitable FTP client. Access is granted according to the working group definitions in the Gamma Portal. As we are using a secure implementation of the FTP protocol, you might have to configure your client. You can find configuration examples below, see Configuring FTP clients.The FTP server uses a port range of 30000 - 32000 to transfer data. These ports need to be open for outgoing traffic at the receiving site, wich is usually the case.

To access your data:

  1. Use the 'FTP Configuration' menu entry of the  Gamma Portal  to select a specific beam time you want to access and click 'FTP register'. If you do not select a beam time, the FTP server will point you to a README file. See 'testing the service' below.
  2. Use a suitable FTP client  to connect to We tested our setup using filezilla,lftp anf fireftp. See Configuring FTP clients below for some information on these clients.

  3. Use your DOOR account to authenticate to the FTP server. DOOR user names and passwords are case sensitive.

  4. If you want to access a different beam time, simply log out of the FTP server, use the 'FTP Configuration' menu again to de-register the old beam time and register for the new one, then log in to the FTP server and thus to the new beam time.

 Testing the service without having done a beam time yet:

  1. If you have a DOOR or DESY account, you can verify that the service works for you.
  2. Just connect to the service using a FTP client e.g. filezilla.
  3. Right-klick on the file named README.txt
  4. A text editor should open and display a short hint.

Configuring FTP clients

Access to is encrypted to protect your privacy. To connect to the server for the first time, you need to accept the servers certificate and - depending on the client you use - the certificates of the signing organizations. We tested the following clients and describe the steps to take.

Note: On windows systems, we recommend using filezilla instead of winSCP due to lower performance and frequent reconnects of win SCP.

filezilla (Linux, Windows)



Usage example

lftp (Linux)



lftp needs to be configured by the user to trust the certificate chain:

mkdir ~/.lftp/certs
# Add the trust chain for DFN issued certificates
# NOTE: This can only be done from a IPv4 aware system.
#       From a IPv6 only system, this currently does not work.
curl > ~/.lftp/certs/desy.pem
# Activate them:
echo 'set ssl:ca-file "~/.lftp/certs/desy.pem"' >> ~/.lftp/rc

The servers welcome message might hint to maintenances or other events of interest. If you do not see the message, you can add a line containing debug 3 to your lftp configuration file, ~/.lftp/rc. An example file might look as follows:

set ssl:ca-file "~/.lftp/certs/desy.pem"
debug 3

Usage example


fireftp (firefox plugin; works on all systems supported by firefox)


NOTE: fireFTP is not available with the latest versions of firefox, starting with Quantum (v 57.0). The developer has discontinued the product (see




To use it with, you need to import the certificate chain into your browser. To do this, go to;name=download_cacert and import the certificates presented there into firefox by simply clicking on them. Then start fireftp.


With large number of files and directories, fireftp will take a huge amount of time setting up and use up large amounts of RAM. With a 8.7 million file beamtime, the setup phase took more than 24 hours with more than 7 GB memory consumption.