Remote Website problem

[Trev-NI]

I have followed instructions best as I can.
I uploaded the files to folder - allsky - using ftp client and the ftp path I use is directly to that folder. I tested placing a random picture file in the folder and can navigate to it and see it ok in web browser.
Upon running the config file as requested I get this error - but the site has been installed. What am I missing? Screengrab of my settings too.

[EricClaeys]

Can you provide the URL to the instructions?

The screenshot is saying you need to run remoteWebsiteInstall.sh. I will improve the message in the next release.

[Trev-NI]

Thanks for taking a look. When I run the install line I get this.

Sorry can you explain a little more what the URL is you ask for?

[EricClaeys]

For the error, use cd ~/allsky. You are missing the slash.

Re: URL, you said:

I have followed instructions best as I can.

I would like to know exactly what instructions so I can clarify them if needed.

[Trev-NI]

I have re-uploaded all the files in - allsky - via ftp. Have run the cd line and get this:

Instructions are clear enough - I have probably done something wrong. Instructions from here:

https://htmlpreview.github.io/?https://raw.githubusercontent.com/AllskyTeam/allsky/master/html/documentation/installations/AllskyWebsite.html

I can have the path clarified from my provider if required

[Trev-NI]

Confused re Websites and Remote Server Settings.

I am sorry if I seem to be a complete numpty here but I am following the online Install a remote Allsky Website instructions on the gitHub page.

1. On the remote server
   Yes this is fine. I have my own personal website and can ftp to it and add the required all sky folder.

2. On the Pi.
   I can follow the instructions ok however . . .
   There are settings here for Remote Website and Remote Server
   The instructions don’t make this clear . .
   Am I to use one or the other OR both?
   Do the instructions No.2 pertain to just the Remote Website?
   Forgive me but I do not understand the basic difference between Remote Website and Remote Server
   Am I not placing the allsky folder to hold a remote website on my (remote server)

I have been working at this for a few days trying to get my head round it and my brain is fried with code and settings.

Also
Upon opening the Websites and Remote Server Settings section from Allsky Settings - does a reset to default values clear only this section or will it clear all settings in Allsky settings - I don’t want to clear anything unless I am certain as I have my camera running pretty well.

Again I apologise but there is a lot to do to get my cam on to my own website

[Trev-NI]

I thought I had updated the allsky to v 06_01 from the instructions but it appears that this was not the case. Luckily I still have my original version with all the settings intact. Where exactly are the instructions fo this update. I appear to be back where I started from.
I followed the instructions from here

https://htmlpreview.github.io/?https://raw.githubusercontent.com/AllskyTeam/allsky/master/html/documentation/installations/Allsky.html

[EricClaeys]

Those are the correct instructions, EXCEPT, you need to use

git clone --recursive --branch v2024.12.06_01 --depth=1 https://github.com/AllskyTeam/allsky.git

instead of the "git clone" in the instructions. This is because v2024.12.06_01 hasn't been officially released yet.

[Trev-NI]

Ah OK, thought is was 1 Feb. I will have another go.

T.

[Trev-NI]

OK got _01 installed ok. Still having problems with uploading website - I get this

[Trev-NI]

This error message also

[EricClaeys]

What's in the file it mentions?
You can also run testUpload.sh --website and see what it says.

[Trev-NI]

Your code line directs me to the same file in temp/testUpload
as in the error screenshot
the content of the file is this:

Commands used are in '/home/pi/allsky/tmp/lftp_cmds/testUpload.sh.txt'
Upload output from 'commands.txt':
�[0;31m*** upload.sh: ERROR, RET=1:
FILE_TO_UPLOAD='commands.txt'
REMOTE_HOST='ftp.gb.stackcp.com'
DIRECTORY='public_html/astro/allsky/'
TEMP_NAME='testUpload.sh-19552'
DESTINATION_NAME='commands.txt'
�[0m
---- Resolving host address...
---- 2 addresses found: 45.8.227.141, 45.8.227.140
---- Connecting to ftp.gb.stackcp.com (45.8.227.141) port 21
<--- 220 FTP server ready
---> FEAT
<--- 211-Features:
<--- AUTH TLS
<--- CCC
<--- CLNT
<--- CSID
<--- EPRT
<--- EPSV
<--- HOST
<--- LANG en-US
<--- MDTM
<--- MFF modify;UNIX.group;UNIX.mode;
<--- MFMT
<--- MLST modify*;perm*;size*;type*;unique*;UNIX.group*;UNIX.groupname*;UNIX.mode*;UNIX.owner*;UNIX.ownername*;
<--- PBSZ
<--- PROT
<--- RANG STREAM
<--- REST STREAM
<--- SIZE
<--- SSCN
<--- TVFS
<--- UTF8
<--- 211 End
---> AUTH TLS
<--- 234 AUTH TLS successful
---> CLNT lftp/4.9.2
WARNING: Certificate verification: The certificate is NOT trusted. The certificate issuer is unknown. (F7:2E:57:12:33:1E:E8:B8:41:DA:C0:DF:3C:95:A6:ED:F3:4C:98:BC)
<--- 200 OK
---> LANG
<--- 200 Using default language en_GB.UTF-8
---> OPTS UTF8 ON
<--- 200 UTF8 set to on
---> HOST ftp.gb.stackcp.com
<--- 504 ftp.gb.stackcp.com: Unknown hostname provided
---> USER trev@trevormckay.co.uk
<--- 331 Password required for trev@trevormckay.co.uk
---> PASS XXXX
<--- 230 Login successful: username and password correct.
---> OPTS MLST modify;perm;size;type;UNIX.group;UNIX.mode;UNIX.owner;
<--- 200 MLST OPTS modify;perm;size;type;UNIX.group;UNIX.mode;UNIX.owner;
---> PWD
<--- 257 "/" is the current directory
---> PBSZ 0
<--- 200 PBSZ 0 successful
---> PROT P
<--- 200 Protection set to Private
START info
WARNING: Certificate verification: The certificate is NOT trusted. The certificate issuer is unknown. (F7:2E:57:12:33:1E:E8:B8:41:DA:C0:DF:3C:95:A6:ED:F3:4C:98:BC)
drwxr-xr-x 9 439581 439581 4096 Feb 3 17:01 allsky
END info
---> CWD /public_html/astro/allsky
<--- 550 /public_html/astro/allsky: No such file or directory
cd: Access failed: 550 /public_html/astro/allsky: No such file or directory
---> QUIT
<--- 221 Goodbye.

[Trev-NI]

Guys, I am really struggling with the Remote Website install.
Been at this on and off for some two weeks now.
I am sorry but I am going round in circles and trying my best to follow the documentation as I see it. I have uploaded the files to my server and I can see something . . .
www.trevormckay.co.uk/astro/allsky
but this is what I see

I have
2.C I run the install.sh
and
2.D configure

but still no luck - there are so many settings - I am now totally confused

where is that imageName setting in the first place - I have searched

[Trev-NI]

from
remoteWebsiteinstall.log

if any help

Tue 4 Feb 15:24:22 GMT 2025 * Test upload file deleted from server.
Wed 5 Feb 12:11:55 GMT 2025 * STARTING INSTALLATION.

Wed 5 Feb 12:11:55 GMT 2025 * Start pre installation checks.
Wed 5 Feb 12:11:55 GMT 2025 * All WebUI settings exist.
Wed 5 Feb 12:11:55 GMT 2025 * No local config file found.
Wed 5 Feb 12:11:55 GMT 2025 * Checking connectivity to https://trevormckay.co.uk/astro/allsky/
Wed 5 Feb 12:11:56 GMT 2025 * Looking for old and new config files at https://trevormckay.co.uk/astro/allsky/
Wed 5 Feb 12:11:56 GMT 2025 * Found new-style 'configuration.json.
Wed 5 Feb 12:11:57 GMT 2025 * Website is valid.
Wed 5 Feb 12:11:57 GMT 2025 * Using new-style Website configuration file on the remote Website; it will be downloaded and saved locally.
Wed 5 Feb 12:11:57 GMT 2025 * Checking upload to server.
Wed 5 Feb 12:12:00 GMT 2025 * INSTALLATION ABORTED
Unable to upload a file to the server..

Wed 5 Feb 12:12:20 GMT 2025 * Test upload file deleted from server.

[Trev-NI]

Eric

Re discussion 4271
Cannot connect to website.

you say

"Correct, but, with this release you should NOT "upload" anything. The installer does that. All users need to do is have a web server with a valid URL, and ideally create an "allsky" directory that will eventually hold the files."

Are there different or updated instructions for this release?

A while back you indicated that with the new release it should be easier to install Remote Website.

I need clarification re instructions as to how I should proceed please see my 2 previous comments

[brianboru82]

The error 550 indicates it can't find that folder on the FTP server. You have public_html/astro/allsky/ listed, try doing just astro/allsky or allsky and see if any of those work.

I also saw a certificate not trusted error in one of your earlier screenshots, try the troubleshooting suggestions here under 'Certificate Related Errors' to see if those resolve it. :
https://htmlpreview.github.io/?https://raw.githubusercontent.com/AllskyTeam/allsky/master/html/documentation/troubleshooting/uploads.html

[Trev-NI]

Thanks for reply. Not much luck.

Looking like still a problem with certificate

I had seen that about the Certificate and added this

now I am seeing this

and the contents of the file are:

Commands used are in '/home/pi/allsky/tmp/lftp_cmds/testUpload.sh.txt'
Upload output from '/tmp/testUpload.sh.txt':
*** upload.sh: ERROR, RET=1:
FILE_TO_UPLOAD='/tmp/testUpload.sh.txt'
REMOTE_HOST='ftp.gb.stackcp.com'
DIRECTORY='astro/allsky/'
TEMP_NAME='testUpload.sh-21747'
DESTINATION_NAME='testUpload.sh.txt'

---- Resolving host address...
---- 2 addresses found: 45.8.227.140, 45.8.227.141
---- Connecting to ftp.gb.stackcp.com (45.8.227.140) port 21
<--- 220 FTP server ready
---> FEAT
<--- 211-Features:
<--- AUTH TLS
...
<--- UTF8
<--- 211 End
---> AUTH TLS
<--- 234 AUTH TLS successful
---> CLNT lftp/4.9.2
WARNING: Certificate verification: The certificate is NOT trusted. The certificate issuer is unknown. (F7:2E:57:12:33:1E:E8:B8:41:DA:C0:DF:3C:95:A6:ED:F3:4C:98:BC)
<--- 200 OK
---> LANG
<--- 200 Using default language en_GB.UTF-8
---> OPTS UTF8 ON
<--- 200 UTF8 set to on
---> HOST ftp.gb.stackcp.com
<--- 504 ftp.gb.stackcp.com: Unknown hostname provided
---> USER trev@trevormckay.co.uk
<--- 331 Password required for trev@trevormckay.co.uk
---> PASS XXXX
<--- 230 Login successful: username and password correct.
---> OPTS MLST modify;perm;size;type;UNIX.group;UNIX.mode;UNIX.owner;
<--- 200 MLST OPTS modify;perm;size;type;UNIX.group;UNIX.mode;UNIX.owner;
---> PWD
<--- 257 "/" is the current directory
---> PBSZ 0
<--- 200 PBSZ 0 successful
---> PROT P
<--- 200 Protection set to Private
START info
WARNING: Certificate verification: The certificate is NOT trusted. The certificate issuer is unknown. (F7:2E:57:12:33:1E:E8:B8:41:DA:C0:DF:3C:95:A6:ED:F3:4C:98:BC)
drwxr-xr-x 11 439581 439581 4096 Feb 5 11:21 allsky
END info
---> CWD /astro/allsky
<--- 550 /astro/allsky: No such file or directory
cd: Access failed: 550 /astro/allsky: No such file or directory
---> QUIT
<--- 221 Goodbye.

[EricClaeys]

I am traveling today so will answer in more detail later.

In the meantime, please hold off doing anything else with the remote Website.
We are officially releasing v2024.12.06_01 very soon, and it should fix the problems you are having. I spent many hours last night improving remoteWebsiteInstall.sh and fixing some bugs.

Sorry for the hassles.
Eric

[Trev-NI]

Thank yo Eric. I appreciate your patience and the hard work you put into this project. Happy to wait.

[EricClaeys]

Your FTP Commandssetting fixed the ERROR and now it's just a WARNING so you can ignore it:

WARNING: Certificate verification: The certificate is NOT trusted. The certificate issuer is unknown.

Look at the last few lines of the output for the fix to the red error in your screenshot:

START info
WARNING: Certificate verification: The certificate is NOT trusted. The certificate issuer is unknown.
drwxr-xr-x 11 439581 439581 4096 Feb 5 11:21 allsky
END info
---> CWD /astro/allsky
<--- 550 /astro/allsky: No such file or directory
cd: Access failed: 550 /astro/allsky: No such file or directory
---> QUIT

It is trying to find a directory on the server called /astro/allsky, but it doesn't exist.
However, the 3rd line in the output shows an allsky directory.

[Trev-NI]

I am very sorry friends - I just can not get this Remote Website to work.

I find the instructions to create the remote website confusing.
I really need a - 1. do this, 2. do that, 3. then do this etc.

I can see the local website at allsky/allsky screengrab attached and all looks as I want it to be
when I try to access the remote site at trevormckay/astro/allsky - I get image loading but the other information appears to be there OK

back in the webui I get this error - screengrab also attached
and the contents of the offending file as here also.

I have been at this some three weeks now and believed that the new update and documentation would make this easier.
Is there no way that in the webui that there could be a basic set of entries for remote web site that would get the site live with an additional dropdown or section for "advanced web settings"
I am going round in circles - I have tried everything.

Commands used are in '/home/pi/allsky/tmp/lftp_cmds/testUpload.sh.txt'
Upload output from '/tmp/testUpload.sh.txt':
*** upload.sh: ERROR, RET=1:
FILE_TO_UPLOAD='/tmp/testUpload.sh.txt'
REMOTE_HOST='ftp.gb.stackcp.com'
DIRECTORY='astro/allsky/'
TEMP_NAME='testUpload.sh-30254'
DESTINATION_NAME='testUpload.sh.txt'

set ssl:verify-certificate no # From FTP Commands
---- Resolving host address...
---- 2 addresses found: 45.8.227.140, 45.8.227.141
---- Connecting to ftp.gb.stackcp.com (45.8.227.140) port 21
<--- 220 FTP server ready
---> FEAT
<--- 211-Features:
<--- AUTH TLS
...
<--- UTF8
<--- 211 End
---> AUTH TLS
<--- 234 AUTH TLS successful
---> CLNT lftp/4.9.2
WARNING: Certificate verification: The certificate is NOT trusted. The certificate issuer is unknown. (F7:2E:57:12:33:1E:E8:B8:41:DA:C0:DF:3C:95:A6:ED:F3:4C:98:BC)
<--- 200 OK
---> LANG
<--- 200 Using default language en_GB.UTF-8
---> OPTS UTF8 ON
<--- 200 UTF8 set to on
---> HOST ftp.gb.stackcp.com
<--- 504 ftp.gb.stackcp.com: Unknown hostname provided
---> USER trev@trevormckay.co.uk
<--- 331 Password required for trev@trevormckay.co.uk
---> PASS XXXX
<--- 230 Login successful: username and password correct.
---> OPTS MLST modify;perm;size;type;UNIX.group;UNIX.mode;UNIX.owner;
<--- 200 MLST OPTS modify;perm;size;type;UNIX.group;UNIX.mode;UNIX.owner;
---> PWD
<--- 257 "/" is the current directory
---> PBSZ 0
<--- 200 PBSZ 0 successful
---> PROT P
<--- 200 Protection set to Private
START info
WARNING: Certificate verification: The certificate is NOT trusted. The certificate issuer is unknown. (F7:2E:57:12:33:1E:E8:B8:41:DA:C0:DF:3C:95:A6:ED:F3:4C:98:BC)
drwxr-xr-x 11 439581 439581 4096 Feb 5 11:21 allsky
END info
---> CWD /astro/allsky
<--- 550 /astro/allsky: No such file or directory
cd: Access failed: 550 /astro/allsky: No such file or directory
---> QUIT
<--- 221 Goodbye.

[EricClaeys]

@Trev-NI, sorry you're still having problems with this.

You said:

I find the instructions to create the remote website confusing. I really need a - 1. do this, 2. do that, 3. then do this etc.

Are you using the newest instructions that came with v2024.12.06_01 ? I updated them based on user feedback from v2024.12.06, including your feedback.
There ARE step-by-step instructions like you want:

 
After reading the newest instructions, if they are still confusing, could you please give me some concrete examples of what's confusing?

 

---

You said:

when I try to access the remote site at trevormckay/astro/allsky - I get image loading but the other information appears to be there OK

Did you do what the message in yellow said? It's telling you exactly what to do. The imageName field is incorrect:

It should be image.jpg. Change it via the WebUI's Editor page - update the remote_configuration.json file.

FYI, in the next release the yellow message will be this, which I think is a little clearer. If you have a suggestion on how to improve it even more, let me know:

 

---

I can't read the 3rd screenshot - the WebUI window is too small, but I assume it's related to the text that follows it.
Please run

testUpload.sh --website

and it should tell you what's wrong. I updated it in this release to catch the problem you are having.
That problem is also what's causing this message on your Website:

Allsky can't upload anything to the server.

[Trev-NI]

OK I see the documentation in the WebUI.

in the editor I have changed the line
"imageName": "/current/temp/image.jpg",
to
"imageName": "image.jpg",

the instructions say
c. Confugure the Remote Website
. . . dropdown at the bottom of the page , select (remote_configuration.jason (Remote Allsky Website)
however . . .
I only have the one option which is
configuration.jason (local Allsky Website)

In the Allsky Settings -
Websites and Remote Server Settings
Use Local Website YES
Use Remote Website YES
Use Remote Server NO

can we clarify this much first.

[EricClaeys]

@Trev-NI,

Did you run 2a and 2b in the instructions?

The installRemoteWebsite.sh command in 2b should have created the remote_configuration.json file.

• If you DID run that command, please attach ~/allsky/config/logs/remoteWebsiteInstall.log and I'll see why the file wasn't created.
• If you did NOT run that command, I'm confused. You wanted step-by-step instructions but didn't follow them?

The remote_configuration.json (Remote Allsky Website) entry in the Editor page isn't there because the file doesn't exist. OR, you need to refresh the browser by going to that page and pressing SHIFT-F5.

[Trev-NI]

Thanks Eric for your patience.I will take a look later with a fresh pair of eyes.

[Trev-NI]

Eric - I am following the instructions as laid out.

1. allsky directory is on my server

2a. Update settings - remote website - Use remote website not enabled. Done - save - reports no changes made (settings are as they should and have been).
2b. Ran the remoteWebsiteInstall.sh and get this:

and the remote install log:

Tue 11 Feb 21:16:51 GMT 2025 * STARTING INSTALLATION.

Tue 11 Feb 21:16:51 GMT 2025 * Start pre installation checks.
Tue 11 Feb 21:16:51 GMT 2025 * All WebUI settings exist.
Tue 11 Feb 21:16:51 GMT 2025 * No local config file found.
Tue 11 Feb 21:16:51 GMT 2025 * Checking connectivity to https://trevormckay.co.uk/astro/allsky/
Tue 11 Feb 21:16:52 GMT 2025 * Got HTTP_STATUS 403 from https://trevormckay.co.uk/astro/allsky/; connectivity worked.
Tue 11 Feb 21:16:52 GMT 2025 * Skipping remaining validity checks due to Basic Connectivity.
Tue 11 Feb 21:16:52 GMT 2025 * No configuration file found - a new one will be created.
Tue 11 Feb 21:16:52 GMT 2025 * Checking upload to server with 'commands.txt'.
Tue 11 Feb 21:16:54 GMT 2025 * Upload failed:
Test upload to Remote Website FAILED.
Tue 11 Feb 21:16:54 GMT 2025 * Completed pre installation checks.
Tue 11 Feb 21:19:26 GMT 2025 * INSTALLATION ABORTED Unable to upload a file to the server..

Tue 11 Feb 21:19:26 GMT 2025 * Asking user if they want to view error message.
Tue 11 Feb 21:20:15 GMT 2025 *** ERROR:

---

Commands used are in '/home/pi/allsky/tmp/lftp_cmds/testUpload.sh.txt'
Upload output from 'commands.txt':
*** upload.sh: ERROR, RET=1:
FILE_TO_UPLOAD='commands.txt'
REMOTE_HOST='ftp.gb.stackcp.com'
DIRECTORY='astro/allsky/'
TEMP_NAME='testUpload.sh-14209'
DESTINATION_NAME='commands.txt'

set ssl:verify-certificate no # From FTP Commands
---- Resolving host address...
---- 2 addresses found: 45.8.227.141, 45.8.227.140
---- Connecting to ftp.gb.stackcp.com (45.8.227.141) port 21
<--- 220 FTP server ready
---> FEAT
<--- 211-Features:
<--- AUTH TLS
<--- CCC
<--- CLNT
<--- CSID
<--- EPRT
<--- EPSV
<--- HOST
<--- LANG en-US
<--- MDTM
<--- MFF modify;UNIX.group;UNIX.mode;
<--- MFMT
<--- MLST modify*;perm*;size*;type*;unique*;UNIX.group*;UNIX.groupname*;UNIX.mode*;UNIX.owner*;UNIX.ownername*;
<--- PBSZ
<--- PROT
<--- RANG STREAM
<--- REST STREAM
<--- SIZE
<--- SSCN
<--- TVFS
<--- UTF8
<--- 211 End
---> AUTH TLS
<--- 234 AUTH TLS successful
---> CLNT lftp/4.9.2
WARNING: Certificate verification: The certificate is NOT trusted. The certificate issuer is unknown. (F7:2E:57:12:33:1E:E8:B8:41:DA:C0:DF:3C:95:A6:ED:F3:4C:98:BC)
<--- 200 OK
---> LANG
<--- 200 Using default language en_GB.UTF-8
---> OPTS UTF8 ON
<--- 200 UTF8 set to on
---> HOST ftp.gb.stackcp.com
<--- 504 ftp.gb.stackcp.com: Unknown hostname provided
---> USER trev@trevormckay.co.uk
<--- 331 Password required for trev@trevormckay.co.uk
---> PASS XXXX
<--- 230 Login successful: username and password correct.
---> OPTS MLST modify;perm;size;type;UNIX.group;UNIX.mode;UNIX.owner;
<--- 200 MLST OPTS modify;perm;size;type;UNIX.group;UNIX.mode;UNIX.owner;
---> PWD
<--- 257 "/" is the current directory
---> PBSZ 0
<--- 200 PBSZ 0 successful
---> PROT P
<--- 200 Protection set to Private
START info
WARNING: Certificate verification: The certificate is NOT trusted. The certificate issuer is unknown. (F7:2E:57:12:33:1E:E8:B8:41:DA:C0:DF:3C:95:A6:ED:F3:4C:98:BC)
drwxr-xr-x 2 439581 439581 4096 Feb 11 11:40 allsky
END info
---> CWD /astro/allsky
<--- 550 /astro/allsky: No such file or directory
cd: Access failed: 550 /astro/allsky: No such file or directory
---> QUIT
<--- 221 Goodbye.

---

Tue 11 Feb 21:28:48 GMT 2025 * STARTING INSTALLATION.

Tue 11 Feb 21:28:48 GMT 2025 * Start pre installation checks.
Tue 11 Feb 21:28:48 GMT 2025 * All WebUI settings exist.
Tue 11 Feb 21:28:48 GMT 2025 * No local config file found.
Tue 11 Feb 21:28:48 GMT 2025 * Checking connectivity to https://trevormckay.co.uk/astro/allsky/
Tue 11 Feb 21:28:49 GMT 2025 * Got HTTP_STATUS 403 from https://trevormckay.co.uk/astro/allsky/; connectivity worked.
Tue 11 Feb 21:28:49 GMT 2025 * Skipping remaining validity checks due to Basic Connectivity.
Tue 11 Feb 21:28:49 GMT 2025 * No configuration file found - a new one will be created.
Tue 11 Feb 21:28:49 GMT 2025 * Checking upload to server with 'commands.txt'.
Tue 11 Feb 21:28:51 GMT 2025 * Upload failed:
Test upload to Remote Website FAILED.
Tue 11 Feb 21:28:51 GMT 2025 * Completed pre installation checks.
Tue 11 Feb 21:34:42 GMT 2025 * STARTING INSTALLATION.

Tue 11 Feb 21:34:42 GMT 2025 * Start pre installation checks.
Tue 11 Feb 21:34:42 GMT 2025 * All WebUI settings exist.
Tue 11 Feb 21:34:42 GMT 2025 * No local config file found.
Tue 11 Feb 21:34:43 GMT 2025 * Checking connectivity to https://trevormckay.co.uk/astro/allsky/
Tue 11 Feb 21:34:43 GMT 2025 * Got HTTP_STATUS 403 from https://trevormckay.co.uk/astro/allsky/; connectivity worked.
Tue 11 Feb 21:34:43 GMT 2025 * Skipping remaining validity checks due to Basic Connectivity.
Tue 11 Feb 21:34:43 GMT 2025 * No configuration file found - a new one will be created.
Tue 11 Feb 21:34:43 GMT 2025 * Checking upload to server with 'commands.txt'.
Tue 11 Feb 21:34:46 GMT 2025 * Upload failed:
Test upload to Remote Website FAILED.
Tue 11 Feb 21:34:47 GMT 2025 * Completed pre installation checks.
Tue 11 Feb 21:36:00 GMT 2025 * INSTALLATION ABORTED Unable to upload a file to the server..

Tue 11 Feb 21:36:00 GMT 2025 * Asking user if they want to view error message.
Tue 11 Feb 21:39:10 GMT 2025 *** ERROR:

---

Commands used are in '/home/pi/allsky/tmp/lftp_cmds/testUpload.sh.txt'
Upload output from 'commands.txt':
*** upload.sh: ERROR, RET=1:
FILE_TO_UPLOAD='commands.txt'
REMOTE_HOST='ftp.gb.stackcp.com'
DIRECTORY='astro/allsky/'
TEMP_NAME='testUpload.sh-28295'
DESTINATION_NAME='commands.txt'

set ssl:verify-certificate no # From FTP Commands
---- Resolving host address...
---- 2 addresses found: 45.8.227.141, 45.8.227.140
---- Connecting to ftp.gb.stackcp.com (45.8.227.141) port 21
<--- 220 FTP server ready
---> FEAT
<--- 211-Features:
<--- AUTH TLS
<--- CCC
<--- CLNT
<--- CSID
<--- EPRT
<--- EPSV
<--- HOST
<--- LANG en-US
<--- MDTM
<--- MFF modify;UNIX.group;UNIX.mode;
<--- MFMT
<--- MLST modify*;perm*;size*;type*;unique*;UNIX.group*;UNIX.groupname*;UNIX.mode*;UNIX.owner*;UNIX.ownername*;
<--- PBSZ
<--- PROT
<--- RANG STREAM
<--- REST STREAM
<--- SIZE
<--- SSCN
<--- TVFS
<--- UTF8
<--- 211 End
---> AUTH TLS
<--- 234 AUTH TLS successful
---> CLNT lftp/4.9.2
WARNING: Certificate verification: The certificate is NOT trusted. The certificate issuer is unknown. (F7:2E:57:12:33:1E:E8:B8:41:DA:C0:DF:3C:95:A6:ED:F3:4C:98:BC)
<--- 200 OK
---> LANG
<--- 200 Using default language en_GB.UTF-8
---> OPTS UTF8 ON
<--- 200 UTF8 set to on
---> HOST ftp.gb.stackcp.com
<--- 504 ftp.gb.stackcp.com: Unknown hostname provided
---> USER trev@trevormckay.co.uk
<--- 331 Password required for trev@trevormckay.co.uk
---> PASS XXXX
<--- 230 Login successful: username and password correct.
---> OPTS MLST modify;perm;size;type;UNIX.group;UNIX.mode;UNIX.owner;
<--- 200 MLST OPTS modify;perm;size;type;UNIX.group;UNIX.mode;UNIX.owner;
---> PWD
<--- 257 "/" is the current directory
---> PBSZ 0
<--- 200 PBSZ 0 successful
---> PROT P
<--- 200 Protection set to Private
START info
WARNING: Certificate verification: The certificate is NOT trusted. The certificate issuer is unknown. (F7:2E:57:12:33:1E:E8:B8:41:DA:C0:DF:3C:95:A6:ED:F3:4C:98:BC)
drwxr-xr-x 2 439581 439581 4096 Feb 11 11:40 allsky
END info
---> CWD /astro/allsky
<--- 550 /astro/allsky: No such file or directory
cd: Access failed: 550 /astro/allsky: No such file or directory
---> QUIT
<--- 221 Goodbye.

---

Tue 11 Feb 21:52:16 GMT 2025 * STARTING INSTALLATION.

Tue 11 Feb 21:52:16 GMT 2025 * Start pre installation checks.
Tue 11 Feb 21:52:16 GMT 2025 * All WebUI settings exist.
Tue 11 Feb 21:52:16 GMT 2025 * No local config file found.
Tue 11 Feb 21:52:16 GMT 2025 * Checking connectivity to https://trevormckay.co.uk/astro/allsky/
Tue 11 Feb 21:52:16 GMT 2025 * Got HTTP_STATUS 403 from https://trevormckay.co.uk/astro/allsky/; connectivity worked.
Tue 11 Feb 21:52:16 GMT 2025 * Skipping remaining validity checks due to Basic Connectivity.
Tue 11 Feb 21:52:16 GMT 2025 * No configuration file found - a new one will be created.
Tue 11 Feb 21:52:16 GMT 2025 * Checking upload to server with 'commands.txt'.
Tue 11 Feb 21:52:19 GMT 2025 * Upload failed:
Test upload to Remote Website FAILED.
Tue 11 Feb 21:52:19 GMT 2025 * Completed pre installation checks.
Tue 11 Feb 21:53:56 GMT 2025 * INSTALLATION ABORTED Unable to upload a file to the server..

Tue 11 Feb 21:53:56 GMT 2025 * Asking user if they want to view error message.
Tue 11 Feb 21:54:18 GMT 2025 *** ERROR:

---

Commands used are in '/home/pi/allsky/tmp/lftp_cmds/testUpload.sh.txt'
Upload output from 'commands.txt':
*** upload.sh: ERROR, RET=1:
FILE_TO_UPLOAD='commands.txt'
REMOTE_HOST='ftp.gb.stackcp.com'
DIRECTORY='astro/allsky/'
TEMP_NAME='testUpload.sh-25749'
DESTINATION_NAME='commands.txt'

set ssl:verify-certificate no # From FTP Commands
---- Resolving host address...
---- 2 addresses found: 45.8.227.141, 45.8.227.140
---- Connecting to ftp.gb.stackcp.com (45.8.227.141) port 21
<--- 220 FTP server ready
---> FEAT
<--- 211-Features:
<--- AUTH TLS
<--- CCC
<--- CLNT
<--- CSID
<--- EPRT
<--- EPSV
<--- HOST
<--- LANG en-US
<--- MDTM
<--- MFF modify;UNIX.group;UNIX.mode;
<--- MFMT
<--- MLST modify*;perm*;size*;type*;unique*;UNIX.group*;UNIX.groupname*;UNIX.mode*;UNIX.owner*;UNIX.ownername*;
<--- PBSZ
<--- PROT
<--- RANG STREAM
<--- REST STREAM
<--- SIZE
<--- SSCN
<--- TVFS
<--- UTF8
<--- 211 End
---> AUTH TLS
<--- 234 AUTH TLS successful
---> CLNT lftp/4.9.2
WARNING: Certificate verification: The certificate is NOT trusted. The certificate issuer is unknown. (F7:2E:57:12:33:1E:E8:B8:41:DA:C0:DF:3C:95:A6:ED:F3:4C:98:BC)
<--- 200 OK
---> LANG
<--- 200 Using default language en_GB.UTF-8
---> OPTS UTF8 ON
<--- 200 UTF8 set to on
---> HOST ftp.gb.stackcp.com
<--- 504 ftp.gb.stackcp.com: Unknown hostname provided
---> USER trev@trevormckay.co.uk
<--- 331 Password required for trev@trevormckay.co.uk
---> PASS XXXX
<--- 230 Login successful: username and password correct.
---> OPTS MLST modify;perm;size;type;UNIX.group;UNIX.mode;UNIX.owner;
<--- 200 MLST OPTS modify;perm;size;type;UNIX.group;UNIX.mode;UNIX.owner;
---> PWD
<--- 257 "/" is the current directory
---> PBSZ 0
<--- 200 PBSZ 0 successful
---> PROT P
<--- 200 Protection set to Private
START info
WARNING: Certificate verification: The certificate is NOT trusted. The certificate issuer is unknown. (F7:2E:57:12:33:1E:E8:B8:41:DA:C0:DF:3C:95:A6:ED:F3:4C:98:BC)
drwxr-xr-x 2 439581 439581 4096 Feb 11 11:40 allsky
END info
---> CWD /astro/allsky
<--- 550 /astro/allsky: No such file or directory
cd: Access failed: 550 /astro/allsky: No such file or directory
---> QUIT
<--- 221 Goodbye.

---

[EricClaeys]

Thanks for the info.
Please run testUpload.sh --website
It should tell you what the problem is and suggest a fix. Post only those few lines, not the dozens of lftp output lines.

Regarding the info you posted, at the end of the lftp output is:

cd: Access failed: 550 /astro/allsky: No such file or directory

What this means is the lftp command logged into your server, just like you do, and tried to go into the /astro/allsky directory, and couldn't because it doesn't exist.
When you log into the server, do you see that directory?

After logging into the server, lftp ran ls -l which lists all the files in the current directory. This line from the output you posted is the result:

drwxr-xr-x 2 439581 439581 4096 Feb 11 11:40 allsky

The first character is d which means the item is a directory. It was last modified on Feb 11 at 11:40 am.
allsky is the name of the directory. You created it in step 1 of the instructions.

The Image Directory setting in the WebUI for the remote Website tells lftp where to find the files.

What is your Image Directory set to?

[Trev-NI]

Eric - I must apologise, I feel terrible giving you so much work for what to others should be something simple.
My ignorance must be trying you patience beyond all limits.

Let me look server side as there was an issue unlocking my specific folder as when I ftp it only remains open for a set amount of time for security reasons - hence my setting up the folder "astro" which should remain open at all times - I will investigate further. Again I am deeply sorry for MY ongoing problem. T.

[Trev-NI]

Taken a bit of time away from the problem.

Started afresh.

I have set up a folder "allsky" on my server
For security reasons I have to unlock my public folder each time I ftp via my control panel
but
I can ftp to a folder "allsky" with a user ftp which unlocks (and keeps it unlocked) by ip in this case I am using the ip address of my PI
wired ethernet connection which is how I intend to use the allskycamera as the wifi will be out of range in my case.
I obtained the ip from the hover over the Pi ethernet logo top right.

I have followed
2a
and
2b
This is as far as I have ever got.

I get this:

and when I proceed - I get this:

I went to upload problems troubleshooting and ran the test upload line
which reported back about the verification
I insert: set ssl:verify-certificate no into FTP Commands (shown in the 2nd screengrab)
retry 2b
and back to "Test upload to Remote website FAILED" dialogue box

Is the initial problem the access to the folder on my server "allsky" ??
and
why is the 1st Dialogue box reporting that he new and old config files: NOT FOUND??

I am following the instructions as laid out.
Still need help.

[EricClaeys]

It's unable to log in, which means the user name or password are wrong. Did you change either of them? The user name was trev@trevormckay.co.uk.

Because it couldn't log in, it never got to the part where it checks for the "allsky" directory.
The message in the second screenshot is only 26% of the whole message.

Please run testUpload.sh --website again and attach any output AND any files it mentions.

Regarding your comment:

I must apologise, I feel terrible giving you so much work for what to others should be something simple. My ignorance must be trying you patience beyond all limits.

Actually, my frustration is not with you, but with myself. I am trying to make this process simple for inexperienced people like yourself, and I think it is when it works, but it's not simple enough when there is a problem. It should clearly state what the problem is and how to fix it.

My main concern is getting this working for you before you get totally frustrated and quit.

[Trev-NI]

Many Thanks Eric for your gracious and kind words.

I love the concept of this project and am hell bent on getting this remote website to work!

Re the upload part. Have you an idea of what ip address I should be using for the access to the file allsky via ftp:
is it the Pi ip, the router ip, etc. perhaps that could be a clue to the problem? I have tried a few with this same result.

and so _
As requested I ran testUpload line and got this

and here is the testupload file content:

Commands used are in '/home/pi/allsky/tmp/lftp_cmds/testUpload.sh.txt'
Upload output from '/tmp/testUpload.sh.txt':
�[0;31m*** upload.sh: ERROR, RET=1:
FILE_TO_UPLOAD='/tmp/testUpload.sh.txt'
REMOTE_HOST='ftp.gb.stackcp.com'
DIRECTORY='public_html/allsky/'
TEMP_NAME='testUpload.sh-32631'
DESTINATION_NAME='testUpload.sh.txt'
�[0m
set ssl:verify-certificate no # From FTP Commands
---- Resolving host address...
---- 2 addresses found: 45.8.227.141, 45.8.227.140
---- Connecting to ftp.gb.stackcp.com (45.8.227.141) port 21
<--- 220 FTP server ready
---> FEAT
<--- 211-Features:
<--- AUTH TLS
<--- CCC
<--- CLNT
<--- CSID
<--- EPRT
<--- EPSV
<--- HOST
<--- LANG en-US
<--- MDTM
<--- MFF modify;UNIX.group;UNIX.mode;
<--- MFMT
<--- MLST modify*;perm*;size*;type*;unique*;UNIX.group*;UNIX.groupname*;UNIX.mode*;UNIX.owner*;UNIX.ownername*;
<--- PBSZ
<--- PROT
<--- RANG STREAM
<--- REST STREAM
<--- SIZE
<--- SSCN
<--- TVFS
<--- UTF8
<--- 211 End
---> AUTH TLS
<--- 234 AUTH TLS successful
---> CLNT lftp/4.9.2
WARNING: Certificate verification: The certificate is NOT trusted. The certificate issuer is unknown. (F7:2E:57:12:33:1E:E8:B8:41:DA:C0:DF:3C:95:A6:ED:F3:4C:98:BC)
<--- 200 OK
---> LANG
<--- 200 Using default language en_GB.UTF-8
---> OPTS UTF8 ON
<--- 200 UTF8 set to on
---> HOST ftp.gb.stackcp.com
<--- 504 ftp.gb.stackcp.com: Unknown hostname provided
---> USER trev@trevormckay.co.uk
<--- 331 Password required for trev@trevormckay.co.uk
---> PASS XXXX
<--- 230 Login successful: username and password correct.
---> OPTS MLST modify;perm;size;type;UNIX.group;UNIX.mode;UNIX.owner;
<--- 200 MLST OPTS modify;perm;size;type;UNIX.group;UNIX.mode;UNIX.owner;
---> PWD
<--- 257 "/" is the current directory
---> PBSZ 0
<--- 200 PBSZ 0 successful
---> PROT P
<--- 200 Protection set to Private
START info
WARNING: Certificate verification: The certificate is NOT trusted. The certificate issuer is unknown. (F7:2E:57:12:33:1E:E8:B8:41:DA:C0:DF:3C:95:A6:ED:F3:4C:98:BC)
END info
---> CWD /public_html/allsky
<--- 550 /public_html/allsky: No such file or directory
cd: Access failed: 550 /public_html/allsky: No such file or directory
---> QUIT
<--- 221 Goodbye.

[EricClaeys]

@Trev-NI,

Have you an idea of what ip address I should be using for the access to the file allsky via ftp

Your remote FTP is hosted at ftp.gb.stackcp.com, correct? Continue using ftp.gb.stackcp.com

Question

Would you be willing to give me the password to your FTP site? I think it'll be a lot more efficient. I'm making changes to the code to help troubleshoot your problem (which other people have as well), and it'll be easier if I can test with your site. I currently have your server name, port, and user name configured, and since I don't have the password I can't proceed.

If you agree, in your reply add a line that looks like

<!-- your_password -->

Before posting it, click on the "Preview" tab and you shouldn't see that line. You, Alex, and I can edit your post and see what the password, but no one else can.

Please first change the password to something else, then post it, and when I'm done reset the password. That way I never have the permanent password.

Eric

[Trev-NI]

Yes, that would be great!

Before I forget - in the documentation - A remote Allsky Website - 2a. is states "Do NOT enable Use Remote Website yet, . . ."
but it does not say later at what stage this should be enabled.

and - Just to clarify. As I have to unlock my public folder via the control panel to ftp into my site but,
there is a facility for me to unlock a specific folder via ip address
it is set as unlocked at this time for this current password to the folder "allsky" which is in my public folder which should be
accessible at all times.

If you need any of the ip addresses that may help - I am happy to supply.
Hope this helps and if you require any other access etc just let me know.
Trevor

[Trev-NI]

Yes those details appear to be correct, I will add that Ip to the unlock by ip.
This unlock by ip remains mysterious - is it that of the user router, my Pi or other?

I should be able to try a few using my ftp client to determine which it is.
I don't really want to seek out another server!

[Trev-NI]

Eric - just tested a few known ip addresses via ftp client to test I could access the folder allsky
and my Public ip address lets me into the folder
I added your ip to the list to allow access
hope this helps

[EricClaeys]

Not sure, but I believe the "lock" stuff is the server only allowing certain IP addresses to log in to the FTP account. It's a nice idea, but a pain if you travel or have a different IP address.

I was able to log into your server and upload and delete a test file.

There's nothing in the root folder - if you FTP into the server you won't see any files or directories.

The problem you are having is NOT an Allsky problem.
It's a problem of not knowing where https://www.trevormckay.co.uk/ points to on the FTP side of the server. You'll need to ask your server administrator where it points to.
Another way of asking is, "where do I need to put a file on my FTP login so I can see it via https://www.trevormckay.co.uk/ ?

I tried several things including creating an astro directory and a public_html directory, but neither worked.

[Trev-NI]

Yes I understand. This server is what I used for my own website and email when I was a working Print and Graphic Designer.
Now I am retired I now just use it for my email so assumed I could put it to use for the allsky camera.
I can of course ftp into trevormckay.co.uk and always could do - thing is I always had to log into the control panel to unlock it first. then I could ftp any changes or updates - then lock it again. Times range from 1hour which was generally enough to make any changes. I found the facility to unlock a folder in the root or public folder which would allow access from a user ip - this is where we are but as you say not ideal.
My next best option would be to find another hosting service that will allow me to upload without unlocking -as probably everyone else does with ease.
I will give it one more go and have a look for a good value provider that I can use just for the allsky camera.

[EricClaeys]

Is this your personal server, or someone else's, like a hosting provider?
If it's yours, you will need to figure out what directory the URL points to.
If it is someone else's server, they should be able to help.
I sense that having to unlock is a pain, but I don't think it's the problem.

Think of it like there is a 100 story apartment building at 123 Main Street and you want to send a surprise package to Mary Smith, who lives there, but you don't know her apartment number.
You may need to ask the apartment manager for help.

[EricClaeys]

Got it. Thanks. I'll test it when I'm on my PC.
I'll also look at the documentation. I will make sure it mentions that the remote Website is enabled as part of the installation.