On item 1) I am using the season skin with weewx 3.9.1 and it is working 
fine in Edge (as is Belchertown)   The issue is almost certainly tied to 
your nginx configuration (Full disclosure, I am using apache)
On Item 2) I checked my system look for any already running error messages 
and I do not see that error occurring.

What OS and version are you running on your new pi?

On Friday, February 8, 2019 at 5:13:40 PM UTC-6, Walter Smith wrote:
>
> Sorry about the empty response a second ago.  I got a new Pi and got 
> version 3.9.1 on a clean install this morning.  All is working pretty well 
> and I like the new skins.  I had the following issues:
>
> 1.  The Microsoft Edge browser refuses to show any web pages.  I can see 
> them fine in Explorer and Firefox.  I do have a new IP address with the new 
> Pi but I've tried all sorts of reboots and InPrivate browsing and I still 
> can't get Edge to display anything.  It has to be Edge's fault because it 
> won't show the "Welcome to Nginx!" page either.
>
> 2.  I noticed but did not copy down or save an error message in the log 
> that was repeated at each interval, something to the effect of "can't start 
> thread X because another thread X is already running".  Sorry for the 
> imprecision.  
>
> Other than that it's doing well.  Some graphs are incomplete because I had 
> to copy over the old SQLite db file.  And it will catch up eventually?  I 
> ran wee_reports utility but it did not change the incomplete graphs.
>
> Thanks everyone for a great system.
>
> Walt
>
> On Wednesday, February 6, 2019 at 7:40:34 AM UTC-6, Thomas Keffer wrote:
>>
>> Well, that was a record short release. We found a serious bug in v3.9.0 
>> that could break skins that do not have fonts defined, such as cmon.
>>
>> So, we are releasing v3.9.1, found in the usual place 
>> <http://weewx.com/downloads/>.
>>
>> -tk
>>
>

-- 
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 [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to