FTP Uploaded Photos to Synology Have No File Ex.

[haightjr]

When viewing the shared folder on my windows machine and within Synology web all the image, keogram and timelapse files are missing the extension. I have to rename each file with the extension. I've looked through all the documentation and searched the internet with no luck. Anyone run into this issue? I am not hosting a site, just uploading to my nas for archival purposes.

[EricClaeys]

If you ftp into the NAS to view the list of files, are the extensions there?
By default, Windows will hide extensions.

[haightjr]

They are not assigned an extension. Type=File. I would also love to see the photos that come in go into daily folders as well which is not happening when they are sent to the ftp folder.

[EricClaeys]

It looks like most of your uploads are failing part way through. When Allsky uploads an image.jpg file, it first uploads the file using a temporary name like SaveImage-12345. It then tells the ftp server to rename the file to the real name. The rename appears to be failing.
Please run a test upload using the instructions at the end of the Troubleshooting -> Uploads documentation page and see what it says.

Allsky doesn't currently have the ability to archive files into separate folders on an ftp server as you would like it to.

[haightjr]

I think I sorted it out. Thank you so much for the guidance.

[haightjr]

I do have another question though. Photos from the allsky camera are now going to the nas share and properly named. I see the timelapse was created and placed in the video folder but the previous days photos are sitting in the root directory and not moved to a dated folder like you see in the raspberry pi directory. How do I go about fixing that minor issue? Thanks.

[EricClaeys]

How did you fix the problem?

Please attach your ftp-settings.sh file (after removing the password). I'd like to see your settings.

[haightjr]

I don't remember for sure what I had to do other than the test image command you mentioned and after an hour or making sure I could access the share from the pi and adjusting the ftp-settings.sh for the directories, it was working for the most part.

# How will files be uploaded?

PROTOCOL="sftp"

# The directory where the current image should be copied to.

IMAGE_DIR="/allsky"
WEB_IMAGE_DIR=""

# The directory where the timelapse video should be uploaded to.

VIDEOS_DIR="/allsky/videos"
VIDEOS_DESTINATION_NAME=""
WEB_VIDEOS_DIR=""

# The directory where the keogram image should be copied to.

KEOGRAM_DIR="/allsky/keograms"
KEOGRAM_DESTINATION_NAME=""
WEB_KEOGRAM_DIR=""

# The directory where the startrails image should be copied to.

STARTRAILS_DIR="/allsky/startrails"
STARTRAILS_DESTINATION_NAME=""
WEB_STARTRAILS_DIR=""

############### ftp, ftps, sftp, and scp PROTOCOLS only:
# Name of the remote server.
REMOTE_HOST="192.168.1.199"

# Optionally enter the port required by your server.

REMOTE_PORT="22"

############### ftp, ftps, and sftp PROTOCOLS only. REMOTE_USER is also used by the scp PROTOCOL:
# The username of the login on the remote server.
REMOTE_USER="allsky"

# The password of the login on your FTP server.  Does not apply to PROTOCOL=scp.

REMOTE_PASSWORD="################"

# If you need special commands executed when connecting to the FTP server enter them here.

LFTP_COMMANDS=""

############### scp PROTOCOL only:
# The path to the SSH key.
SSH_KEY_FILE=""

############### S3 PROTOCOL only:
# AWS CLI directory where the AWS CLI tools are installed.
AWS_CLI_DIR="/home/pi/.local/bin"

# Name of S3 Bucket where the files will be uploaded.

S3_BUCKET="allskybucket"

# S3 Access Control List (ACL).

S3_ACL="private"

############### GCS PROTOCOL only:
# Name of the GCS bucket where the files are uploaded.
GCS_BUCKET="allskybucket"

# GCS Access Control List (ACL).

GCS_ACL="private"

DO NOT CHANGE THE NEXT LINE

FTP_SH_VERSION=1