unable to display constellation overlay

[sjtaubman]

I'm new here and new to Allsky, so hopefully posting in the correct place and thank you in advance for any help.

I am running Allsky on a Raspberry Pi 4. I have been able to get most features working, but have been unable to display the constellation overlay. When I have this feature turned on, the constellation overlay does not appear and I get the following error:

Failed to load resource: the server responded with a status of 403 ()

My website is located here: https://www.sharppark.net/allsky/

Screenshot of the error message:

I have tried changing the permissions of the configuration.json file to no effect. Thank you!

[EricClaeys]

Can you list the contents of the "allsky" directory on the server.
I'm 99% sure the server can access configuration.json, otherwise it wouldn't know the title to your page or what icons to show in the bar on the left. But I have no idea why it gives those errors.

Please attach your configuration.json file.

[sjtaubman]

Thank you. Attaching the configuration.json file and screenshots (two files) of the allsky directory on the remote server. It does appear to be accessing the json file as everything else seems to be working correctly (and I created a dummy.json file and no problem seeing it).

configuration.json

[sjtaubman]

Not sure if this is relevant, but I noticed the "Failed to load resource" error I'm getting in the Console window is showing a file name with an apparent timestamp but without the "ts=" in front of the timestamp.

[EricClaeys]

Another thing to try is to create a file called dummy.json in the allsky directory and add text to it like "hello". Then see if you can get to it via https://www.sharppark.net/allsky/dummy.json
If not, then your web server is probably blocking .json files.

[EricClaeys]

Steve,
Having no ?_ts= is fine. The $ajax call adds its own timestamp, ?_= (the variable is called _ instead of _ts but serves the same purpose).

To rule out the file itself, rename it to configuration.txt, then try to access https://www.sharppark.net/allsky/configuration.txt.

@Alex-developer, any ideas?
Steve's web server handles .json files but not configuration.json.
This sounds familiar ...

[sjtaubman]

Ok, just renamed it to configuration.txt and had no problem accessing it fwiw.

[Alex-developer]

Steve, Having no ?_ts= is fine. The $ajax call adds its own timestamp, ?_= (the variable is called _ instead of _ts but serves the same purpose).

To rule out the file itself, rename it to configuration.txt, then try to access https://www.sharppark.net/allsky/configuration.txt.

@Alex-developer, any ideas? Steve's web server handles .json files but not configuration.json. This sounds familiar ...

This look to me like either a permissions issue or the web server blocking access to the file.

The site appears to be hosted by Google so maybe they have some documentation that can help?, I had a very quick look but coudl not see anything

If you create a new file called configuration.json in the root of your website can you access that?

Cheers

Alex

[sjtaubman]

Thanks, Alex. I created a file call configuration.json in the root directory and got a 403 - Forbidden. I then tried changing the name to configuration.txt in the root directory and got the same 403 - Forbidden. If the file is renamed to test.txt or test.json, I have no problem accessing it. Strangely, in my allsky directory I could access configuration.txt but not configuration.json.

SiteGround is the hosting service I am using and it does seem that for some reason it is blocking access to this file? Is there perhaps a workaround where I just rename the file to something else (and all of the references to this file)?

[sjtaubman]

That was it! I renamed the file to config.json and changed all references to this filename as well. I also needed to clear the cache in my web browser and now it works. Now I just need a night when it isn't foggy here to see I can align the constellations correctly. Thank you both for your help with this!

[EricClaeys]

@sjtaubman, Steve,
I highly suggest contacting SiteGround to get them to fix it from their end.
The proper way to edit the config file is to use the WebUI and edit remote_configuration.json (remote Website). When you save your changes in the WebUI it will upload the file to the server and rename it to "configuration.json".
In the future when you upgrade the Allsky Website it's going to look for "configuration.json" and won't install if they file isn't there.

Eric

[sjtaubman]

Thank you. I submitted a support ticket to SiteGround regarding this issue and we will see if they are able to resolve it.

…

On Jul 29, 2024, at 9:14 PM, Eric Claeys ***@***.***> wrote: @sjtaubman <https://github.com/sjtaubman>, Steve, I highly suggest contacting SiteGround to get them to fix it from their end. The proper way to edit the config file is to use the WebUI and edit remote_configuration.json (remote Website). When you save your changes in the WebUI it will upload the file to the server and rename it to "configuration.json". In the future when you upgrade the Allsky Website it's going to look for "configuration.json" and won't install if they file isn't there. Eric — Reply to this email directly, view it on GitHub <#3774 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BJRWQF2QFAYLDU4ZDAI7CITZO4HKFAVCNFSM6AAAAABLSFQ5QSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAMJYGYYTGMQ>. You are receiving this because you were mentioned.

[EricClaeys]

Please keep me posted.

[sjtaubman]

Got a rapid response from SiteGround: "Web access to the configuration.json file was stopped by our web application firewall by a rule that is aimed at preventing scanning for exposed configurations. If public access to the file is required, the rule can be disabled for your site, which I already did." I am now able to access the configuration.json file without any issues. Thanks for your help on this, and glad to have the problem resolved.

…

On Jul 30, 2024, at 11:55 AM, Eric Claeys ***@***.***> wrote: Please keep me posted. — Reply to this email directly, view it on GitHub <#3774 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BJRWQF7IEICCZO2HGL7CMJDZO7OTVAVCNFSM6AAAAABLSFQ5QSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAMJZGM4TQMA>. You are receiving this because you were mentioned.

[Alex-developer]

Got a rapid response from SiteGround: "Web access to the configuration.json file was stopped by our web application firewall by a rule that is aimed at preventing scanning for exposed configurations. If public access to the file is required, the rule can be disabled for your site, which I already did." I am now able to access the configuration.json file without any issues. Thanks for your help on this, and glad to have the problem resolved.
…
On Jul 30, 2024, at 11:55 AM, Eric Claeys @.***> wrote: Please keep me posted. — Reply to this email directly, view it on GitHub <#3774 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/BJRWQF7IEICCZO2HGL7CMJDZO7OTVAVCNFSM6AAAAABLSFQ5QSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAMJZGM4TQMA. You are receiving this because you were mentioned.

Glad its resolved

Alex

[EricClaeys]

Interesting, SiteGround must look for the word "configuration", since "dummy.json" worked.
Anyhow, glad it's working!