Instant Terra Forum

Instant Terra => Support - How to ... ? => Topic started by: babe on March 18, 2022, 03:34:53 PM

Title: Tuto of WorldBrowser error 401
Post by: babe on March 18, 2022, 03:34:53 PM

Hello, J'ai suivie

I next the tutorial WorldBrowser, I obtains an error 401, there the detail :

" Connection error (An error occured, Error code : 401.)
  Check that you have a valid connection to the Internet. "

Why ? I not understand error, or is normal, iam sorry if, I speak bad in english. It not a my language national.

Title: Re: Tuto of WorldBrowser error 401
Post by: Alexis Vaisse on March 22, 2022, 03:17:21 AM

Hello,

The World browser uses external web sites, such as OpenTopography, to download the data.
It may happen that the OpenTopography site is down. In this case, you will get an error, for example error 401.

If you try again later, the site may be up and running again, and you will be able to complete the tutorial.

Title: Re: Tuto of WorldBrowser error 401
Post by: Erik on April 25, 2022, 07:24:00 AM

Hello, I'm getting the same error message and have verified that the OpenTopography website is not down. Could there be a potential problem with the API key that Instant Terra uses? 

I have also verified that it's not my firewall blocking the connection as I turned it off to test and get the same error either way.   Would love any help. Thanks!

Title: Re: Tuto of WorldBrowser error 401
Post by: Alexis Vaisse on April 25, 2022, 08:45:34 AM

You're right, it seems that the OpenTopography API has changed.
We will update Instant Terra so that it can use the OpenTopography API again.

Meanwhile, as a workaround, you can use the Mapbox data source with a free Mapbox key.

Title: Re: Tuto of WorldBrowser error 401
Post by: Erik on April 26, 2022, 02:54:13 AM

Oh great! I'll set up an account with Mapbox. Was hoping I didn't have to, but that's fine. Thanks!

Title: Re: Tuto of WorldBrowser error 401
Post by: Alexis Vaisse on May 07, 2022, 03:30:56 PM

Hi,

Instant Terra 2.5.1 is now available with a fix for this issue.