SIRAS creates a district/LEA SFTP account and provides the password securely. Before configuring an automated SIS process, confirm that someone at the district can sign in manually and access the folder.
Think of the SFTP site as a secure remote folder in the cloud. SIRAS and the district can place sensitive integration files there without sending them through ordinary email. An SFTP client is simply an application that lets you sign in to that remote folder, similar to using File Explorer for files on your computer.
If SFTP clients, ports, or firewall settings are unfamiliar, involve your district IT or technology staff. They are welcome to contact SIRAS if they need assistance with the connection.
Contents
| Connection SettingsHost, port, username, password, and protocol. | Test Manual Access FirstProve the connection before automating it. |
| What the SFTP Folder Is Used ForAeries credentials, file-based imports, and SIRAS exports. | Timeouts & Firewall IssuesWhat to check when the login information is correct but the server does not respond. |
| Credentials & ChangesHow the password is used and how to provide replacement credentials securely. | Other TroubleshootingAuthentication, folders, files, and scheduled jobs. |
Standard SIRAS SFTP Connection Settings
| Setting | Value |
|---|---|
| Protocol | SFTP |
| Server / Host | ftp.sirassystems.org |
| Port | 7472 |
| Username | The LEA's 7-digit County-District (CD) code, unless SIRAS provides a different username for the account. |
| Password | The district-specific SFTP password provided securely by SIRAS. |
| Remote directory | Start in the account's default folder unless SIRAS provides a specific subfolder or path for the integration. |
The SIRAS integration server uses SFTP on port 7472. If your software presents FTP, FTPS, and SFTP as separate choices, select SFTP.
The district's seven-digit County-District code can be looked up in the California School Directory.
Test Manual SFTP Access Before Configuring Automation
As soon as SIRAS provides the district's SFTP password, have the district technical contact test the connection using an SFTP client such as WinSCP or another client approved by the district.
- Open the SFTP client and create a new connection.
- Select SFTP as the protocol.
- Enter
ftp.sirassystems.org. - Enter port
7472. - Enter the district username and SFTP password.
- Connect to the server.
- Confirm that the district's SFTP location opens.
- When appropriate for the integration, upload and/or download a small approved test file.
The district can connect manually to the SIRAS SFTP site and access the expected location. Do this before spending time configuring an API credential delivery, SIS scheduled import, demographic/contact file process, or other automation.
There is no expectation that every SIRAS administrator should know how to configure an SFTP client or troubleshoot a network. Ask the district's IT/network staff to assist with this connection step when needed.
What the SFTP Folder Is Used For
The same secure SFTP workspace can support several different parts of an SIS integration.
| Use | How the SFTP folder is involved |
|---|---|
| Aeries → SIRAS API setup | After the district creates the Aeries API credential using Aeries' SIRAS integration instructions, place the credential information in a text file and upload it to the district SFTP folder. Do not email the API credential to SIRAS. The non-secret Aeries login/base URL can be emailed separately to SIRAS. |
| File-based SIS → SIRAS | The district or SIS process places approved demographic, enrollment, contact, or other import files in the SFTP location for SIRAS to process. |
| SIRAS → SIS | SIRAS places generated export files in the SFTP location so the district SIS or scheduled process can retrieve them. |
| SIRAS → Aeries | Aeries retrieves the SIRAS Special Ed Data Import files from the district's SFTP location. The Aeries configuration uses the same district SFTP password that was first tested with the manual SFTP connection. |
| Credential replacement | If an API key or other approved integration credential must be replaced, the district can place the new information securely in the SFTP folder and tell SIRAS that the replacement is ready. |
This is why Aeries onboarding can feel confusing: the same SFTP username/password may first be used by a person signing into the secure folder and later be entered into Aeries so Aeries can retrieve SIRAS-generated files. The credentials are the same; the purpose of each connection is different.
Credentials, Passwords & Changes
SIRAS creates the LEA SFTP account and provides its password securely. Keep the credential available to the district technical staff who are responsible for the integration.
- Do not send the SFTP password, API keys, or private credentials through ordinary email.
- The same district SFTP password may be used by an approved automated SIS connection after the manual connection has been tested.
- If the district needs the SFTP password changed, contact SIRAS.
- If an Aeries API credential changes, upload the replacement securely to the SFTP folder and notify SIRAS that it is available.
- When technical staff or vendors change, review who still needs access and rotate credentials when appropriate.
Connection Times Out or the Host Does Not Respond
If the district has verified that the server, port, username, password, and SFTP protocol are correct, but the client still shows a timeout, waiting-for-host, host-not-responding, or similar connection message, the problem may be on the district network rather than with the SFTP credentials.
A district firewall or other network security rule may block SFTP traffic to
ftp.sirassystems.org on port 7472. The network administrator may need to permit that outbound connection before the SFTP client or automated SIS process can reach the server.
A useful troubleshooting sequence is:
- Confirm the connection is using SFTP.
- Confirm host
ftp.sirassystems.organd port7472. - Confirm the username/password were entered correctly.
- If the connection still waits or times out before authentication, involve district IT/network staff and have them review firewall or outbound network rules for port 7472.
- After any firewall change, retry the manual SFTP connection before returning to the automated SIS configuration.
After the network change, the SFTP client should reach the server and proceed to authentication/login. Once manual access works, continue with the appropriate integration setup.
Other SFTP Troubleshooting
| Problem | What to check |
|---|---|
| Authentication failed / access denied | Verify the district username and SFTP password. Confirm that an old saved password is not being reused. |
| Unexpected host-key warning | Do not automatically accept an unexpected changed host key. Confirm the server identity with district IT or SIRAS. |
| Login works but expected files are not present | Confirm the correct account/location, expected file-generation time, data direction, and whether the relevant SIRAS or district process has already run. |
| Manual SFTP works but an SIS scheduled process does not | Compare the automated job's protocol, server, port, username, password, directory, schedule, and network execution environment with the connection that worked manually. |
| A credential was changed | Confirm that both the manual connection profile and any automated SIS process were updated when appropriate. |
If the settings appear correct and the issue remains unresolved, have the district technical contact provide SIRAS with the district name, approximate time of the attempt, exact error message, whether manual SFTP access works, and which integration process is being configured. Do not include the SFTP password in the support message.
What Comes After SFTP Access Works?
SFTP access is an early integration milestone, not the entire integration. Continue with the workflow that applies to the district:

