What problem are we encountering while trying to deploy our system to the playground?

pola · November 19, 2024, 3:59pm

dfx deploy resma-medical-clinic-frontend --playground

Uploading assets to asset canister…
WARN: This project does not define a security policy for some assets.
WARN: You should define a security policy in .ic-assets.json5. For example:
WARN: [
WARN: {
WARN: “match”: “*/”,
WARN: “security_policy”: “standard”
WARN: }
WARN: ]
WARN: Assets without any security policy: all
WARN: To disable the policy warning, define “disable_security_policy_warning”: true in .ic-assets.json5.
Fetching properties for all assets in the canister.
Done fetching properties for all assets in the canister. Took 106.181µs
Starting batch.
Staging contents of new and changed assets in batch 2:
/assets/icp-logo-e6583bc6.png 1/1 (98375 bytes) sha e6583bc632eb233ad949e095ca6cd7d7aeabd236a0e5f7fe11aff6f1fc7f8bc6 (with 7 headers)
/logo2.svg 1/1 (15139 bytes) sha 037eb7ae523403daa588cf4f47a34c56a3f5de08a5a2dd2364839e45f14f4b8b (with 7 headers)
/assets/index-6cb27694.css 1/1 (22022 bytes) sha 6cb27694e377e5f563c33f9dda707e9a815957842fe713f0f5e6a30ce92f05e0 (with 7 headers)
/index.html (gzip) 1/1 (357 bytes) sha c6ec2fb01f7252793b0148adc664610f5acfea366dd4b400de45f289c3f8638b (with 7 headers)
/favicon.ico 1/1 (15406 bytes) sha 4e8d31b50ffb59695389d94e393d299c5693405a12f6ccd08c31bcf9b58db2d4 (with 7 headers)
/assets/profile-94530c78.png 1/1 (11149 bytes) sha 94530c78ad7d92f2aded04a1d173e27be2551e0f27e5270272c3e5a16245c6b3 (with 7 headers)
/index.html 1/1 (533 bytes) sha 763bcab228181fbac688554ecd1383a5b4b0a43bf584a8cadd25eb93744c946d (with 7 headers)
/assets/index-6cb27694.css (gzip) 1/1 (5171 bytes) sha e8ba81fdf321118cddc10dc253096af1ed57cb988494d45413197632ac650ea7 (with 7 headers)
/assets/rxicon-973957d9.svg 1/1 (49657 bytes) sha 973957d9ce6e7d965b33a934a6d3ae47b8974b63da9c80b7012a5cd692008cfa (with 7 headers)
/assets/rx-0c4dd209.jpg 1/1 (71984 bytes) sha 0c4dd209f91b3ef8a800fdab90da509939a7239e4720bea1c2c6087846a40cf0 (with 7 headers)
/assets/hc-170e38e7.jpg 1/1 (52129 bytes) sha 170e38e7fe0b3113fde4574d0d6b3144b8ddd681dc6a1a781192c532b3ca3e5f (with 7 headers)
/assets/check-up-3a9df2fe.png 1/1 (96814 bytes) sha 3a9df2fe52faed4ead3241b82667e2f8a93793169d1b8342d11f4ed0f84d7b34 (with 7 headers)
Error: Failed while trying to deploy canisters.
Caused by: Failed while trying to install all canisters.
Caused by: Failed to install wasm module to canister ‘resma-medical-clinic-frontend’.
Caused by: Failed to store assets in canister ‘resma-medical-clinic-frontend’.
Caused by: Failed asset sync with canister w6dgu-3iaaa-aaaab-qadha-cai.
Caused by: Failed to create project asset: Failed to create encoding: Failed to create chunk: Failed to create chunk: The replica returned an HTTP Error: Http Error: status 500 Internal Server Error, content type “text/plain; charset=utf-8”, content: backend_timeout
Caused by: Failed to create encoding: Failed to create chunk: Failed to create chunk: The replica returned an HTTP Error: Http Error: status 500 Internal Server Error, content type “text/plain; charset=utf-8”, content: backend_timeout
Caused by: Failed to create chunk: Failed to create chunk: The replica returned an HTTP Error: Http Error: status 500 Internal Server Error, content type “text/plain; charset=utf-8”, content: backend_timeout

Severin · November 19, 2024, 5:00pm

Status 500 can often be fixed by just retrying. Does it happen repeatedly?

pola · November 19, 2024, 5:30pm

Yes, we tried deploying multiple times and still prompting the same error.

Nimakra · November 19, 2024, 10:19pm

In your dfx.json, if the frontend canister’s gzip is set to true, try setting it to false:

"gzip": false,

pola · November 20, 2024, 2:56am

the code still not working

Severin · November 20, 2024, 9:16am

Would you mind trying a few more times and sharing the canister id afterwards? We don’t see anything useful in the boundary node logs for w6dgu-3iaaa-aaaab-qadha-cai

willguest · November 29, 2024, 9:33am

I’m having the same issue - I have tried and failed to deploy about a dozen times in the last day.

The error is the same, and started showing up in dfx 0.20.0, when I switched to using compressed builds. On that version I could only get brotli compression to work. Switching to 0.21.0 seemed to fix the issue but now it has returned.

I have tried many things, including a project rebuild, adding (and then removing) ‘“gzip”: false’ from my dfx.json and restarting dfx with (and without) --clean and --background flags

One other observation - the upload (which is already slower than before) seems to hang for ~20 secs before the error appears.

I suspect it might have something to do with my .ic-asset.json file, which looks like this:

github.com

Exeud/exeudvr-canister/blob/develop/src/assets/.ic-assets.json

[
    {
        "match": ".well-known",
        "ignore": false
    },
    {
        "match": "**/*",
        "allow_raw_access": false,
        "headers": {
            "Content-Security-Policy": "default-src 'self';script-src 'self' 'unsafe-eval';connect-src 'self' https://icp-api.io https://*.icp0.io https://*.ic0.app;img-src 'self' data: https:;style-src * 'unsafe-inline';style-src-elem * 'unsafe-inline';font-src *;object-src 'none';base-uri 'self';frame-ancestors 'none';form-action 'self';upgrade-insecure-requests;require-trusted-types-for 'script';",
            "X-Frame-Options": "DENY",
            "Referrer-Policy": "same-origin",
            "Strict-Transport-Security": "max-age=31536000; includeSubDomains",
            "X-Content-Type-Options": "nosniff",
            "X-XSS-Protection": "1; mode=block",
            "Permissions-Policy": "accelerometer=(self), ambient-light-sensor=(self), autoplay=(self), battery=(), camera=(), cross-origin-isolated=(), display-capture=(), document-domain=(), encrypted-media=(), execution-while-not-rendered=(), execution-while-out-of-viewport=(), fullscreen=(self), geolocation=(), gyroscope=(self), keyboard-map=(), magnetometer=(self), microphone=(self), midi=(), navigation-override=(), payment=(), picture-in-picture=(), publickey-credentials-get=(), screen-wake-lock=(), sync-xhr=(), usb=(), web-share=(), xr-spatial-tracking=(self), clipboard-read=(), clipboard-write=(), gamepad=(), speaker-selection=(), conversion-measurement=(), focus-without-user-activation=(), hid=(), idle-detection=(), interest-cohort=(), serial=(), sync-script=(), trust-token-redemption=(), unload=(), window-placement=(), vertical-scroll=()"
        }
    },
    {
        "match": "**/*.loader.js",

This file has been truncated. show original

Severin · November 29, 2024, 1:51pm

I really don’t know what’s happening

That I’m pretty sure does not affect anything. The error looks more like something with the protocol. .ic-assets.json5 is an application-layer thing for the asset canister content

Henn91 · November 29, 2024, 7:08pm

Just build us website where we can build, test and than deploy our canisters. The less moving parts the better.

Topic		Replies	Views
Custom domain: Assets without a security policy "all" Developers	2	45	October 29, 2024
Up to date documentation - dfx - asset canister redirect urls Developers Documentation	1	21	November 14, 2024
Assigned: BNT-13 - Motoko Certified Assets Canister Bounties	16	1028	November 25, 2024
Dfx 0.14.4 is promoted Developers	0	243	September 6, 2023
Dev Blog: Introducing `dfx deploy --playground` Education dfx , dev-update , dev-blog	8	580	February 9, 2024

What problem are we encountering while trying to deploy our system to the playground?

Related topics