R
RunPod2mo ago
tzk

S3 uploads have stopped working - despite environment variables set up for template

My worker is not uploading to S3 - despite me setting up the environment variables for S3 in the template. The error in the log is "No bucket endpoint set, saving to disk folder 'simulated_uploaded'" - Interestingly this worked fine previously. I just created a new image and it no longer works. Can you advise on waht to do?
Solution:
@tzk you have wrong ENV names
Jump to solution
11 Replies
nerdylive
nerdylive2mo ago
Maybe set the proper env variable for s3 fjrst Edit template
tzk
tzk2mo ago
yep - I done that and made sure the variables are all correct in the template. However still the same result
Marcus
Marcus2mo ago
Maybe a regression of the bug fix when the environment variables in serverless got lost. https://discord.com/channels/912829806415085598/1185333521124962345/1250186174702551050
tzk
tzk2mo ago
Thanks for this context - I'll try the "Please note that you may have to scale down your workers to 0 and back up again to update your workers." step and try again Unfortunately, issue still persists
nerdylive
nerdylive2mo ago
hmm @Madiator2011 (Work) try sending your endpoint id here too
Madiator2011
Madiator20112mo ago
hmm
nerdylive
nerdylive2mo ago
hmm he's having trouble with the s3 upload function on runpod, madiator
tzk
tzk2mo ago
oh thanks @nerdylive and @Madiator2011 (Work) - it's 3nptpzriu3mt37
Solution
Madiator2011 (Work)
@tzk you have wrong ENV names
Madiator2011 (Work)
BUCKET_ENDPOINT_URL BUCKET_ACCESS_KEY_ID BUCKET_SECRET_ACCESS_KEY and it your case one env is saved as SECRET_ACCESS_KEY
tzk
tzk2mo ago
oh man - that was so dumb of me and thank you so much. I didn't copy and pasted correctly thanks
Want results from more Discord servers?
Add your server