AllSky Remote Web Installer - Cannot connect to website

[evripidis]

So, after clean installing the v2024.12.06_01 and trying to setup everything from scratch, I want to activate the Remote Website.
I do have access through FTP, the testupload works fine, but now I get this new error.

Upload output from '/tmp/testUpload.sh.txt':
   ---- Resolving host address...
---- 2 addresses found: 2a00:1c98:1010:1::58, 213.158.90.88
---- Connecting to lpobservatory.gr (2a00:1c98:1010:1::58) port 21
...
---> AUTH TLS
<--- 234 AUTH TLS successful
---> CLNT lftp/4.9.2
WARNING: Certificate verification: hostname checking disabled
<--- 200 OK
---> USER n188878arg
<--- 331 Password required for n188878arg
---> PASS XXXX
<--- 230 User n188878arg logged in
---> PWD
<--- 257 "/" is the current directory
START info
WARNING: Certificate verification: hostname checking disabled
drwxr-x---   3 n188878arg psaserv        27 Jan 31 23:23 httpdocs
-rw-r--r--   1 n188878arg psacln     208963 Feb  1 12:50 image.jpg
drwx------   2 n188878arg root         4096 Feb  1 12:08 logs
-rw-r--r--   1 n188878arg psacln         28 Feb  1 12:41 testUpload.sh.txt
END info
In DIRECTORY=/:
drwxr-x---   3 n188878arg psaserv        27 Jan 31 23:23 httpdocs
-rw-r--r--   1 n188878arg psacln     208963 Feb  1 12:50 image.jpg
drwx------   2 n188878arg root         4096 Feb  1 12:08 logs
-rw-r--r--   1 n188878arg psacln         28 Feb  1 12:41 testUpload.sh.txt
---> EPSV
<--- 229 Entering Extended Passive Mode (|||55153|)
---- Connecting data socket to (2a00:1c98:1010:1::58) port 55153
---> MLSD
<--- 150 Opening BINARY mode data connection for MLSD
WARNING: Certificate verification: hostname checking disabled
<--- 226 Transfer complete
---> TYPE I
<--- 200 Type set to I
---> EPSV
<--- 229 Entering Extended Passive Mode (|||55530|)
---- Connecting data socket to (2a00:1c98:1010:1::58) port 55530
---> STOR testUpload.sh-11999
<--- 150 Opening BINARY mode data connection for testUpload.sh-11999
WARNING: Certificate verification: hostname checking disabled
<--- 226 Transfer complete
---> MFMT 20250201105036 testUpload.sh-11999
<--- 213 Modify=20250201105036; testUpload.sh-11999
---> DELE testUpload.sh.txt
<--- 250 DELE command successful
---> TYPE A
<--- 200 Type set to A
---> EPSV
<--- 229 Entering Extended Passive Mode (|||55264|)
---- Connecting data socket to (2a00:1c98:1010:1::58) port 55264
---> MLSD
<--- 150 Opening ASCII mode data connection for MLSD
WARNING: Certificate verification: hostname checking disabled
<--- 226 Transfer complete
---> TYPE I
<--- 200 Type set to I
---> RNFR testUpload.sh-11999
<--- 350 File or directory exists, ready for destination name
---> RNTO testUpload.sh.txt
<--- 250 Rename successful
---> QUIT
<--- 221 Goodbye.

[EricClaeys]

@evripidis,
When I try to go to https://lpobservatory.gr/ I get this:

I think this is a bug - the installer is trying to go to your URL but I believe this is what's there:

drwxr-x---   3 n188878arg psaserv        27 Jan 31 23:23 httpdocs
-rw-r--r--   1 n188878arg psacln     208963 Feb  1 12:50 image.jpg
drwx------   2 n188878arg root         4096 Feb  1 12:08 logs
-rw-r--r--   1 n188878arg psacln         28 Feb  1 12:41 testUpload.sh.txt

None of those files are a default the web server uses, and you (correctly) have the web site configured to not allow displaying the contents of the directory if there's no default file.

I'm looking into it.

[evripidis]

Hmm interesting. @EricClaeys does the installer looking for the specific folder allsky ? Is this requirement? If so, I think it would be useful an error message such as " Unable to locate allsky folder" or something.

For example, if I want the website to be running directly at lpobservatory.gr and not at lpobservatory.gr/allsky, I should directly upload all the files & folders directly at server's root location.

PS. Tried with or without the allsky folder but the issue remains.

[EricClaeys]

@evripidis,

Please try the attached file. It should fix the problem. To use it, download to the allsky directory on your Pi, then:

mv remoteWebsiteInstall.sh  remoteWebsiteInstall.sh-OLD
mv remoteWebsiteInstall.sh.txt remoteWebsiteInstall.sh

does the installer looking for the specific folder allsky

No, at that point in the installation, the installer was simply trying to determine if the URL was valid.
In your case, the installer saw a "403 forbidden" code instead of a "200 success" code, and the installer considered "403 forbidden" an error and gave you the "cannot connect" message.

The fix is to consider a "403 forbidden" code to be success. After thinking about it, this makes sense because the server did in fact accept the URL and went to the proper directory. It just didn't find anything at the URL it could use.

This is actually the expected behavior when a NEW web site is created but before anything is copied to it.
I didn't see this problem in testing because I used web sites that had the prior Allsky installed.

remoteWebsiteInstall.sh.txt

[EricClaeys]

For example, if I want the website to be running directly at lpobservatory.gr and not at lpobservatory.gr/allsky, I should directly upload all the files & folders directly at server's root location.

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.