Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
duniter
duniter
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 191
    • Issues 191
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 2
    • Merge Requests 2
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards

Mise à jour effectuée, merci de nous signaler tout dysfonctionnement ! | Upgrade done, please let us know about any dysfunction!

  • nodes
  • typescript
  • duniterduniter
  • Issues
  • #1329

Closed
Open
Opened Jan 12, 2019 by Cédric Moreau@c-geekOwner

WS2P sync does not work on nodes with a path in their WS2P endpoint

For example with this endpoint:

WS2P 90e9b12 duniter.g1.1000i100.fr 443 /ws2p

Duniter will try to join wss://duniter.g1.1000i100.fr /ws2p. There is an extra space here which make the connection fail.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
1.10
Milestone
1.10
Assign milestone
Time tracking
None
Due date
None
Reference: nodes/typescript/duniter#1329