Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #4928

Closed
Open
Created 11 years ago by Administrator@rootOwner
  • New issue

  • Report abuse

  • New issue

  • Report abuse

SSH Port changed but cached somewhere

Closed

SSH Port changed but cached somewhere

Created by: alessandroorru

I configured my ssh port to 12205 recently, and it appeared correctly on all gitlab pages. Then I changed it to 22005. Now when I reload the repository page (where I see its address) sometimes I see 12205, sometimes I see 22005. The strange thing is that this happens also on newly created project on repository address and repository setup instructions, so I think that there is a worker thread that has cached the port, but I can't find a way to reset it.

I'm using Gitlab 6.0 with unicorn

Linked issues
...

    Related merge requests

    • Administrator
      Administrator @root · 11 years ago
      Owner

      Created by: bertjwregeer

      This may sound obvious, but have you tried stopping unicorn entirely and re-starting it?

      By Administrator on 2013-08-29T15:01:54 (imported from GitLab project)

    • Administrator
      Administrator @root · 11 years ago
      Owner

      Created by: alessandroorru

      I didn't notice that unicorn process was still alive after stopping both nginx and gitlab. I killed it with -QUIT signal and restarted and now it works fine, thank you.

      Anyway I think that this should be managed a lot better. It's a gitlab.conf setting, so it should be managed somehow by restarting gitlab with init script (i'm using ubuntu 12.04 server).

      By Administrator on 2013-08-29T15:21:15 (imported from GitLab project)

    • Administrator
      Administrator @root · 11 years ago
      Owner

      Created by: Razer6

      @alessandroorru Can you reproduce this bahavior with restarting it again? There is a port configuration in `gitlab.conf``

      By Administrator on 2013-09-01T18:15:42 (imported from GitLab project)

    • Administrator
      Administrator @root · 11 years ago
      Owner

      Created by: Razer6

      It's been at least 2 weeks (and a new release) since we heard from you. I'm closing this issue but if you still experience this problem, please open a new issue (but also reference the old issue(s)). Make sure to also include the necessary debugging information conforming to the issue tracker guidelines found in our contributing guidelines.

      By Administrator on 2013-10-13T11:25:16 (imported from GitLab project)

    • You're only seeing other activity in the feed. To add a comment, switch to one of the following options.
    Please register or sign in to reply
    0 Assignees
    Assign to
    Milestone
    No milestone
    None
    None
    Time tracking
    Due date
    None
    None
    1
    Labels
    Awaiting feedback
    Assign labels
    • No matching results
    • Manage project labels
    Confidentiality
    Not confidential

    You are going to turn on confidentiality. Only team members with at least Reporter access will be able to see and leave comments on the issue.

    Lock issue
    Unlocked
    participants
    Reference: