forever loading about weather-bar-app

[GregC-cyber]

I have the same issue, and here are my observations:

It worked on my units at home until my router died last week (on Saturday, January 20, 2024). I installed a slightly newer but still old backup router of the same manufacturer (Netgear) and then it got the 'foever loading.' No change in DNS servers or firewall. I'm thinking the it's a port or ports that are now blocked, and I didn't have any forwarded in the original router to begin with.

Next, it works at work if I FIRST boot the PC on a emergency backup WiFi network that is a totally open, direct connection to the ISP (AT&T). I can then switch to one of the internal production networks that run through various edge gear including a hardware firewall and it continues to work, even on our most 'secured' line (all on Comcast). However, if I boot the PC and it connects to any of the internal networks first, I will again get the 'forever loading,' even if I switch to the backup WiFi afterwards. I have to open it first on the direct open connection and THEN switch networks. Once it's opened it stays running very well all day, updates etc.

Seems like it is may be a port issue that once that's opened on the PC and communication is active on it the other network gear
lets it continue until I break the communication.

I'd like someone's thoughts on this and perhaps the ports that Weather Bar opens so I can test that as well. I've set Windows Defender here to let allow the app, but as I've said, whether it works properly or not is dependent on which network I boot to first.

Greg C-cyber

[manifestinteractive]

This app only uses standard web ports. If you have access to the Internet from your computer, it's not a port issue unless you've got some software installed that blocks Internet traffic on an app level. If you do, I'd check that app to see if you created a rule to block traffic.

But if you're seeing a loading screen, the app can detect an Internet connection ( otherwise you'd see an offline screen ). The loading screen is only shown when an Internet connection is detected, a request for data is made, and the app is waiting for the results that never come, which would happen if the app is blocked from getting online.

[Cola-Schmola]

@GregC-cyber Hi, so did you manage to solve the problem? Please share the solution if you have one :)

[GregC-cyber]

I haven't found a solution as yet. The app is on the accepted program list in the firewall, IP to the app is allowed in/out, all ports are allowed to it. I've tested various firewall settings, turning the firewall off, turned the antivirus off, turned off the antimallware, and still no success. I've checked my router settings and there isn't anything tricky there, should just be straight through to my PCs. I've pinged the WeaterBar app site IP with no issues and with the Digital Ocean host as well, no issues. No issues with any other Internet connections. I tried an https brower connection the WeatherBar ip, the browser said the As I said before the only thing that changed on me was that my original router died, I replaced it with a newer one after about an hour and that because there was that bit of time that elapsed installing and configuring the replacement router, Comcast assigned me a different dynamic IP address. I'm thinking this has to be key because I had 2 units where WeatherBar was working up to the moment my router went, and then later WeatherBar no longer worked. Not a thing was changed on my laptops, they were just sitting there idle waiting for the new connection.. I say it's something ISP related as I've also previously mentioned I have the situation at my employer where if I start the app on our backup network ISP without any firewall it works flawlessly. If I start it on our regular production network it "continuously loads". I have to start it on the unprotected no firewall network first to get it running then switch to the production network and it will continue to work.. I could check this by bringing my personal laptop to work and trying that sometime, however they discourage personal devices on the network there. I've tried an https browser connection to the IP address the app appears to call, 159.203.76.158, got "NET::ERR_CERT_COMMON_NAME_INVALID" and "This server could not prove that it is *159.203.76.158*; its security certificate is from *api.weatherbarapp.com <http://api.weatherbarapp.com>*. This may be caused by a misconfiguration or an attacker intercepting your connection." I'd tried this as I see that the app opens port 443 and wanted to see if there was a problem there. But regardless, it still works at my job site. For what it may be worth, pinging "api.weatherbarapp.com" fails, and of course pings might also be blocked there. I've seen this happen randomly few-and-far-between on my home Cmcast connection in the past, but it's always come back. It's been several weeks now, and my time and sorry skillset is limited as to what remains for me to test.

…

On Wed, Feb 28, 2024 at 10:41 AM Cola-Schmola ***@***.***> wrote: @GregC-cyber <https://github.com/GregC-cyber> Hi, so did you manage to solve the problem? Please share the solution if you have one :) — Reply to this email directly, view it on GitHub <#56 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BFTODRAU7TXU2PRZX4YRDRLYV5M3RAVCNFSM6AAAAABCAZWV6KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRZGM4TGMJWHA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[Cola-Schmola]

I haven't found a solution as yet....

wow! thank you for such a thorough and detailed response. I can see that you understand what you are writing about and have a great understanding of computers in general! Well, let's hope we get some help ;)