Show the Local Weather: OpenWeatherMap Warning

Just a heads up to anybody thinking of using OpenWeatherMap to get their weather data for this project: to use the JavaScript geolocation API you have to be running over a HTTPS connection, if you’re running over a HTTPS connection then all your external API requests must also go over a HTTPS connection. The problem is that OpenWeatherMap only allow HTTPS requests if you pay them money.

I built my project using some test data that I grabbed from them (to prevent excessive API calls, which they limit to a certain number per hour) and so I only found out that my project wouldn’t actually work after I’d already built it around OpenWeatherMap. :weary:

Hopefully somebody reads this before making the same mistake.


You can use If you add this url before your api url, it should work:

1 Like

It takes a really long time then I get the error:

index.html:1 XMLHttpRequest cannot load No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin '' is therefore not allowed access. The response had HTTP status code 522.

Seems like is down… should work though.

Perfect timing. :anguished::grinning:

I think I’ll just cut my losses and switch to the Dark Sky API.

The other link works.[quote=“BenGitter, post:4, topic:60292”] should work though.

I decided to use google geolocation APIs as a replacement to navigator.geolocation.
Here is more about it: The Google Maps Geolocation API

That Google API is very inaccurate. It thinks I’m 123 miles away.

So is this any good then Ben? I tried the one a while ago and found it took forever to make requests.

Well this link seems to be up all the time (that isn’t working). Unless you want to use your app regularly, I don’t see a problem. I suppose it is not a clean solution to add such a link to your api url, but it works great as a quick fix. If you now upfront that you will need this, you might want to search for another api.

But, I have’t used cors-anywhere much, so I don’t know if it is faster.

1 Like

From a cursory glance at the Twitter account it seems it isn’t a new problem. I guess they just don’t have enough bandwidth/resources and so the server gets overloaded.

must be someones bootcamp project :smiley:

Or…you just stick with using HTTP:

Take a look at this link The site allows 1000 API requests a day (should be more than enough for the project).

And just using this site a simple jquery call should allow you to use your existing HTTP javascript.

$.get(“”, function(response) {
console.log(response.ip, response.loc);
}, “jsonp”)

For background on this issue, see:

Here’s what I’d recommend:

  • Use navigator.geolocation and fall back to an IP-based location API if that fails.Here’s a basic example on how to do that:
  • Use a weather API that supports both HTTP and HTTPS, like Weather Underground, Apixu, or Dark Sky.

Lots of people hit this issue regularly, hopefully the project guidelines will be updated with more information soon.

I had the same problem with codepen. I finished my weather app a while ago, and when I tried using it recently, it didn’t work. Well, while struggling to figure out what to do, I realized I could try accessing my codepen using HTTP instead of HTTPS. Viola! It works now.

Basically a simple solution is to make sure campers share their codepen link using HTTP.

In my case my problems aren’t over, since I just moved my portfolio to a vps, and I’m serving all content through HTTPS ( I’m planning on having every app live in a subdomain, which will be served through HTTPS as well… I guess I’ll have to make nodejs handle the json request on the server or something similar. Though I’m new to nodejs…