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
Website does not load #351
Comments
Ok, an update. I have changed the UI compose with:
Now I have more info about this. I think it is related with the user auth.
My registry uses username and passowrd. If I go to "myregistry.com/v2/_catalog?n=1000" chrome asks me for user and password, I type them and I can see the catalog. But the registry-fe does not ask for username and password. So I assume there is the problem. How can I fix it? |
Hi, thank you for using my project and submitting issues. You are miss-configuring the Docker Registry UI, please refer the documentation: https://github.com/Joxit/docker-registry-ui?tab=readme-ov-file#available-options
|
Hello, Thanks for the answer, I have done the changes and now I have another error: An error occured: Check your connection and your registry must have I have added it:
But it is still failing with the same error... |
If you are using |
Hello,
First, thanks for this image, this is a tool that I would like to use but I have some problems with it...
This is my docker compose file:
Also, I have a reverse proxy with nginx with a site named myregistry.com and it redirects all from this name to 10.0.0.5:5000 (I wanted to use SSL)
The registry works fine, I can do the 'docker login' and do the push and pulls. But the registry-ui does not work. I can use it with http://myregistry-fe.com (it's behind reverse proxy too), the web site loads for some minutes and then a popup appears with:
<!DOCTYPE html> <html> <head> <title>Error</title> <style> html { color-scheme: light dark; } body { width: 35em; margin: 0 auto; font-family: Tahoma, Verdana, Arial, sans-serif; } </style> </head> <body> <h1>An error occurred.</h1> <p>Sorry, the page you are looking for is currently unavailable.<br/> Please try again later.</p> <p>If you are the system administrator of this resource then you should check the error log for details.</p> <p><em>Faithfully yours, nginx.</em></p> </body> </html>
Could you please help me with this?
The text was updated successfully, but these errors were encountered: