Has anyone gotten ente to work with minio?

When trying to upload I am currently getting a 403 forbidden with:

<?xml version="1.0" encoding="UTF-8"?>
<Error><Code>SignatureDoesNotMatch</Code><Message>The request signature we calculated does not match the signature you provided. Check your key and signing method.</Message><Key>1234567890123456/abcdef12-3456-7890-abcd-efghijklmnop</Key><BucketName>b2-eu-cen</BucketName><Resource>/b2-eu-cen/1234567890123456/abcdef12-3456-7890-abcd-efghijklmnop</Resource><RequestId>1234567890123456</RequestId><HostId>1234567890123456abcdef1234567890123456abcdef1234567890123456abcdef</HostId></Error>

<?xml version="1.0" encoding="UTF-8"?>
<Error><Code>SignatureDoesNotMatch</Code><Message>The request signature we calculated does not match the signature you provided. Check your key and signing method.</Message><Key>1234567890123456/abcdef12-3456-7890-abcd-efghijklmnop</Key><BucketName>b2-eu-cen</BucketName><Resource>/b2-eu-cen/1234567890123456/abcdef12-3456-7890-abcd-efghijklmnop</Resource><RequestId>1234567890123456</RequestId><HostId>1234567890123456abcdef1234567890123456abcdef1234567890123456abcdef</HostId></Error>

I set mc admin config set h0/b2-eu-cen api cors_allow_origin="*" but I suspect I also need to set allowed headers somehow. I tried to set a cors.xml like this:

<?xml version="1.0" encoding="UTF-8"?>
<CORSConfiguration xmlns="http://s3.amazonaws.com/doc/2006-03-01/">
<CORSRule>
    <AllowedOrigin>*</AllowedOrigin>
    <AllowedMethod>GET</AllowedMethod>
    <AllowedMethod>PUT</AllowedMethod>
    <AllowedMethod>POST</AllowedMethod>
    <AllowedMethod>DELETE</AllowedMethod>
    <AllowedMethod>HEAD</AllowedMethod>
    <ExposeHeader>X-Amz-Request-Id</ExposeHeader>
    <ExposeHeader>X-Amz-Id-2</ExposeHeader>
    <ExposeHeader>ETag</ExposeHeader>
    <AllowedHeader>*</AllowedHeader>
</CORSRule>
</CORSConfiguration>

<?xml version="1.0" encoding="UTF-8"?>
<CORSConfiguration xmlns="http://s3.amazonaws.com/doc/2006-03-01/">
<CORSRule>
    <AllowedOrigin>*</AllowedOrigin>
    <AllowedMethod>GET</AllowedMethod>
    <AllowedMethod>PUT</AllowedMethod>
    <AllowedMethod>POST</AllowedMethod>
    <AllowedMethod>DELETE</AllowedMethod>
    <AllowedMethod>HEAD</AllowedMethod>
    <ExposeHeader>X-Amz-Request-Id</ExposeHeader>
    <ExposeHeader>X-Amz-Id-2</ExposeHeader>
    <ExposeHeader>ETag</ExposeHeader>
    <AllowedHeader>*</AllowedHeader>
</CORSRule>
</CORSConfiguration>

But no such luck, I get the following error:

mc: <ERROR> Unable to set bucket CORS configuration for h0/b2-eu-cen. A header you provided implies functionality that is not implemented.

mc: <ERROR> Unable to set bucket CORS configuration for h0/b2-eu-cen. A header you provided implies functionality that is not implemented.

Don't worry I set in my compose.yaml:

  web:
    ...
    # Modify these values to your custom subdomains, if using any
    environment:
      ENTE_API_ORIGIN: https://ip.com
      ENTE_ALBUMS_ORIGIN: https://ip.com

  web:
    ...
    # Modify these values to your custom subdomains, if using any
    environment:
      ENTE_API_ORIGIN: https://ip.com
      ENTE_ALBUMS_ORIGIN: https://ip.com

Also my s3 looks like this:

s3:
      are_local_buckets: true
      b2-eu-cen:
         key: <redacted>
         secret: <redacted>
         endpoint: https://ente.ip.com
         region: eu-central-2
         bucket: b2-eu-cen

s3:
      are_local_buckets: true
      b2-eu-cen:
         key: <redacted>
         secret: <redacted>
         endpoint: https://ente.ip.com
         region: eu-central-2
         bucket: b2-eu-cen

Any ideas?

6 Replies

Ducky•4mo ago

Remember to use /solved to mark your thread as solved once your question is answered.

sfrhel6•4mo ago

@codedcosmos are you not using the quick start script that setups up the minio container too ? If you are self hosting , you need specify the bucket endpoint as your own ip:3000 i.e where minio is listening?

codedcosmosOP•4mo ago

I did use the quick start script and I am using minio I wonder if nginx is in the way but not sure I'm getting

has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.

has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.

now. I think I am in over my head

codedcosmosOP•4mo ago

I think I'm having similar issues to https://github.com/ente-io/ente/discussions/2546

GitHub

Minio with nginx and https not working · ente-io ente · Discussio...

Hello! I have the following problem: I have created ente photos as a container and also created the webapp as a container. Basically, both ente and the web app work. However, I always see empty pic...

codedcosmosOP•4mo ago

The nginx config here helped me https://aur.archlinux.org/cgit/aur.git/tree/minio-server-nginx.conf?h=ente-server-git

Ducky•4mo ago

-# If your issue is resolved, you can use the /solved command to close the thread. If not, use /unsolve to cancel. Thread marked as solved. It will be closed in <t:1752360878:R>. This thread is now closed.

Gaming

Programming

Has anyone gotten ente to work with minio?

Did you find this page helpful?