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
  • #4209

Closed
Open
Created Jun 05, 2013 by Administrator@rootOwner

User Creation API Not Found

Created by: bassrock

  1. Summary:

When Posting to /v3/users I get a 404 Not Found Error.

  1. Steps to reproduce:

On Gitlab 5.2 try posting a request to /v3/users with any request body. The one I used is:

{"twitter":"","projects_limit":10000,"name":"test","password":"test","email":"[email protected]","linkedin":"","skype":"","username":"test"}

  1. Expected behavior:

When not passing a token or if I am passing a token I expect to get back a new user reposnse object or an unauthorized response.

  1. Observed behavior

Instead I receive a response like: {"message":"404 Not Found"}

  1. Output of checks
Checking Environment ...

Git configured for git user? ... yes
Has python2? ... yes
python2 is supported version? ... yes

Checking Environment ... Finished

Checking GitLab Shell ...

GitLab Shell version >= 1.4.0 ? ... OK (1.4.0)
Repo base directory exists? ... yes
Repo base directory is a symlink? ... no
Repo base owned by git:git? ... yes
Repo base access is drwxrws---? ... yes
post-receive hook up-to-date? ... yes
post-receive hooks in repos are links: ... 

Checking GitLab Shell ... Finished

Checking Sidekiq ...

Running? ... yes

Checking Sidekiq ... Finished

Checking GitLab ...

Database config exists? ... yes
Database is SQLite ... no
All migrations up? ... yes
GitLab config exists? ... yes
GitLab config outdated? ... no
Log directory writable? ... yes
Tmp directory writable? ... yes
Init script exists? ... yes
Init script up-to-date? ... yes
Projects have satellites? ... 
Redis version >= 2.0.0? ... yes
Your git bin path is "/usr/local/bin/git"
Git version >= 1.7.10 ? ... yes (1.8.2)

Checking GitLab ... Finished
* Version of GitLab you are running; 5.2
* Add the last commit sha1: 6654db2
* Describe your setup:
System information
System:     Ubuntu 12.04
Current User:   git
Using RVM:  no
Ruby Version:   1.9.3p194
Gem Version:    1.8.23
Bundler Version:1.3.1
Rake Version:   10.0.4

GitLab information
Version:    5.2.0
Revision:   6654db2
Directory:  /home/git/gitlab
DB Adapter: mysql2
URL:        http://****.com
HTTP Clone URL: http://***/some-project.git
SSH Clone URL:  git@****:some-project.git
Using LDAP: no
Using Omniauth: no

GitLab Shell
Version:    1.4.0
Repositories:   /home/git/repositories/
Hooks:      /home/git/gitlab-shell/hooks/
Git:        /usr/local/bin/git
Assignee
Assign to
Time tracking