Dropbox API not available

Dear Michael

This sensor message looks like the Dropbox webservice is either currently not avialable, or the access is blocked from your location. Please manually check https://api.dropbox.com/1/oauth2/token

Do you get an error message because you did not post any data, or is that URL not reachable?

It appears the health-check is no longer returning the expected response.

https://api.dropbox.com/1/oauth2/token

{"error": "Call requires one of the following methods: POST, OPTIONS. Got GET."}

Hello,

please update PRTG in that case. I checked with the current version 20.4.64, the Common SaaS sensor shows 100%. Though historic data of that sensors shows that Dropbox is sometimes reported as not responding, it looks like temporary issues with the Dropbox API access.

Hi there!

I already have the 20.4.64.1402 PRTG version installed (the latest available) and still have the “Dropbox API not available” warning message at Common SaaS Check Sensor.

I am able to access the following link (from my PRTG server): https://api.dropbox.com/1/oauth2/token

And I receive the next response from this URL: {"error": "Call requires one of the following methods: POST, OPTIONS. Got GET."}

Hope you can help me. Thanks in advance!

We have exactly the same problem.

Version currently installed: 20.4.64.1402+ Selected release channel: Stable Latest version available from Paessler: 20.4.63.1427

BTW: Have you withdrawn the last release?

Hello, the release was not redrawn, but with the auto-update we enable the rollout in waves.

The API URLs we use usually result in an error because we don't apply an API key. However in our test instances, the dropbox API is always down now. The case is under investigation as the cause is not yet clear.

Same issue here:

probe device sensor (Common SaaS Check) claims: "88 % (Available Services) is below the warning limit of 90 % (Dropbox API not available)".

Any news on a fix please?

Any update on this? Why do I care about the DropBox API anyway? We do not use DropBox in our org.

Any update on this? Issue only started appearing last week. Thanks

Hello Chris and Sarah,

We are still investigating on this case. In the meantime, you have the possibility to create the sensor anew and deselect the check box corresponding to Dropbox. Afterwards, the sensor won't be in warning state anymore.

Please, notice that removing the sensor will also remove its historical data.

Kind regards.

Hello Norman,

Thank you for your message, I indeed added a short notice regarding the option to remove the sensor as it will of course delete the historical data.

Regarding the issue, a fix is already at the implementation stage and therefore, will probably be released in the next version of PRTG (21.1.65) planned earlier in January.

Regards.

Did the endpoint change for some reason? I came here to ask the same question. The PRTG logs do not show the endpoint: https://api.dropbox.com/1/oauth2/token

they show Endpoint URL: https://www.dropbox.com/1/oauth/authorize

Instead. The api.dropbox.com/.... does return a valid response

I am on the latest stable build also. These details were found by enabling result handling.

Hello Wayne,

It seems that Dropbox stopped using the URL address used by the sensor, indeed. And therefore, we have planned to change it for the next version of PRTG. Thank you for your message.

Regards.

How do we stop it in the meantime?

Hello Chris,

There is no option to remove existing providers when the sensor is created, however you have the possibility to modify the notification triggers or create the sensor anew and deselect the check box related to Dropbox.

Regards.