Skip to content

Enabling the FlowFuse NPM Registry with Docker, nginx-proxy, and Let’s Encrypt #295

Closed

Description

@dgatti0213

Current Behavior

Lets encrypt did not provision the NPM Library server with a cert.

Bugs:

  • Verdaccio $authenticated variable was stripped
  • npm registry TLS certificate was not issued

Expected Behavior

I added/modified this to get it to work:

npm-registry-config:
    content: |
      storage: /verdaccio/storage
      web:
        enable: false
      auth:
        ff-auth:
          baseURL: http://forge:3000/
          adminUser: admin
          adminSecret: ${NPM_PASSWORD:-secret}
      packages:
        '@*/*':
            
          **#Modified**
          access: $$authenticated
        log: { type: stdout, format: pretty, level: http }
  npm-registry:
    image: "flowfuse/npm-registry:0.0.1"
    networks:
      - flowforge
    restart: always
    environment:
      - "VIRTUAL_HOST=npm.${DOMAIN:?error}"
      - "VIRTUAL_PORT=4873"
     
      **#Added**
      - "LETSENCRYPT_HOST=npm.${DOMAIN:?error}"

Steps To Reproduce

Spin up the compose file with using the the Lets Encrypt scripts.

Environment

  • FlowFuse version: Latest
  • Platform/OS: Linux / Docker
  • Browser: Chrome

Linked Customers

https://app-eu1.hubspot.com/contacts/26586079/record/0-1/334502

Activity

  1. added theissue type on Mar 11, 2026
  2. added a commit that references this issue on Mar 11, 2026
    9455eda
  3. added and removed
    needs-triageNeeds looking at to decide what to do
    on Mar 11, 2026
  4. added this to the 2.28 milestone on Mar 11, 2026
  5. added a commit that references this issue on Jun 23, 2026
    f40c64c
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions