Note: This article pertains to Transport units with SarOS firmware.
When uploading a file on a TransPort (for example when trying to use the router as a OVPN server or client and you need to upload the Key and Certificates files), issues can be encountered, no matter which protocol is used for the upload.
For example you can get a write error using SCP:
![User-added image](https://818164.app.netsuite.com/core/media/media.nl?id=464133&c=818164&h=3642aed72fb933faa802)
![User-added image](https://818164.app.netsuite.com/core/media/media.nl?id=464181&c=818164&h=a9f79e3a114ca70347db)
Or also if trying to upload a key file using the WEB interface (Administration - X.509 Certificate Management > Key files):
![User-added image](https://818164.app.netsuite.com/core/media/media.nl?id=464270&c=818164&h=49c425c9d21e2b80b092)
Most of the times, that is not depending on the protocol used (FTP, WEB, SCP) nor on the file type (.zip,.jpg,.crt,etc), but, instead, is due to the file name format being not accepted from te system.
On TransPort routers, the '8.3' filename format has to be used. That means that every filename should have a maximum of 8 characters before the '.' plus a maximum of 3 characters for the extension. Very often the issue is that the first part is exceeding this limit of “8”, so the first thing to try in those situations is to use a file name compliant with the 8.3 format.
Last updated:
Jan 03, 2024