Tommy Penner

@ferencb @SMCDevel3 On June 15 we pushed a fix for the issue where the API returned `null` for some fields, including the `"upload"` object. If you guys are still having...

@hitendra2f Has your local environment been properly provisioned? Did you install the Vimeo library via Composer? Can you try running `composer install`?

Hi @dumbeau this is a known issue on the Vimeo backend, with `transcode.status` returning `complete` prematurely. As a workaround, check the `is_playable` field from the response instead. This will return...

The password is only used with the Vimeo Player; it's not exposed using the API. However, you can update the password by editing the video: https://developer.vimeo.com/api/reference/videos#edit_video

Your authentication token allows you to edit the video's settings -- you don't need to know the password.

What version of TLS is configured on your end? Vimeo only accepts TLS 1.2 and newer connections, in compliance with [internet-wide](https://www.digicert.com/blog/depreciating-tls-1-0-and-1-1/) [security mandates](https://blog.pcisecuritystandards.org/are-you-ready-for-30-june-2018-sayin-goodbye-to-ssl-early-tls).

Check your configuration and verify that you're connecting to Vimeo using a TLS 1.2 connection, that should resolve the SSL error.

@brucemcpherson can you link to the video or provide the video id?

@nimisis Can you provide the exact `"name"` value used on upload? From there we can test, thanks.

@nimisis It looks like the forward slash character (among other characters) is omitted when providing the information as part of the first tus upload request. We have a fix for...