File location and ROOT error with Belchertown Skin

[Eric Gammeter]

Trying to get Belchertown skin to run, continual file location problem (file not found)

Debug info has all log, info and file list information.  No joy after multiple installation attempts.  Please let me know what you find.

Thank you-

/Eric

[Vince Skahan]

    [[StandardReport]]
    # This is the old "Standard" skin. By default, it is not enabled.
    # skin = Standard
    # enable = false
   

 You need to comment it all out, or leave it uncommented and set enable=false.

[Eric Gammeter]

[[StandardReport]]
    # This is the old "Standard" skin. By default, it is not enabled.
    # skin = Standard
    # enable = false
   

    [[Belchertown]]
        skin = Belchertown
        HTML_ROOT = /var/www/html/weewx/belchertown

        enable = true

What part of StandardReport is not commented-out? 

[Tom Keffer]

Commenting out the "enable" option causes a report to be run.

I know this is counter-intuitive, but this is for backwards compatibility. The option was introduced in V3.6. Before that, the only way to disable a report was to delete or comment out the entire report section, which in some cases was dozens of lines. To maintain backwards compatibility required this behavior.

Set it to:

[[StandardReport]]
    # This is the old "Standard" skin. By default, it is not enabled.

    skin = Standard
    enable = false

-tk

On Wed, Apr 1, 2026 at 4:32 AM Eric Gammeter <n8a...@gmail.com> wrote:

[[StandardReport]]
    # This is the old "Standard" skin. By default, it is not enabled.
    # skin = Standard
    # enable = false
   
    [[Belchertown]]
        skin = Belchertown
        HTML_ROOT = /var/www/html/weewx/belchertown

        enable = true

What part of StandardReport is not commented-out? 

On Tuesday, March 31, 2026 at 2:50:27 PM UTC-4 Vince Skahan wrote:

    [[StandardReport]]
    # This is the old "Standard" skin. By default, it is not enabled.
    # skin = Standard
    # enable = false
   

 You need to comment it all out, or leave it uncommented and set enable=false.

On Tuesday, March 31, 2026 at 11:29:47 AM UTC-7 Eric Gammeter wrote:

Trying to get Belchertown skin to run, continual file location problem (file not found)

Debug info has all log, info and file list information.  No joy after multiple installation attempts.  Please let me know what you find.

Thank you-

/Eric

--
You received this message because you are subscribed to the Google Groups "weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/weewx-user/dabf03e5-0fa7-4795-9d72-5997f84ddf1en%40googlegroups.com.

[Vince Skahan]

Eric - you defined a [[StandardReport]] but did not tell the report generator where to find the skin.conf file in the appropriate subdirectory under the /etc/weewx/skins directory.

To have that report known to the report generator, but skipped, simply set enable=false ala:

[[StandardReport]]

   skin = Standard

   enable = false

To undefine that report completely, you could have commented it 'all' out ala:

# [[StandardReport]]

#   skin = Standard

#   enable = false

But your half-way variant is not valid.   Leave it uncommented and enable=false, or comment the whole report definition out completely.  The half-way measure you tried is not valid.

[Eric Gammeter]

Change made:

   #[[StandardReport]]

      # This is the old "Standard" skin. By default, it is not enabled.
      # skin = Standard
      # enable = false

    [[Belchertown]]
        skin = Belchertown
        HTML_ROOT = /var/www/html/weewx/belchertown

        enable = true

Doing this did eliminate the "file not found" issue.  

Still trying to get the Belchertown skin to show-up on my web site, and then get MQTT up and running.  Meantime, I have the default (or standard) WEEWX report active, but:  There is no formatting/style information is appearing at my web site ftp (/Weather), see attached screen shot files, along with a "weedebug_4.info" file.    

[John Smith]

There is no formatting/style information is appearing at my web site

If you hit F12 in your browser and then click on the network tab and then refresh the page check for URLs that fail to load, most likely CSS files if styles aren't loading.

Could be anything from files missing on your webserver to plugins blocking the browser from actually downloading them.

--
You received this message because you are subscribed to the Google Groups "weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/weewx-user/a3b14314-0c7e-4a1d-b3de-c608aba60e27n%40googlegroups.com.

[Eric Gammeter]

results:

GEThttps://oakorchardweather.net/seasons.css[HTTP/2 404 247ms]

GEThttps://oakorchardweather.net/seasons.js[HTTP/2 404 28ms]

Loading failed for the <script> with source “https://oakorchardweather.net/seasons.js”. oakorchardweather.net:12:30

Uncaught ReferenceError: setup is not defined

    onload https://oakorchardweather.net/:1

oakorchardweather.net:1:1

[Eric Gammeter]

Looks like Belchertown Skin is not active.  I do not know why.

[John Smith]

When I checked the link in your previous email I got certificate warnings, but 404 errors usually come from the server because the file requested doesn't exist, check the file system on your server to see if they were copied from the weeWX skin directory to the html directory.

To view this discussion visit https://groups.google.com/d/msgid/weewx-user/9db4e544-4969-4cd6-84f9-752c3b363eaen%40googlegroups.com.

[Eric Gammeter]

You get the certificate warning because my site is NOT https, only http.    

[John Smith]

It must also be listening on port 443 and sending a certificate otherwise I'd get connection refused errors.

In which case that might be why you are getting 404s, the web pages are telling the browser to use https for the CSS files.

To view this discussion visit https://groups.google.com/d/msgid/weewx-user/92bc7604-f18a-4d31-bc69-f39741ad0816n%40googlegroups.com.

[John Smith]

Nope getting 404s for http requests too

[John Smith]

It's a little note worthy that if you view page source on 404 files there is actually html and it tries load ad content using javascript or in an iframe from searchvity.com.

Given that domain points to a different IP, has your server been compromised?

[Eric Gammeter]

Ok.  I will be checking on the situation.  Thanks much for your input.  /Eric

Get Outlook for Android

---

From: weewx...@googlegroups.com <weewx...@googlegroups.com> on behalf of John Smith <deltafo...@gmail.com>
Sent: Friday, April 3, 2026 10:31:47 AM
To: weewx...@googlegroups.com <weewx...@googlegroups.com>
Subject: Re: [weewx-user] Re: File location and ROOT error with Belchertown Skin

 

You received this message because you are subscribed to a topic in the Google Groups "weewx-user" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/weewx-user/WZI7qCJUQSw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to weewx-user+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/weewx-user/CAGTinV5gBwZj%2BdWTEgXiNBd0fYGHZdYcTC_53POBTMsfvGwJOg%40mail.gmail.com.

[Vince Skahan]

Eric -  weewx seems running and both skins show updates at 11:30 EDT (15 minutes ago) which is ok based on your unusual 1800 second archive interval.

As always - if you do not post any logs, you are making the odds of getting help decrease significantly...

For your CSS and JS issues, you are either missing the files in your /var/www/html target directories 'or' your permissions are wrong in the target directories.  Only the weewx and/or webserver logs will say which is the case.   My guess in the absence of logs is permissions.  Did you touch anything manually ?

FWIW - the javascript console seems to indicate you are missing all of the .js and .css files from each skin.   Simply copy them from under /etc/weewx into the expected places in your /var/www/html tree and make sure the permissions permit the webserver process to read them and everything should work ok.  I've appended screenshots from the javascript console which list them out.

[Eric Gammeter]

Still working at getting BT skin to work (ie:  show-up on my web site).  I do not see any errors in the log that would clue me-in.  ??  Attached is my INFO file with LOG and DEBUG. 

Thank you-

/E

[Vince Skahan]

It's working fine. You need to give it the appropriate URL to open.....

[Eric Gammeter]

That is great!  I certainly did not see it-  not expecting to have to put /belchertown on the end of the url. What am I missing on getting it to happen without adding /belchertown?

[Eric Gammeter]

Straightened-out web pointer and all is good now! Thank you much.