starred/docker-registry-ui-jc21
1
0
Fork 0
mirror of https://github.com/jc21/docker-registry-ui.git synced 2026-04-25 09:15:54 +03:00
Code Issues 20 Projects Releases 3 Packages Wiki Activity

[GH-ISSUE #1] Error connecting to registry over HTTP #1

New issue
Closed
opened 2026-02-27 07:15:08 +03:00 by kerem · 2 comments
kerem commented 2026-02-27 07:15:08 +03:00
Owner
Copy link

Originally created by @msnelling on GitHub (Apr 17, 2018).
Original GitHub issue: https://github.com/jc21/docker-registry-ui/issues/1

I'm running this UI in Kubernetes 1.10 connecting to our private registry in the same cluster and getting the below error.

WARNING: NODE_ENV value of 'production' did not match any deployment config file names.
WARNING: See https://github.com/lorenwest/node-config/wiki/Strict-Mode
2018-04-17T09:57:13.375Z - info: PID 6 listening on port 80 ...
2018-04-17T09:57:13.379Z - info: Registry Host: image-registry:5000
warn: Error: write EPROTO 139648476564296:error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol:../deps/openssl/openssl/ssl/s23_clnt.c:825:
     at _errnoException (util.js:1031:13)
    at WriteWrap.afterWrite [as oncomplete] (net.js:873:14)
warn: Error: write EPROTO 139648476564296:error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol:../deps/openssl/openssl/ssl/s23_clnt.c:825:
     at _errnoException (util.js:1031:13)
    at WriteWrap.afterWrite [as oncomplete] (net.js:873:14)

Our private registry is running with HTTP and I have successfully used this project to connect as a UI without issue https://github.com/snagles/docker-registry-manager

Below are the environment variables I'm using (excuse the Kubernetes syntax).

            containers:
            - name: image-registry-ui
              image: jc21/registry-ui
              env:
              - name: REGISTRY_HOST
                value: image-registry:5000
              - name: REGISTRY_SSL
                value: "false"
              - name: REGISTRY_STORAGE_DELETE_ENABLED
                value: "true"
              - name: REGISTRY_DOMAIN
                value: registry.example.com
              ports:
              - containerPort: 80
                name: http
                protocol: TCP
Originally created by @msnelling on GitHub (Apr 17, 2018). Original GitHub issue: https://github.com/jc21/docker-registry-ui/issues/1 I'm running this UI in Kubernetes 1.10 connecting to our private registry in the same cluster and getting the below error. ``` WARNING: NODE_ENV value of 'production' did not match any deployment config file names. WARNING: See https://github.com/lorenwest/node-config/wiki/Strict-Mode 2018-04-17T09:57:13.375Z - info: PID 6 listening on port 80 ... 2018-04-17T09:57:13.379Z - info: Registry Host: image-registry:5000 warn: Error: write EPROTO 139648476564296:error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol:../deps/openssl/openssl/ssl/s23_clnt.c:825: at _errnoException (util.js:1031:13) at WriteWrap.afterWrite [as oncomplete] (net.js:873:14) warn: Error: write EPROTO 139648476564296:error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol:../deps/openssl/openssl/ssl/s23_clnt.c:825: at _errnoException (util.js:1031:13) at WriteWrap.afterWrite [as oncomplete] (net.js:873:14) ``` Our private registry is running with HTTP and I have successfully used this project to connect as a UI without issue https://github.com/snagles/docker-registry-manager Below are the environment variables I'm using (excuse the Kubernetes syntax). ```yaml containers: - name: image-registry-ui image: jc21/registry-ui env: - name: REGISTRY_HOST value: image-registry:5000 - name: REGISTRY_SSL value: "false" - name: REGISTRY_STORAGE_DELETE_ENABLED value: "true" - name: REGISTRY_DOMAIN value: registry.example.com ports: - containerPort: 80 name: http protocol: TCP ```
kerem closed this issue 2026-02-27 07:15:08 +03:00
kerem commented 2026-02-27 07:15:09 +03:00
Author
Owner
Copy link

@msnelling commented on GitHub (Apr 17, 2018):

Ok, I solved this myself. The problem is with specifying the REGISTRY_SSL=false environment variable, the code is actually just checking whether the variable is set or not (which I have to say isn't particularly intuitive since the docs say to specify true to use SSL so it's not unreasonable to expect false to not use SSL).

<!-- gh-comment-id:381950714 --> @msnelling commented on GitHub (Apr 17, 2018): Ok, I solved this myself. The problem is with specifying the `REGISTRY_SSL=false` environment variable, the code is actually just checking whether the variable is set or not (which I have to say isn't particularly intuitive since the docs say to specify `true` to use SSL so it's not unreasonable to expect `false` to not use SSL).
kerem commented 2026-02-27 07:15:09 +03:00
Author
Owner
Copy link

@jc21 commented on GitHub (Apr 17, 2018):

Yeah I was just mirroring the variable and it's use from the official docker registry. I probably should check the string value..

<!-- gh-comment-id:382176361 --> @jc21 commented on GitHub (Apr 17, 2018): Yeah I was just mirroring the variable and it's use from the official docker registry. I probably should check the string value..
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
develop
2.0.1
2.0.0
1.0.0
Labels
Clear labels   
pull-request

Mirrored from GitHub Pull Request

No labels
pull-request
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/docker-registry-ui-jc21#1
No description provided.