SSL - Certificate is invalid when opening the browser and the connection not working

[WangJiaoJo]

Hi, Verdaccio team,

I have followed the instructions on this page to generate the certificates,

and when running Verdaccio, it is running on https://0.0.0.0:4873 but with warning.
warn --- http address - https://0.0.0.0:4873/ - verdaccio/5.25.0

And when visit this URL on browser, the page is like this and it cannot be connected only after clicking the 'Proceed to 0.0.0.0(unsafe)'.

May I ask if there is any solution about this issue? Thanks in advance.

[juanpicado]

I frankly prefer using Docker example for https rather use this feature but I haven't tried since years so dunno so far.

[WangJiaoJo]

Hi, Juanpicado,
Thanks for your reply!
Is this an example that I can refer to for using htttps?
https://github.com/verdaccio/verdaccio/blob/master/docker-examples/v4/https-portal-example/docker-compose.yml

Or could you please share the links if you have other examples that I can refer to?
I would really appreciae your help! Thanks!

[juanpicado]

Yeah that one, is a bit outdated but would work also on v5, also there are nginx examples you can also setup HTTPS at proxy level is the best way so far

[WangJiaoJo]

Thanks, Juanpicado, it is really helpful.

[WangJiaoJo]

@juanpicado Hi, I have a problem here, when I follow this example https://github.com/verdaccio/verdaccio/blob/master/docker-examples/v4/https-portal-example/docker-compose.yml, I get the error
cannot open config file /verdaccio/conf/config.yaml: false
Here is my docker compose yml,
services:
xxxxxx1:
image: appkit:latest
restart: always
verdaccio:
depends_on:
- xxxxxx1
image: verdaccio:1.0.0
container_name: xxxxxxxxx
ports:
- "4873:4873"
restart: always
volumes:
- "./storage:/verdaccio/storage"
- "./conf:/verdaccio/conf"
https-portal:
image: steveltn/https-portal:1
ports:
- '80:80'
- '443:443'
links:
- verdaccio:verdaccio
environment:
DOMAINS: 'example.com -> http://verdaccio:4873'
STAGE: local
FORCE_RENEW: 'true'

Is there any wrong with the configuration or solution to resolve this error?
'there are nginx examples you can also setup HTTPS at proxy level'
And is it possible to share the example link or guidance of the nginx examples mentioned above?

Thanks in advance!

[juanpicado]

File permissions probably try chmod 777 to figure it out

[WangJiaoJo]

You mean use chips 777 to allow the permission to /verdaccio/conf files, right?
And any nginx examples that I can refer to?
Thanks!