Integrating Thumbnails and Reviewables fails when media is > 1Mb

General
,
1

Since we’ve updated Ayon server and pipeline and moved our server we are now unable to completely publish a reviewable. It dies during the integration and we’re getting an HTTP error response 413: Request Entity Too Large for URL when trying to publish reviewables.

If the thumbnail or the mp4 generated after running the Maya playblast is done and an mp4 generated, exceeding 1Mb causes it to fail in trying to POST to ayon server to then go to ftrack. Couldn’t find any configuring settings to set the limit since in Ayon settings. Never had problems before publishing reviewables before the update. Why would the http server have it’s max payload changed. Anyone else come across this problem?

INFO: Uploading reviewable 'h264' ...
INFO: Uploading reviewable S:\_Projects\<Game>\Ayon\<GameStudio>\Sequences\TST\TST_sh0010\publish\review\reviewMain\v002\NntG_TST_sh0010_reviewMain_v002_h264.mp4
DEBUG: <AyonEndpoint> "POST /api/projects/<GameStudio>/versions/e0afceab859b11efa3f0bcf1716c8d5a/reviewables?label=h264 HTTP/1.1" 413 183
Traceback (most recent call last):
File "C:\Users\<User>\AppData\Local\Ynput\AYON\dependency_packages\ayon_2406251801_windows.zip\dependencies\pyblish\plugin.py", line 528, in __explicit_process
runner(*args)
File "C:\Users\<User>\AppData\Local\Ynput\AYON\addons\core_1.0.0\ayon_core\plugins\publish\integrate_review.py", line 28, in process
self._upload_reviewable(project_name, version_id, instance)
File "C:\Users\<User>\AppData\Local\Ynput\AYON\addons\core_1.0.0\ayon_core\plugins\publish\integrate_review.py", line 85, in _upload_reviewable
ayon_con.upload_file(
File "C:\Users\<User>\AppData\Local\Ynput\AYON\app\AYON 1.1.0\dependencies\ayon_api\server_api.py", line 1980, in upload_file
return self.upload_file_from_stream(
File "C:\Users\<User>\AppData\Local\Ynput\AYON\app\AYON 1.1.0\dependencies\ayon_api\server_api.py", line 1940, in upload_file_from_stream
return self._upload_file(
File "C:\Users\<User>\AppData\Local\Ynput\AYON\app\AYON 1.1.0\dependencies\ayon_api\server_api.py", line 1899, in _upload_file
response.raise_for_status()
File "C:\Users\<User>\AppData\Local\Ynput\AYON\app\AYON 1.1.0\dependencies\requests\models.py", line 1021, in raise_for_status
raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 413 Client Error: Request Entity Too Large for url: http://<AYON_SERVER>/api/projects/<GameStudio>/versions/e0afceab859b11efa3f0bcf1716c8d5a/reviewables?label=h264
3

Could you report your versions for:

  • ayon_core (seems like 1.0.0?)
  • ayon_api (should be from dependency package)

And also the running AYON server?

4

Ayon server 1.4.1+202409161539
Ayon 1.1.0

ayon_core (1.0.0)
ayon_api (1.0.9)
“”“Package declaring Python API for AYON server.”“”
version = “1.0.9”

There’s one thing that is unusual which I had posted on discord but didn’t get a reply. Not sure if it’s related. I posted this:

“Im running into a problem getting my deadline render publish and seeing a strange exception error on the Submit Image Publish step. Basically I’m on Launcher 1.1.0, core 1.0.0, deadline 0.3.1). What’s strange is that the Server timed out exception is in C:\Program Files\Ynput\AYON 1.0.0-rc.2\dependencies\ayon_api\server_api.py. This is an old installation of ayon pipeline that still exists before I upgraded to C:\Program Files\Ynput\AYON 1.1.0 which is the pipeline that is running. How is server_api.py being called using an old pipeline path yet everything else is running under the new pipeline path? Here’s the error log”

5

Hi @acheng,

This issue sounds similar to what came up on Ynput discord here. (I think you are both at the same studio - so likely same issue.)

Someone there replied:

Do you have ayon behind nginx or anything?
If so, try client_max_post_size

Note: I think they meant client_max_body_size

Which seemed to solve it there :white_check_mark:

So, using nginx?

See NGINX client_max_body_size in their docs which does indeed default to 1m

By default, NGINX® has a upload limit of 1 MB per file. By editing client_max_body_size, you adjust the file upload size. Use the http, server, or location block to edit client_max_body_size. Changes to the http block affect all server blocks (virtual hosts).

So raise that setting.

6

Thank you for following up BigRoy. Yes, indeed this has just been resolved and thumbnails/reviewables are publishing properly again! Knew migrating servers who throw us some curveballs.