I have seen one other person have that issue. It looks like some junk is in the image label template. Can you show me the output of the command below?

bash: virtualenv/indi-allsky/bin/activate: File o directory non esistente

You will need to run this from within the indi-allsky git checkout folder

./config.py dump | grep TEMPLATE
2024-02-04 00:31:57,207 [INFO] MainProcess config._dump() [805]: Dumping config
"WEB_STATUS_TEMPLATE": "Status: {status:s}\nLat: {latitude:0.1f}/Long: {longitude:0.1f}\nSidereal: {sidereal_time:s}\nMode: {mode:s}\nSun: {sun_alt:0.1f}&deg; {sun_dir:s}\nMoon: {moon_alt:0.1f}&deg; {moon_dir:s}\nPhase: {moon_phase_str:s} <span data-bs-toggle=\"tooltip\" data-bs-placement=\"right\" title=\"{moon_phase:0.0f}%\">{moon_glyph:s}</span>\nSmoke: {smoke_rating:s} {smoke_rating_status}\nKp-index: {kpindex:0.2f} {kpindex_rating:s} {kpindex_trend:s} {kpindex_status:s}\nAurora: {ovation_max:d}% {ovation_max_status}",
"IMAGE_LABEL_TEMPLATE": "# size:30 [Use 60 for higher resolution cameras]\n# xy:-15,15 (Upper Right)\n# anchor:ra (Right Justified)\n# color:150,0,0\n{timestamp:%Y.%m.%d %H:%M:%S}\n# color:100,100,0\nLat {latitude:0.0f} Long {longitude:0.0f}\n# color:150,150,150\nHubble {hst_up:s} [{hst_next_h:0.1f}h/{hst_next_alt:0.0f}\u00c3\u0083\u00c2\u0082\u00c3\u0082\u00c2\u00b0]\nISS {iss_up:s} [{iss_next_h:0.1f}h/{iss_next_alt:0.0f}\u00c3\u0083\u00c2\u0082\u00c3\u0082\u00c2\u00b0]\n# xy:-15,-240 (Lower Right) [Use -15,-450 for size 60]\n# color:175,175,0\nSun {sun_alt:0.0f}\u00c3\u0083\u00c2\u0082\u00c3\u0082\u00c2\u00b0\n# color:125,0,0\nMercury {mercury_alt:0.0f}\u00c3\u0083\u00c2\u0082\u00c3\u0082\u00c2\u00b0\n# color:100,150,150\nVenus {venus_alt:0.0f}\u00c3\u0083\u00c2\u0082\u00c3\u0082\u00c2\u00b0\n# color:150,0,0\nMars {mars_alt:0.0f}\u00c3\u0083\u00c2\u0082\u00c3\u0082\u00c2\u00b0\n# color:100,100,0\nJupiter {jupiter_alt:0.0f}\u00c3\u0083\u00c2\u0082\u00c3\u0082\u00c2\u00b0\n# color:100,100,150\nSaturn {saturn_alt:0.0f}\u00c3\u0083\u00c2\u0082\u00c3\u0082\u00c2\u00b0\n# color:150,150,150\nMoon {moon_phase:0.0f}% {moon_alt:0.0f}\u00c3\u0083\u00c2\u0082\u00c3\u0082\u00c2\u00b0\n# xy:15,-120 (Lower Left) [Use 15,-210 for size 60]\n# anchor:la (Left Justified)\n# color:0,150,150\nStars {stars:d}\n# color:150,50,50\nKp-index {kpindex:0.2f}\n# color:150,150,150\nSmoke {smoke_rating:s}\n# xy:15,15 (Upper Left)\n# color:0,150,0\nExposure {exposure:0.6f}\n# color:150,50,0\nGain {gain:d}\n# color:50,50,150\nTemp {temp:0.1f}{temp_unit:s}\n# color:150,0,150\nStretch {stretch:s}\nStacking {stack_method:s}\n# color:200,200,200 (default color)\n# additional labels will be added here",
"URL_TEMPLATE": "https://{bucket}.s3.{region}.{host}",
"URL_TEMPLATE": "https://{bucket}.s3.{region}.{host}",
"TITLE_TEMPLATE": "Allsky Timelapse - {day_date:%Y-%m-%d} - {timeofday}",
"DESCRIPTION_TEMPLATE": "",

I see the extra characters in there. I am not sure what would cause that... maybe some character code conversion I was not expecting.

I would just go to the wiki page and replace your template with the expected default. You can copy it directly from here and paste it directly in the configuration page Config -> "Image tab" (about half way down).

github.com/aaronwmorris/indi-allsky/wiki/Image-Labels#defaults

I replace and magically is ok.
Thanks.
Ettore

Some more help with S3 please!

Some time ago Aaron wrote:
1. Exposure your all sky camera directly to the Internet (like you mentioned you would try).
1a. indi-allsky now supports uploading images and video to an S3 bucket. The page is locally served, but the images and videos are downloaded directly from S3, offloading most the bandwidth.
2. A few days ago, I released the SyncAPI functionality. You can setup a publicly available version of the indi-allsky web interface and your local server will perform web service calls to upload images and videos to the remote instance.

Well I've looked at AWS's description of S3 and I just can't understand it. It's odd because I've been using computers and networked systems for decades but this one has left me flummoxed.

Can you give a worked example of how to use this (assuming I'm prepared to take a subscription service, of course)?

Of course I would like to have access to historical Timelapse's on my local network, but would also like to share it. That would seem to fit with your model of using a local server -- though I'm not too happy about opening our internal network to the outside world.

But also, my wife would like to have a page with the Timelapse's on our observatory website, which is hosted by an external service (SquareSpace), but she doesn't know how to use this AWS service here.

Thanks,
Richard

You can think of S3 (or Object Storage) as a web based persistent file server. Files are uploaded via an API, but the files may be accessed/downloaded via regular HTTPS. Many companies use S3 to store documents and files with ACLs so it requires credentials to access the files, but you can also apply an anonymous access ACL and then the files can be accessed by a normal web browser. You can host entire web sites on S3 if all of the content is static files.

Here is a file from one of my S3 buckets: allskyasi290.s3.us-east-2.amazonaws.com/...1_20230816_night.jpg

In the "cloud" container based framework, because containers do not have permanent storage and get created and destroyed regularly, any files that are generated and need to be stored persistently would use Object Storage.

When you enable Non-Local Images in indi-allsky, all image and video links will be generated with the S3 URLs so none of them are served from the local instance. There is another option to serve files locally when coming from your local network, but S3 when a request comes from a remote network (serving the files on your local network has less latency than using S3).

With my cameras generating 1920x1080 images, I was paying about $3.00/mo to AWS for hosting about 3 months worth of images and videos (for a single camera).

A surprising number of people are using the SyncAPI, as an alternative. With the SyncAPI, you setup an install of indi-allsky on a remote VPS server and your local install of indi-allsky pushes images and videos to the remote server via REST API calls. In this case, your local network is never exposed. Gord Tulloch is using the SyncAPI: gordtulloch.com/indi-allsky/ You can tell he is using the SyncAPI by the REMOTE designation in the status.

@Aaron quick question:

The initial implementation allows you to upload individual timelapses (and startrail timelapses) to Youtube. All videos are not automatically uploaded. I can add an option to upload all videos to Youtube automatically if there is enough interest.

Can you integrate that option?

Done. I have not done a lot of testing with these changes, please let me know if you see any strange exceptions.

Yeah indeed, it is a little bit tricky the whole Authorized URL thing..

I would like a feedback from fellow users about "cheap" cameras that are already using succesfully right now.

I currently use the ASI224 without issue but I would like to reuse it again for planetary.