Summary
If you receive an FTP error when uploading listings to a portal, the issue is usually related to portal requirements, credentials, connection settings, or temporary outages. Many FTP errors must be resolved by the destination portal rather than Box+Dice.
This article explains common FTP error messages, what they mean, and the recommended next steps.
In this article
General guidance
FTP errors are typically generated by the destination portal.
If the error relates to credentials, connection type, or server availability, you will need to contact the portal’s support team.
If advised, provide the full FTP error message to the portal so they can investigate.
Common FTP errors and resolutions
undefined method 'each' for #
When uploading to REIWA error received
What to do
Contact support to escalate to the Product Team for the internal server error
Broken Pipe
This error means the connection was closed unexpectedly.
The connection may have been terminated by the trading partner, or by a proxy server, router, or firewall between the client and server.
What to do
Contact the portal to confirm the issue.
Ask whether there is a file size limit for uploads.
The "Auction date" provided is invalid
When uploading to REA, listings set to FORTHCOMING AUCTION or AUCTION must include a valid auction date and time.
What to do
Ensure both date and time are entered before uploading.
Listings Property location Map ref is too long (maximum is 4 characters)
This error refers to the Reference field under Advanced Property Information.
What to do
Reduce the reference value to four characters or fewer.
Commercial Property Name of the property is too long (maximum is 20 characters)
This means the property name exceeds the allowed character limit.
What to do
Shorten the property name to 20 characters or fewer.
Residential Property Details for sold listing – Sold Type is invalid
This error indicates the Sale Type has not been entered.
What to do
Open the Sales Details screen and select a Sale Type.
Inappropriate ioctl for device
This error is usually caused by incorrect SFTP configuration.
Possible causes
- Binary Mode is not enabled.
- Incorrect credentials.
- An extra space in the username or password.
What to do
Verify credentials carefully.
Check for accidental spaces.
Confirm Binary Mode requirements with the portal.
NET::SSH::ConnectionTimeout
This error occurs when the client attempts to connect using SSH private keys.
Important
Only SFTP using username and password over port 22 is supported.
Passwords must be 20 characters or fewer.
Connection timed out
The destination portal took too long to accept the connection.
What to do
Wait a few minutes and try again.
You can still upload to other portals individually by clicking each portal name.
Execution expired
The destination website took too long to respond.
What to do
Retry the upload after a few minutes.
Upload other portals individually if required.
getaddrinfo: Name or service not known
This indicates invalid portal connection details.
Possible causes
Incorrect hostname
Incorrect username or password
What to do
Contact the portal and provide the FTP error.
The portal will need to supply updated credentials to Box+Dice.
undefined method 'yearly'
This means pricing information is missing.
What to do
Ensure a Portal Price or Bond Price is entered in Listing Information.
421 Home directory not available – aborting
This error means the supplier’s FTP server is temporarily unavailable.
What to do
Retry later.
Contact the portal if the issue persists.
421 cleartext sessions and weak ciphers are not accepted
421 Please reconnect using TLS security mechanisms
These errors indicate the portal requires explicit TLS/SSL FTP.
Important
Explicit TLS/SSL FTP is not supported.
-
Supported connection types are:
FTP (unencrypted)
SFTP (secure)
What to do
Confirm the portal supports FTP or SFTP.
451 Failure writing to local file
This indicates the FTP user has reached their disk space limit on the portal server.
What to do
Contact the portal to confirm and increase available storage.
500 Illegal PORT command
This means the FTP connection is set to Active mode instead of Passive.
What to do
Update the portal settings to use Passive mode.
550 There is not enough space on the disk
552 Disk Full
The portal’s disk was full at the time of upload.
What to do
Contact the portal to confirm the issue has been resolved.
Retry the upload once space has been cleared..
534 TLS required, configure with AUTH first
This error occurs when Use SFTP connection is not enabled.
What to do
Ensure the Use SFTP option is ticked in portal settings.
AutoExtend is not allowed for your membership type
This indicates an authentication issue with Trade Me.
What to do
Re-authenticate the client.
Confirm they are logged into the correct Trade Me account.
FTP Error: fingerprint SHA256 does not match
SFTP uses SSH fingerprints to verify the remote server.
If a portal changes servers, the fingerprint may no longer match.
What to do
Log a support request to have the old fingerprint entries removed.