# Recording URL downloads returning 403

**URL:** <https://devforum.zoom.us/t/recording-url-downloads-returning-403/77808>\
**Category:** Cloud Recordings\
**Created:** [October 24, 2022, 12:33pm UTC](https://devforum.zoom.us/t/recording-url-downloads-returning-403/77808 "2022-10-24T12:33:49Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![jacek.podgorski](https://avatars.discourse-cdn.com/v4/letter/j/ce73a5/32.png) [@jacek.podgorski](https://devforum.zoom.us/u/jacek.podgorski)\
**Post date:** [October 24, 2022, 12:33pm UTC](https://devforum.zoom.us/t/recording-url-downloads-returning-403/77808/1 "2022-10-24T12:33:49Z")

</div>

Our application started to crash when downloading recordings using rec/webhook\_download endpoint. We get 403 in response. There are no changes in code on our side. What changed during the weekend on the ZOOM side and how to fix it?  
Issue is super-urgent because it crashes our production business process…

---

<div class="post-metadata">

**Author:** ![b.pedersen](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/b.pedersen/32/42573_2.png) [@b.pedersen](https://devforum.zoom.us/u/b.pedersen)\
**Post date:** [October 27, 2022, 9:17pm UTC](https://devforum.zoom.us/t/recording-url-downloads-returning-403/77808/2 "2022-10-27T21:17:50Z")

</div>

A couple things observed in relation to our experience of this:

1. Does not occur with all zoom domains. All download urls for one site fail (403), while all for another site succeed (the failure is before the 302 redirect to common zoom backend API server).
2. It is only failing on linux - the same requests executed on windows are succeeding.  
edit:
3. further, querying the download url with a freshly updated cURL succeeds (on the linux box), while the application does not.

---

<div class="post-metadata">

**Author:** ![jacek.podgorski](https://avatars.discourse-cdn.com/v4/letter/j/ce73a5/32.png) [@jacek.podgorski](https://devforum.zoom.us/u/jacek.podgorski)\
**Post date:** [October 28, 2022, 5:20am UTC](https://devforum.zoom.us/t/recording-url-downloads-returning-403/77808/3 "2022-10-28T05:20:17Z")

</div>

Yes, correct. It occurs only on linux distributions. The problem is in SSL handshake and for some reason this SSL handshake process fails.  
We temporary solved the problem by forcing TLS 1.2 in our client application before initiating connection for download recordings. This is temporary fix and still waiting for response from ZOOM side because SSL handshake should be managed from operating system level, not code.

---

<div class="post-metadata">

**Author:** ![b.pedersen](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/b.pedersen/32/42573_2.png) [@b.pedersen](https://devforum.zoom.us/u/b.pedersen)\
**Post date:** [October 28, 2022, 7:45pm UTC](https://devforum.zoom.us/t/recording-url-downloads-returning-403/77808/4 "2022-10-28T19:45:08Z")

</div>

A bit more - per SSL labs, the cipher suites offered by different customer zoom sites and the backend zoom service are all quite different. Best we can tell, problem lies with attempting to use TLS 1.3.

---

<div class="post-metadata">

**Author:** ![ravi.sahu](https://avatars.discourse-cdn.com/v4/letter/r/8dc957/32.png) [@ravi.sahu](https://devforum.zoom.us/u/ravi.sahu)\
**Post date:** [November 2, 2022, 3:54am UTC](https://devforum.zoom.us/t/recording-url-downloads-returning-403/77808/5 "2022-11-02T03:54:08Z")

</div>

@elisa.zoom @donte.zoom Do you know if the team is looking into this.

---

<div class="post-metadata">

**Author:** ![gianni.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/gianni.zoom/32/32523_2.png) [@gianni.zoom](https://devforum.zoom.us/u/gianni.zoom)\
**Post date:** [November 2, 2022, 8:45pm UTC](https://devforum.zoom.us/t/recording-url-downloads-returning-403/77808/6 "2022-11-02T20:45:29Z")

</div>

Hi @ravi.sahu @b.pedersen @jacek.podgorski ,

Thank you for sharing this issue and teaming up to troubleshoot. Can you please each submit a [support ticket](https://devsupport.zoom.us/hc/en-us) for this issue with the following info as it sounds like a bug:

- account id
- full request/response
- screenshot and/or video of error
- a link to this forum thread

I’ll also flag internally to get the attention of our service engineers.

---

<div class="post-metadata">

**Author:** ![zoomuser](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/zoomuser/32/40795_2.png) [@zoomuser](https://devforum.zoom.us/u/zoomuser)\
**Post date:** [November 10, 2022, 1:37am UTC](https://devforum.zoom.us/t/recording-url-downloads-returning-403/77808/8 "2022-11-10T01:37:58Z")

</div>

I have the same issue when reproducing the download\_url into a web-based player, when pausing the video after a while returns 403 error code.

My application is playing the URL with the ?access\_token parameter, which keeps the video working a little longer but later crashes with 403 (Access Forbidden)

Any idea how to solve this issue?

 ![403_issue](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/5/4/54376b14c11c59dc19c404f59f685128a26e7c6a.png)

---

<div class="post-metadata">

**Author:** ![gianni.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/gianni.zoom/32/32523_2.png) [@gianni.zoom](https://devforum.zoom.us/u/gianni.zoom)\
**Post date:** [January 28, 2023, 12:46am UTC](https://devforum.zoom.us/t/recording-url-downloads-returning-403/77808/9 "2023-01-28T00:46:41Z")

</div>

Hi @zoomuser ,

This could be similar to what occurred here:

> [@Update: Recording download url 403 error](https://devforum.zoom.us/t/update-recording-download-url-403-error/5608):
>
> Hello Everyone, We apologize for any inconvenience that may have happen with the ability to use the cloud recording download url. Last weekend our backend team deployed a new security feature to fix a potential vulnerability with our recordings. However, since this security fix interrupted our valued customers downloading recordings with the download\_url, we are in the process of removing the change so that you can continue using the download\_url with the access token. Our Engineering team is…

If you’re still having this issue, please use the same guidance I shared above for submitting your bug ticket. Make sure you are logged into your developer account when you submit.
