remoteWebsiteInstall.sh issue with remote_configuration.json in v2024.12.06_06

[astrobrothers]

Fresh install of v2024.12.06_06 and moving to new web host - everything is working so far, except for remote website.
Issue: When I ./remoteWebsiteInstall.sh it fails, see attached image.
Equipment: RPi 4 8GB, HQ cam and Trixie OS

It stops on item 2, checking the remote_configuration.json file. It is not creating it, I cannot open it in the WebUI editor as I have in previous builds.

It also says it cannot find the remote website ERROR 404. Note, it's a funky URL until I get the domain transferred over. That said, the URL definitely works. I can also say for certain that testUpload.sh works and if I turn remote website on in WebUI, the current image.jpg is being continuously updated to the correct folder (../public_html/allsky-MA-1/image.jpg) and this can be seen remotely at http://user.myecosites.com/allsky-MA-1/image.jpg

A couple notes:
I'm using key wo/password to ssh to host. This works fine from command line. In WebUI, I had to put a dummy pw to satisfy lftp. That is clearly working for transfer, but not sure if that hack is messing something else up.

I've been finding with this build that I have to often reenter info in the WebUI a few times. It's not consistent, but has happened in general with this build for me. Not sure if using Raspberry Pi Connect is playing a role. Once it saves, it sticks, but I've been having to double check my edits actually save.

[EricClaeys]

When I go to http://user.myecosites.com/ I get:

user.myecosites.com’s DNS address could not be found

What is your Protocol setting?
remoteWebsiteInstall.sh only works with the ftp-like protocols.

[astrobrothers]

sftp
Sorry I gave you the URL without the actual raw link: http://eepxutvpjqdfcqtv.myecosite.com/allsky-MA-1/image.jpg
I'm waiting for the IT folks to migrate this to observe.mit.edu, which will then make it observe.mit.edu/allsky-MA-1/ when all is said and done.

Is the script throwing an error because of DNS issues before it tries to create the .json file and then upload to remote website? I assumed setting this up while the domain is being registered would be fine and then update it next week. Should I maybe wait to install allsky remote website until the DNS part is sorted out?

[EricClaeys]

I don't remember the order - if the remote configuration file is created first, then the website uploaded, or if the website is uploaded then the .json file created and uploaded.
Either way, I suggest waiting for the final DNS name.

[astrobrothers]

I got it working today. Here's what I did:

1. It's possible that the DNS migration played a role, difficult to troubleshoot as there were a lot of moving pieces. Site is now observe.mit.edu and actual director structure is /public_html/allsky-MA-1
2. After that, I could run testUpload.sh no problem, ssh no problem, just as before the domain change.
3. As far as I can tell, even after running allsky-config compare_paths --website, was that the actual error was only being triggered when trying to use ./remoteWebsiteInstall.sh
4. The change that fixed it was in WebUI, changing the "Website URL" to just https://observe.mit.edu <-- leaving off the /allsky-MA-1/ Then, rerun website install and it worked. I guess I don't totally understand why it cared, as long as I know what to do for the next several cameras I build.

Note that in /documentation/explanations/serverLocationToURL.html --> it says in item #2 "The URL to the Allsky Website is still https://mysite.com/allsky" That's why I was keeping the /allsky-MA-1 directory in the WebUI entry. Is it just a preference for the root (public_html)? or did it want to see an index.php/html file? Also, should the instructions say, point to main director of your site, not allsky?

[EricClaeys]

FYI, you can move the icons on the left side down by editing the leftSidebarStyle field in the remote configuration.json.
Mine is set to: top: 300px; background-color: yellow;
The yellow is just for fun.

For # 4, I don't know why the "Website URL" didn't work with "/allsky-MA-1". It should have.

Please upload ~/allsky/config/logs/remoteWebsiteInstall.log. That may give me a clue.

[EricClaeys]

In your note about the documentation, remoteWebsiteInstall.sh uses the server's URL to look for some files to determine if an existing website is there, and if so, if it's one from a prior release or the current release. It uses the curl tool to mimic a web browser, so doesn't know anything about public_html (which is what FTP sees).
The server's URL should take you to the directory that holds the Allsky Website, in your case allsky-MA-1. By chance do you have some allsky files in the directory ABOVE allsky-MA-1 ?

Also, when going to your site, is the web server doing any redirection?