lorrod

Hello! I tried to pass input entity of the chat, it still raises the same error. Only fix which I described helps. Thank you.

I think the main reason caused links which are required admin approval to join. I have tested regular links - it is working Admin approval links are not working

Have the same problem, did you solve that?

The method modify_dn() with the parameter "accountExpires" set to 0 can be used to set an account to "never expire" in Active Directory over LDAP. The accountExpires attribute in Active...

+1 in queue :) I believe this will bring much more users to plane.

Thank you for your quick response, unfotunately the issue is still exist.. I have updated env vars of registry container: ```yaml environment: REGISTRY_STORAGE_FILESYSTEM_ROOTDIRECTORY: /registry REGISTRY_STORAGE_DELETE_ENABLED: 'true' REGISTRY_HTTP_HEADERS_Access-Control-Allow-Origin: '[https://ui.registry.external.url.com]' REGISTRY_HTTP_HEADERS_Access-Control-Allow-Methods: '[HEAD,GET,OPTIONS,DELETE]'...

Sure, here it is Here is copied request with 401 response: curl 'https://ui.registry..com/v2/_catalog?n=1000' \ -H 'authority: ui.registry..com' \ -H 'accept: */*' \ -H 'accept-language: en-GB,en-US;q=0.9,en;q=0.8' \ -H 'referer: https://ui.registry..com/' \...

Yes, as you can see above, configuration option REGISTRY_SECURED is set to true... I attach a screenshot of 401 response headers, yes, "WWW-Authenticate" is presented and equals to `Bearer realm="https://git..com/jwt/auth",service="container_registry",scope="registry:catalog:*"`...

Hello! Thank you for staying in contact! Sorry for late response, we have switched our focus... I tried to use this image `joxit/docker-registry-ui:latest` but it comes with different sha `sha256:899f61697a3d269aa1a6c14cbcf6f5c21480804854496bb1e6e9e4fabf758b36`....

I have tried, no luck, sorry! Is there anything else we can try? :D