This message was deleted.
# support
s
This message was deleted.
p
Hi @Nishant singh đź‘‹ can you verify that provided bucket name and S3 credentials are correct?
did you check clickhouse logs? anything related to S3 there?
in past, we have noticed that config changes via volume mount, not propagating with docker-compose. And it required removing the existing container and spawning them again.
n
credentials are correct. I haven’t checked the logs will give you a follow up on this. Also I am running the existing container after updating the config with docker compose restart