[Superdesk Question] Default username and password?
  • Vote Up0Vote Down Nalyk CalmisNalyk Calmis
    Posts: 84Member
    Hello,

    I managed to install Superdesk, but i did not found the default admin username and password to log in into the system. Can anyone help me?
  • 11 Comments sorted by
  • Vote Up1Vote Down Andrey PodshivalovAndrey Podshivalov
    Posts: 1,526Member, Administrator, Sourcefabric Team
    try
    login: User1
    password: a
  • Vote Up1Vote Down Mugur RusMugur Rus
    Posts: 132Member
    Currently we have only the Livedesk plugin implemented. You should see in the menu the following entries: Liveblogs, Media archive, Users. The Media archive entry displays a simple form to upload files. The media archive user interface is not implemented yet.

    Best,
    Mugur
  • Vote Up1Vote Down Yauhen KirylauYauhen Kirylau
    Posts: 104Member
    Hello Bram!
    So you did tried "admin"/"admin" and it was not working, right?
    Can you please check browser console (usually binded to F12) messages and docker-compose output for any exceptions?
    Innovations developer, Sourcefabric
  • Vote Up1Vote Down Yauhen KirylauYauhen Kirylau
    Posts: 104Member
    So did you tried pressing F12 in the browser as i suggested above? After that try to log in again and check if there any messages.
    Innovations developer, Sourcefabric
  • Vote Up0Vote Down Nalyk CalmisNalyk Calmis
    Posts: 84Member
    Thank you, Andrey.

    I'll try it later.
  • Vote Up0Vote Down Nalyk CalmisNalyk Calmis
    Posts: 84Member
    Reply to @Andrey+Podshivalov:

    Andrey, it works, thanks. I wish to know, do i have access only to livedesk component?
  • Vote Up0Vote Down Nalyk CalmisNalyk Calmis
    Posts: 84Member
    Reply to @Mugur+Rus:

    Thank you, @Mugur. It's like you described it in your post, i just wanted to make it clear for me.

    All the best to developers. Doing a great job.
    Post edited by Nalyk Calmis at 2012-11-06 05:05:45
  • Vote Up0Vote Down bram kortlevenbram kortleven
    Posts: 8Member
    I can't seem to get logged into the installed system.
    I started it up after installation with the docker-local-demo.sh script, and ran the docker-local-create-user.sh script as per instruction in the other script files... I even tried changing the docker-local-create-user.sh script to add another user, but still cannot log in to the system.
    Installation on a clean Ubuntu 14.04 x64 system (on VMWare) with 2GB RAM, following the guide in     https://github.com/superdesk/superdesk/blob/master/README.md 
    Is there anyone that installed the system in the same way, and did get to log into it?
    We'd like to start using it, learning to use it, to implement and deploy it in september for a local small student radio station.

    Please advise!
  • Vote Up0Vote Down bram kortlevenbram kortleven
    Posts: 8Member
    Hey Yauhen,

    No idea where/how to do that. I'm using a Mac as my desktop using latest Chrome browser to try to log in.
    The server is running Superdesk is a virtualized (VMWare ESXi) Ubuntu machine, no 'console' available there except ssh.

    Where/how to I get the browser console in Chrome? (or do you recommend another browser you know that has it?)
    The docker-compose output, I guess you mean the script output that keeps running on my screen?: No output, error or info messages when trying to log in, apart from the usual scheduler notifications and wamp messages...

    Recent output below:









    backend_1  | 16:25:20 beat.1 | Scheduler: Sending due task publish:transmit (superdesk.publish.transmit) level=INFO process=MainProcess


    backend_1  | 16:25:23 beat.1 | Scheduler: Sending due task ingest:update (superdesk.io.update_ingest) level=INFO process=MainProcess


    mongodb_1  | 2015-06-13T16:25:26.588+0000 [clientcursormon] mem (MB) res:4 virt:501


    mongodb_1  | 2015-06-13T16:25:26.589+0000 [clientcursormon]  mapped (incl journal view):320


    mongodb_1  | 2015-06-13T16:25:26.594+0000 [clientcursormon]  connections:1


    backend_1  | 16:25:30 beat.1 | Scheduler: Sending due task publish:transmit (superdesk.publish.transmit) level=INFO process=MainProcess


    backend_1  | 16:25:37 wamp.1 | broadcasting "{"data": "ping", "from": "http://127.0.0.1/api"}"


    backend_1  | 16:25:37 wamp.1 | broadcasting "{"data": "ping", "from": "http://127.0.0.1/api"}"


    backend_1  | 16:25:37 wamp.1 | msg sent to 3 client(s)


    backend_1  | 16:25:37 wamp.1 | msg sent to 3 client(s)


    backend_1  | 16:25:40 beat.1 | Scheduler: Sending due task publish:transmit (superdesk.publish.transmit) level=INFO process=MainProcess


    backend_1  | 16:25:50 beat.1 | Scheduler: Sending due task publish:transmit (superdesk.publish.transmit) level=INFO process=MainProcess


    backend_1  | 16:25:53 beat.1 | Scheduler: Sending due task ingest:update (superdesk.io.update_ingest) level=INFO process=MainProcess


    backend_1  | 16:26:00 beat.1 | Scheduler: Sending due task publish:transmit (superdesk.publish.transmit) level=INFO process=MainProcess


    backend_1  | 16:26:07 wamp.1 | broadcasting "{"data": "ping", "from": "http://127.0.0.1/api"}"


    backend_1  | 16:26:07 wamp.1 | broadcasting "{"data": "ping", "from": "http://127.0.0.1/api"}"


    backend_1  | 16:26:07 wamp.1 | msg sent to 3 client(s)


    backend_1  | 16:26:07 wamp.1 | msg sent to 3 client(s)


    backend_1  | 16:26:10 beat.1 | Scheduler: Sending due task publish:transmit (superdesk.publish.transmit) level=INFO process=MainProcess


    backend_1  | 16:26:20 beat.1 | Scheduler: Sending due task publish:transmit (superdesk.publish.transmit) level=INFO process=MainProcess


    backend_1  | 16:26:23 beat.1 | Scheduler: Sending due task ingest:update (superdesk.io.update_ingest) level=INFO process=MainProcess


    backend_1  | 16:26:30 beat.1 | Scheduler: Sending due task publish:transmit (superdesk.publish.transmit) level=INFO process=MainProcess


    backend_1  | 16:26:37 wamp.1 | broadcasting "{"data": "ping", "from": "http://127.0.0.1/api"}"


    backend_1  | 16:26:37 wamp.1 | broadcasting "{"data": "ping", "from": "http://127.0.0.1/api"}"


    backend_1  | 16:26:37 wamp.1 | msg sent to 3 client(s)


    backend_1  | 16:26:37 wamp.1 | msg sent to 3 client(s)


    backend_1  | 16:26:40 beat.1 | Scheduler: Sending due task publish:transmit (superdesk.publish.transmit) level=INFO process=MainProcess


    backend_1  | 16:26:50 beat.1 | Scheduler: Sending due task publish:transmit (superdesk.publish.transmit) level=INFO process=MainProcess



    Thanks for havind a look and trying to guide me!

  • Vote Up0Vote Down bram kortlevenbram kortleven
    Posts: 8Member
    F12 doesn't do a thing in Chrome on OSX... sorry :s

  • Vote Up0Vote Down bram kortlevenbram kortleven
    Posts: 8Member
    I tried in FireFox, and I see a message 'cannot connect to ws://127.0.0.1/ws'

    I looked up where the ws://127.0.0.1/ws was mentioned and adjusted the 127.0.0.1 to the actual internal IP address of the machine in every rule of the docker/docker-compose.yml file.
    It works now!
    I can successfully log in now.

    Thanks so much for pointing me in the right direction!

    Post edited by bram kortleven at 2015-06-13 13:06:04
Add a Comment