Jones Magloire

Hi, I made a new release if you want to try it v2.5.3

Did you set `REGISTRY_HTTP_HEADERS_Access-Control-Allow-Credentials` to your docker registry server environment configuration as suggested in my [recommended-docker-registry-usage](https://github.com/Joxit/docker-registry-ui#recommended-docker-registry-usage)?

Hi, thank you for using my project ! Are you hosting the ui or are you using the [demo ui](https://joxit.dev/docker-registry-ui/demo/) ? If you are using the demo UI, my domain...

Hi there, since you are using nginx in front of my UI, you do not need `NGINX_PROXY_PASS_URL` and the `REGISTRY_URL` should be your nginx address with `https` on port `443`...

Hi, thank you for using my project :smile: I need more details about your issue :slightly_smiling_face:

I checked your screenshot, please next time fufill correctly a bug report as [defined here](https://github.com/Joxit/docker-registry-ui/issues/new?assignees=&labels=&template=bug_report.md&title=) So there are no longer an option named `URL` in docker-registry-ui since v2, you may...

Hi, your error says > has been blocked by CORS policy: Request header field accept is not allowed by `Access-Control-Allow-Headers` in preflight response. The configuration for `Access-Control-Allow-Headers` is missing from...

Hello, thank you for using my project. I need more details such as the browser console + network tab

Hi @colindawson, your issue is simple, you just need to read the [FAQ](https://github.com/Joxit/docker-registry-ui#faq) and all the linked issues...: > - Why OPTIONS (aka preflight requests) and DELETE fails with 401...

Yeah, but this is exactly what I saw in your screenshot: "preflight request" and "401 status code". Both of them are in the FAQ. The FAQ gives you three ways...