etranger7

You're right. When I asked Amazon Q about this, it's telling me that this is happening because: `The error you're encountering - "AccessControlListNotSupported: The bucket does not allow ACLs" -...

My current setting is ACL: private CORS policy of the AWS s3 bucket: ``` [ { "AllowedHeaders": ["*"], "AllowedMethods": ["GET", "HEAD"], "AllowedOrigins": ["*"], "ExposeHeaders": [] } ] ``` and it...

Could the CORS policy be what's doing the overriding? Until I set the CORS policy, the stream was unwatchable.

No problem :) Thanks for looking into it. I think it's great that this information can be exposed so that it can be tracked.

I believe AOL is using a catchall like Yahoo. What happens if you use the "headless" verification method?

What does this read -p "Enter the port you want nginx to expose: " NGINX_SERVICE_PORT refer to? Is it referring to the port that most people would pick 443 or...

@prakashoriga if you're getting zero views, I'd suggest making sure you included {{ TrackView }} in the template that you're using. Without it, it won't track views at all.

Thank you for your reply @nosnilmot I'm not sure how much I need to provide but here are the logs a around the time when SIGTERM is received: ``` 2024-09-24...

Makes sense. I just checked and when I intentionally stop the container, the logs also show SIGTERM followed by a bunch of services being stopped and ending with the "cancelling...

After further investigation, we concluded that this is caused by using ``` docker compose up ``` instead of ``` docker compose up -d ``` We're running docker in non-root mode...