FAQ - GigaMove

Please check the following:

1. Are the necessary cookies (such as the Shibboleth Identity Provider of your home institution, the DFN Discovery Service, and the Shibboleth Service Provider on the GigaMove server) enabled?

2. Is Shibboleth authentication working? Usually, it is sufficient to use the Shibboleth Service Provider of your home institution.

3. If Shibboleth authentication is working but access is still not possible, it could be due to two reasons:

• The Shibboleth Identity Provider may not be registered with DFN.
• The Shibboleth Identity Provider of your home institution may not provide all required information. You can find the information that is transmitted under this link.

4. Is there a firewall or proxy blocking access?

5. Does your router support TCP connections or only UDP?

The entire application uses the HTTPS protocol to transfer data securely.

Additionally, the following options can be used:

• Protect files with a password
• Password-protected archive
• Encrypt file(s)
• Delete files immediately after download

Only you and persons who have the link can access the data provided. 

The administrators of the system have access to the server and the file system, but access to the data by an administrator by service instruction without good reason is prohibited.

To prevent access by administrators, you can encrypt your data before uploading it. 

This may be caused by the following:

1. A virus may have been found in the file This file is deleted immediately after detection.

2. Possibly the validity of the file has expired.

If your home router only uses UDP for name queries, you may experience issues accessing the storage services. In this case, you might receive an error message stating that an address like "*.s3.fds.rwth-aachen.de" cannot be resolved (ERR_NAME_NOT_RESOLVED).

We recommend updating your home router in such cases so that it can also use TCP.

To use the storage services without restrictions, both UDP and TCP must be supported for name queries. This complies with the DNS standard, which requires that both protocols are available.