Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • J jami-client-gnome
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 88
    • Issues 88
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • savoirfairelinux
  • jami-client-gnome
  • Issues
  • #593

Closed
Open
Created Jan 06, 2017 by RingBot@RingBotOwner

configured bootsrap node always defaults to port 4222

Issue generated from Tuleap's migration script. Originally submitted by: Simon Désaulniers (sim590)

I have found that configuring the port using the GNOME client configuration interface fails to configure a bootstrap address with the appropriate port.

I have tried bootstrapping on a local node (on my machine) using an address obtained from the router with first empty port, then changing the port and saving doesn't take the change into account when looking at the log.

I can confirm that this bug doesn't occur on Windows 32 client.

Assignee
Assign to
Time tracking