I wanna test out the codebase feature
I wanna test out the codebase feature but getting this error?

23 Replies
i have object store is set in the instance
Is it set in the workspace settings?

also yes

double check the workspace you are sending it to
wmill workspace
but yes it's saying the instance object store is not configured
i deployed with helm to eks cluster might be due to that ?
no
removed & reauthed same error.
did you save the instance settings with the s3 configuration?
yes also test from server & worker. is ✅
trying verbose to see details

can you restart your servers please

when did you save the settings?
found a interesting clue
let me double check this
oh very interesting looks like thats bucket config was deleted but settings still show that like it didn't get unlinked.
gonna setup again.
that was dead-end i setup again but it's still same error.
restarting the
app
oh is this the reason/

2025-05-20T08:41:36.033699Z ERROR Bad config: Object store is required for snapshot script and is not configured for servers error=BadConfig("Object store is required for snapshot script and is not configured for servers") target=windmill_common::error span={"email":"neco@nokta.dev","method":"POST","traceId":"d86b1481-b178-42f4-930c-697347cc5931","uri":"/api/w/quera/scripts/create_snapshot","username":"neco","workspace_id":"quera","name":"request"}
still no luck after a restart.
how can i test storage is set correctly or not ?
it's the reason above, s3 instance storage is not available on the pro plan
I forgot you were on the pro plan
although, the restriction was originally for the shared cache. We could have it work somehow for snapshots
that would be nice; meanwhile i will upgrade to enterprise for this client case.
friendly feedback there's no button for upgrade to enterprise 😅 i need to cancel and reiniate the biliing process again.
👍
we have 95% of customers on EE so Pro plan is a bit left behind
bug report: now that i create new enterprise plan portal.windmill still shows the old account.
i guess stripe created 2 customer
anyways i got the apiKey i needed but can not access to portal
--- after math.
Still getting the same error
finaly worked had to delete s3 configs and recreate