Belchertown skin - working great, except Darksky Forecasts

[Tom Cichowicz]

I've got it creating a Darksky forecast json file - with data - however web page doesn't display..

 ??  version 1.1?

[Pat]

Need a little more information than this. A link to your website? Debug logs? 

Skin version 1.2 will be released tomorrow if all goes to plan, and I advise you to switch to Aeris weather since DarkSky will be stopping their API usage at some point. 

[Tom Cichowicz]

OK, thanks ...

     I changed my Secret id and API to my Aeris account values...

I am getting forecast ONLY on my internal local webserver (weewx pi ) that is running as well.

However public server host by Go Daddy - not displaying forecast,  or graphs. ??

Plus the rounding of ALL values not happening. as well as the undefined messages along with the value in some locations.

I did go through and delete ALL the index.html files under the ../blechertown folder on my remote webserver - and restarted weewx.

Hasn't yet changed anything.

[Tom Cichowicz]

sorry here's a link to my public webpage...

Link to page

 I'll have to turn debug back on and grab a tail --- may be a bit for that.

[Pat]

Try to debug the skin using these methods: https://github.com/poblabs/weewx-belchertown/tree/development#how-to-use-debug - You may find the error? 

The undefined units could be because you may be running your site within a subfolder of a subfolder? Like mysite.com/weather/weewx/belchertown or something? See https://github.com/poblabs/weewx-belchertown/issues/342

Whats the link to your public site? 

[Pat]

Your website is returning a 404 NOT FOUND error for the forecast, weewx data files and graph json files. They are supposed to be uploaded to the JSON folder. You'll need to fix that. 

[Pat]

Start by fixing your JSON file missing errors - that might solve all of your issues. 

On Wednesday, September 9, 2020 at 12:58:23 PM UTC-4 tcich...@gmail.com wrote:

[Tom Cichowicz]

Pat;

   ok ... here's my syslog after turning on debug, in both weewx.conf & skin.conf

[Tom Cichowicz]

Pat;

   ok, I'll see if I can figure out why this is happening. I've configured the weewx FTP settings:

   [[FTP]]

        # FTP'ing the results to a webserver is treated as just another report,

        # albeit one with an unusual report generator!

        skin = Ftp

        

        # If you wish to use FTP, set "enable" to "true", then

        # fill out the next four lines.

        # Use quotes around passwords to guard against parsing errors.

        enable = true

        user = xxxxxx

        password = xxxxxx

        server = mpython.com    # The ftp server name, e.g, www.myserver.org

        path = /KM4VIG/weewx    # The destination directory, e.g., /weather

        

        # Set to True for an FTP over TLS (FTPS) connection. Not all servers

        # support this.

        secure_ftp = False

        

        # To upload files from something other than what HTML_ROOT is set

        # to above, specify a different HTML_ROOT here.

        #HTML_ROOT = public_html

        

        # Most FTP servers use port 21

        port = 21

        

        # Set to 1 to use passive mode, zero for active mode

        passive = 1

Howerver ; the files exist where they are suppose to?

 here's a screenshot from my remote connection folders...

they appear to be there and are only 9mins old from this message.. ??

what I'm I doing wrong, or where do I look to find the problem?

[Tom Cichowicz]

Pat;

   I moved the remote webserver - path directly off the root.... so the URL is now...

<New page Location>

   the problem still exists - after rebuilding the file/folders.. 

???

On Wednesday, September 9, 2020 at 1:02:19 PM UTC-4 Pat wrote:

[Pat]

If the files are there, then maybe your web host could be blocking access to those files?

[Tom Cichowicz]

Pat;

    I can't seem to figure it out, seems like a relative/absolute path issue?  Those kinda problems get my head spinning - like trying to think about double negatives! 

  However, I poked a hole in my router temporarily - allowing my rpi/weewx exposing my server to the world @ , http://idlewood.dyndns.org/weewx/belchertown/

   It runs as it does from a local URL, only the one error in the browser console  - related to a file that truly doesn't exist -> custom.css

  I may just setup another rpi to act as an external webserver -- But would prefer to figure out what it's not working from my mpython.com domain ---

[Pat]

Yep, that link looks good. You should be able to view the json files without restriction - just browse to them. 

For example, this is returning a 404: http://www.mpython.com/weather/belchertown/json/weewx_data.json

But on my site, you can browse to it without a problem. https://belchertownweather.com/json/weewx_data.json

Once you get access working to the json files, the rest should (hopefully) fall in line. 

[Tom Cichowicz]

It must be locked down at the server level, as I’m not doing nothing different- 

  I assume if I worked with my hosting tech support, they could release the restrictions on those files?

  I just hate even thinking about those calls... and I’m retired! I’m leaning toward, either setting up on one of my synology NAS boxes, or perhaps a docker session on my unraid server.

  Or easier yet keep in internal local.

[Tom Cichowicz]

Pat;

   I figured it out...

I was able to get into my hosting provider's webserver control panel. (I've never used it before)

stumbled around for awhile - haven't done any web development in over 20years.... needless to say things have changed.

I found that there wasn't any MIME type defined for JSON files ... I just added one to the list (“application/json .json” is the correct JSON content type entry.)

   That fixed it!  http://www.mpython.com/weather/belchertown/

  Thanks for ALL your help, looking forward to version 1.2 - I'm sure it will be GREAT!

  and Thanks for all your hard work and sharing AND Helping those that surely need it. 

On Wednesday, September 9, 2020 at 3:53:06 PM UTC-4 Pat wrote: