# Unable to log in after installation

**URL:** <https://community.graylog.org/t/unable-to-log-in-after-installation/702>\
**Category:** Graylog Central (peer support)\
**Created:** [April 5, 2017, 1:39pm UTC](https://community.graylog.org/t/unable-to-log-in-after-installation/702 "2017-04-05T13:39:30Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![jgoods](https://avatars.discourse-cdn.com/v4/letter/j/5fc32e/32.png) [@jgoods](https://community.graylog.org/u/jgoods)\
**Post date:** [April 5, 2017, 1:39pm UTC](https://community.graylog.org/t/unable-to-log-in-after-installation/702/1 "2017-04-05T13:39:30Z")

</div>

I am using Ubuntu 16.04 LTS with Graylog 2.2. I am able to access the login page, but no matter what I set the password to and run it through the command “echo -n password | sha256sum” I cannot log in. I have not been able to find where anyone else has had this issue either. I did go as far as wiping the server clean and starting all over again (it’s a Hyper-v VM), but the exact same issue occurred again. I am not sure what I am doing wrong now. could someone please assist?

---

<div class="post-metadata">

**Author:** ![jochen](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/jochen/32/8_2.png) [@jochen](https://community.graylog.org/u/jochen)\
**Post date:** [April 5, 2017, 1:49pm UTC](https://community.graylog.org/t/unable-to-log-in-after-installation/702/2 "2017-04-05T13:49:47Z")

</div>

Try using the SHA-256 hash of “password” (literally…) for testing:

```auto
root_password_sha2 = 5e884898da28047151d0e56f8dc6292773603d0d6aabbdd62a11ef721d1542d8

```

Also, how exactly did you configure Graylog and which error messages do you see in your web browser when trying to log in?

---

<div class="post-metadata">

**Author:** ![jgoods](https://avatars.discourse-cdn.com/v4/letter/j/5fc32e/32.png) [@jgoods](https://community.graylog.org/u/jgoods)\
**Post date:** [April 5, 2017, 2:06pm UTC](https://community.graylog.org/t/unable-to-log-in-after-installation/702/3 "2017-04-05T14:06:16Z")

</div>

I did test it with the password “password” and unfortunately it did not help. The error isn’t actually an error, but just a denied due to bad credentials. The message is “Invalid credentials, please verify them and retry.”

The command that I ran was:  
echo -n password | sha256sum  
and the outcome was:  
5e884898da28047151d0e56f8dc6292773603d0d6aabbdd62a11ef721d1542d8

---

<div class="post-metadata">

**Author:** ![jochen](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/jochen/32/8_2.png) [@jochen](https://community.graylog.org/u/jochen)\
**Post date:** [April 5, 2017, 2:12pm UTC](https://community.graylog.org/t/unable-to-log-in-after-installation/702/4 "2017-04-05T14:12:53Z")

</div>

Using the hash for “password” (`5e884898da28047151d0e56f8dc6292773603d0d6aabbdd62a11ef721d1542d8`), how does your Graylog configuration file look like?

---

<div class="post-metadata">

**Author:** ![jgoods](https://avatars.discourse-cdn.com/v4/letter/j/5fc32e/32.png) [@jgoods](https://community.graylog.org/u/jgoods)\
**Post date:** [April 5, 2017, 3:03pm UTC](https://community.graylog.org/t/unable-to-log-in-after-installation/702/5 "2017-04-05T15:03:08Z")

</div>

It is going to be a few minutes because somehow I just accidentally cleared the server.config file while attempting to output it to screen so that I could copy and paste it here.

---

<div class="post-metadata">

**Author:** ![tadeuuuuu](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/tadeuuuuu/32/246_2.png) [@tadeuuuuu](https://community.graylog.org/u/tadeuuuuu)\
**Post date:** [April 5, 2017, 5:33pm UTC](https://community.graylog.org/t/unable-to-log-in-after-installation/702/6 "2017-04-05T17:33:32Z")

</div>

Hello guys, i’m facing this same problem =/

---

<div class="post-metadata">

**Author:** ![jgoods](https://avatars.discourse-cdn.com/v4/letter/j/5fc32e/32.png) [@jgoods](https://community.graylog.org/u/jgoods)\
**Post date:** [April 5, 2017, 5:35pm UTC](https://community.graylog.org/t/unable-to-log-in-after-installation/702/7 "2017-04-05T17:35:14Z")

</div>

I wiped out the server and set it back up with no issue logging in now. Sorry, I do not have a solution other than that.

---

<div class="post-metadata">

**Author:** ![tadeuuuuu](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/tadeuuuuu/32/246_2.png) [@tadeuuuuu](https://community.graylog.org/u/tadeuuuuu)\
**Post date:** [April 5, 2017, 5:39pm UTC](https://community.graylog.org/t/unable-to-log-in-after-installation/702/8 "2017-04-05T17:39:22Z")

</div>

This is my /etc/graylog/server/server.conf

```auto
is_master = true
node_id_file = /etc/graylog/server/node-id
password_secret = Bltp23N2H6xNwUaG0guc35zMeKuqosuyEB3wT6UYM0RTKtal6CafG7ToKxKfIZGQK6E3ham2XckrunC8QaC1JKoXbJSc0ko8
root_username = admin
root_password_sha2 = 6b3a55e0261b0304143f805a24924d0c1c44524821305f31d9277843b8a10f4e
plugin_dir = /usr/share/graylog-server/plugin
rest_listen_uri = http://192.168.0.104:12900/api/
web_listen_uri = http://192.168.0.104:9000/
rotation_strategy = count
elasticsearch_max_docs_per_index = 20000000
elasticsearch_max_number_of_indices = 20
retention_strategy = delete
elasticsearch_shards = 4
elasticsearch_replicas = 0
elasticsearch_index_prefix = graylog
allow_leading_wildcard_searches = false
allow_highlighting = false
elasticsearch_analyzer = standard
output_batch_size = 500
output_flush_interval = 1
output_fault_count_threshold = 5
output_fault_penalty_seconds = 30
processbuffer_processors = 5
outputbuffer_processors = 3
processor_wait_strategy = blocking
ring_size = 65536
inputbuffer_ring_size = 65536
inputbuffer_processors = 2
inputbuffer_wait_strategy = blocking
message_journal_enabled = true
message_journal_dir = /var/lib/graylog-server/journal
lb_recognition_period_seconds = 3
mongodb_uri = mongodb://localhost/graylog
mongodb_max_connections = 1000
mongodb_threads_allowed_to_block_multiplier = 5
content_packs_dir = /usr/share/graylog-server/contentpacks
content_packs_auto_load = grok-patterns.json
proxied_requests_thread_pool_size = 32

```

Any help will be appreciate!

Thanks!

---

<div class="post-metadata">

**Author:** ![KO1984](https://avatars.discourse-cdn.com/v4/letter/k/71e660/32.png) [@KO1984](https://community.graylog.org/u/KO1984)\
**Post date:** [April 5, 2017, 11:02pm UTC](https://community.graylog.org/t/unable-to-log-in-after-installation/702/9 "2017-04-05T23:02:56Z")

</div>

Your password secret is incorrect. The secret isn’t supposed to be a sha256 hash, it’s supposed to be in the form of command options.

> password\_secret  
> You must set a secret that is used for password encryption and salting here. The server will refuse to start if it’s not set. Generate a secret with for example pwgen -N 1 -s 96. If you run multiple graylog-server nodes, make sure you use the same password\_secret for all of them!

[http://docs.graylog.org/en/2.2/pages/installation/manual\_setup.html](http://docs.graylog.org/en/2.2/pages/installation/manual_setup.html)

---

<div class="post-metadata">

**Author:** ![jochen](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/jochen/32/8_2.png) [@jochen](https://community.graylog.org/u/jochen)\
**Post date:** [April 6, 2017, 7:50am UTC](https://community.graylog.org/t/unable-to-log-in-after-installation/702/10 "2017-04-06T07:50:30Z")

</div>

> [@KO1984](#):
>
> Your password secret is incorrect.

No, it’s okay. The `password_secret` setting can really be any random string with at least 16 characters.

---

<div class="post-metadata">

**Author:** ![jochen](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/jochen/32/8_2.png) [@jochen](https://community.graylog.org/u/jochen)\
**Post date:** [April 6, 2017, 7:56am UTC](https://community.graylog.org/t/unable-to-log-in-after-installation/702/11 "2017-04-06T07:56:25Z")

</div>

> [@tadeuuuuu](#):
>
> Hello guys, i’m facing this same problem =/

Please open a new topic and post your Graylog configuration, the logs of your Graylog node, and a detailed description of the error message(s) you see in your browser.
