-
-
Notifications
You must be signed in to change notification settings - Fork 329
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DELETE woes (again) #214
Comments
Hello, Thank you for using my project 😄 To avoid CORS, the registry and the UI must have the same host AND port. |
I am not sure how two processes can listen() on the same port without specifying different IP addresses and without triggering EADDRINUSE. But removing REGISTRY_URL did the trick, thank you! Maybe it would be helpful to point to this issue from the FAQ. |
Hello,
I'm aware of #104 and the FAQ regarding DELETE.
In #207 I read:
So I thought I give it a try.
My registry and registry-ui are on the same host. I have the registry on port 443, the UI on port 8080 and httpd as reverse proxy on port 8443.
The location part in
etc/nginx/conf.d/default.conf
within the running container is enabled, so NGINX_PROXY_PASS_URL seems to have done its thing:Unforunatley I still see an 401 reponse code for OPTIONS in the registry log:
The IP address 172.16.39.68 tells me that the request came from my browser, not from nginx within registry-ui. I would have expected the latter.
Am I missing something?
Regards,
Robert
The text was updated successfully, but these errors were encountered: