Download packages error

[dpetiz]

Hello people
I'm trying to install a package but it always return me error.

npm install weex-styler@0.3.0

Aug 21 10:21:31 verdaccio docker-compose[2558621]: verdaccio    | info --- auth/allow_action: access granted to: luis.correia
Aug 21 10:21:31 verdaccio docker-compose[2558621]: verdaccio    | info --- allowed access for weex-styler
Aug 21 10:21:31 verdaccio docker-compose[2558621]: verdaccio    | http <-- 200, user: luis.correia(37.27.47.71 via 192.168.160.1), req: 'GET /weex-styler', bytes: 0/0
Aug 21 10:21:31 verdaccio docker-compose[2558621]: verdaccio    | http <-- 200, user: luis.correia(37.27.47.71 via 192.168.160.1), req: 'GET /weex-styler', bytes: 0/2672
Aug 21 10:21:31 verdaccio docker-compose[2558621]: verdaccio    | info <-- 192.168.160.1 requested 'POST /-/npm/v1/security/advisories/bulk'
Aug 21 10:21:31 verdaccio docker-compose[2558621]: verdaccio    | http <-- 200, user: null(37.27.47.71 via 192.168.160.1), req: 'POST /-/npm/v1/security/advisories/bulk', bytes: 150/0
Aug 21 10:21:31 verdaccio docker-compose[2558621]: verdaccio    | info <-- 192.168.160.1 requested 'GET /weex-styler/-/weex-styler-0.3.0.tgz'
Aug 21 10:21:31 verdaccio docker-compose[2558621]: verdaccio    | info --- auth/allow_action: access granted to: luis.correia
Aug 21 10:21:31 verdaccio docker-compose[2558621]: verdaccio    | info --- allowed access for weex-styler
Aug 21 10:21:31 verdaccio docker-compose[2558621]: verdaccio    | http <-- 200, user: luis.correia(37.27.47.71 via 192.168.160.1), req: 'GET /weex-styler/-/weex-styler-0.3.0.tgz', bytes: 0/0
Aug 21 10:21:31 verdaccio docker-compose[2558621]: verdaccio    | info --- making request: 'GET http://registry.npmjs.org/weex-styler/-/weex-styler-0.3.0.tgz'
Aug 21 10:21:31 verdaccio docker-compose[2558621]: verdaccio    | http <-- 200, user: null(37.27.47.71 via 192.168.160.1), req: 'POST /-/npm/v1/security/advisories/bulk', bytes: 150/2
Aug 21 10:21:31 verdaccio docker-compose[2558621]: verdaccio    | error--- unexpected error: Protocol "https:" not supported. Expected "http:"
Aug 21 10:21:31 verdaccio docker-compose[2558621]: verdaccio    | TypeError [ERR_INVALID_PROTOCOL]: Protocol "https:" not supported. Expected "http:"
Aug 21 10:21:31 verdaccio docker-compose[2558621]: verdaccio    |     at new ClientRequest (node:_http_client:183:11)
Aug 21 10:21:31 verdaccio docker-compose[2558621]: verdaccio    |     at Object.request (node:https:379:10)
Aug 21 10:21:31 verdaccio docker-compose[2558621]: verdaccio    |     at Request.start (/usr/local/lib/node_modules/verdaccio/node_modules/@cypress/request/request.js:743:32)
Aug 21 10:21:31 verdaccio docker-compose[2558621]: verdaccio    |     at Request.end (/usr/local/lib/node_modules/verdaccio/node_modules/@cypress/request/request.js:1500:10)
Aug 21 10:21:31 verdaccio docker-compose[2558621]: verdaccio    |     at end (/usr/local/lib/node_modules/verdaccio/node_modules/@cypress/request/request.js:556:14)
Aug 21 10:21:31 verdaccio docker-compose[2558621]: verdaccio    |     at Immediate._onImmediate (/usr/local/lib/node_modules/verdaccio/node_modules/@cypress/request/request.js:570:7)
Aug 21 10:21:31 verdaccio docker-compose[2558621]: verdaccio    |     at process.processImmediate (node:internal/timers:478:21)
Aug 21 10:21:31 verdaccio docker-compose[2558621]: verdaccio    | http <-- 500, user: luis.correia(37.27.47.71 via 192.168.160.1), req: 'GET /weex-styler/-/weex-styler-0.3.0.tgz', error: internal server error

My verdaccio config:

storage: /verdaccio/storage
plugins: /verdaccio/plugins

web:
  enable: true
  title: Example NPM Registry
  logo: https://media.example.com/images/logo.png

url_prefix: '/'
max_body_size: 50mb

auth:
  htpasswd:
    file: /verdaccio/conf/htpasswd
    # Maximum amount of users allowed to register, defaults to "+inf".
    # You can set this to -1 to disable registration.
    max_users: -1
    # Hash algorithm, possible options are: "bcrypt", "md5", "sha1", "crypt".
    algorithm: bcrypt # by default is crypt, but is recommended use bcrypt for new installations
    # Rounds number for "bcrypt", will be ignored for other algorithms.
    rounds: 10

# https:
#     key: /etc/ssl/certs/star.example.com.key
#     cert: /etc/ssl/certs/star.example.com.crt
#     ca: /etc/ssl/certs/star.example.com.pem

security:
  api:
    legacy: false
    jwt:
      sign:
        expiresIn: 365d

uplinks:
  npmjs:
    url: https://registry.npmjs.org/
    max_fails: 20
    fail_timeout: 10m

packages:
  'example-webpack-plugin':
    access: $authenticated
    publish: $authenticated
    proxy: npmjs
  'example-*':
    access: $authenticated
    publish: $authenticated
  '**':
    access: $authenticated
    publish: $authenticated
    proxy: npmjs

middlewares:
  audit:
    enabled: true

logs:
  - {type: stdout, format: pretty, level: http}

Could someone help me solving it?
i'm accessing verdaccio behind a nginx

my nginx config

server_tokens off;
ssl_certificate /etc/ssl/star.example.com.crt;
ssl_certificate_key /etc/ssl/star.example.com.key;
client_max_body_size 100M;
tcp_nopush on;
tcp_nodelay on;

map $http_upgrade $connection_upgrade {
  default Upgrade;
  '' close;
}

# Disable nginx default http server
server {
  server_name _;
  listen 80 default_server;
  return 444;
}

# Disable nginx default https server
server {
  listen 443 ssl;
  server_name _;
  return 444;
}

## Verdaccio
server {
  listen 80;
  server_name beowulf.example.com;


  return 301 https://$server_name$request_uri;
}

server {
  listen 443 ssl http2;
  server_name beowulf.example.com;



  proxy_http_version 1.1;
  proxy_set_header Host $host;
  proxy_set_header X-Forwarded-Proto $scheme;
  proxy_set_header X-Forwarded-Port $server_port;
  proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
  proxy_set_header Upgrade $http_upgrade;
  proxy_set_header Connection $connection_upgrade;

  # This block was added because keycloak 20 header is big so we were getting 502 error after the login
  proxy_buffer_size   256k;
  proxy_buffers   4 512k;
  proxy_busy_buffers_size   512k;

  client_body_buffer_size 256K;

  location / {

        proxy_pass http://127.0.0.1:4873;
      }

  }

[juanpicado]

Protocol "https:" not supported. Expected "http:"

weird, never seen this before, I'll compare with my nginx configuration

[LuisSCorreia]

Having tested this, I can confirm that it solves the issue, as I was able to install multiple versions of that package.
However, what should our next steps be going forward? We can't simply delete all Verdaccio storage as we have hundreds of packages...

[juanpicado]

If you are using a domain, I recommend use https://verdaccio.org/docs/env#public-url VERDACCIO_PUBLIC_URL, this variable will change the url hosted on the storage on the fly, try it out and let me know.

[LuisSCorreia]

Hello @juanpicado, sorry for the delay.
We've tried that out, but we get the same error (Protocol "https:" not supported. Expected "http:").
Also, the GET request that Verdaccio makes to the uplink (registry.npmjs.org) is still targeting a HTTP link. Not sure if this is relevant but I thought it was worth mentioning.

[LuisSCorreia]

Is there any quick way for us to delete from storage the packages that were obtained from the uplink? That would solve the issue, I think

[juanpicado]

Is there any quick way for us to delete from storage the packages that were obtained from the uplink?

you should not do this, I run verdaccio behind nginx for over few years with no issue, so I'm thinking what might be different in your case.