[image] Used to work fine till v0.11.2 Thoughts?

No worries, I figured it out. It’s quite straightforward. For future readers, the way to do it is to run gzip right after the build step. DFX picks it up automatically. Like this: dfx build <canister_name> gzip -f -1 ./target/wasm32-unknown-unknown/release/<canister_name>.wasm

BUG: Since upgrading to dfx v0.12, running into "Failed to install wasm. The replica returned an HTTP Error: Http Error: status 413 Payload Too Large"

Developers Command Line Tools

saikatdas0790 November 16, 2022, 4:31pm 20

Yeah, they are significantly smaller now. I was even able to upgrade to dfx v0.12 due to this. These are my wasm sizes now

1 Like

Possible BUG: Running into "Payload Too Large" error even though my canister is around 1 MB in size

Topic		Replies	Views
Possible BUG: Running into "Payload Too Large" error even though my canister is around 1 MB in size Command Line Tools	21	1145	January 15, 2024
Canister Install returned Http Error: status 413 Payload Too Large Developers	1	789	November 22, 2021
Dfx 0.16: Wasm module is too large Language Support Wasm	4	290	February 1, 2024
Issue with deploying to playground Developers	3	168	May 15, 2024
Dfx deploy gzip Developers	1	269	October 10, 2023

BUG: Since upgrading to dfx v0.12, running into "Failed to install wasm. The replica returned an HTTP Error: Http Error: status 413 Payload Too Large"

Related topics