Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

client 'console' not found error when logging in #1226

Closed
swattor opened this issue Aug 22, 2019 · 14 comments
Closed

client 'console' not found error when logging in #1226

swattor opened this issue Aug 22, 2019 · 14 comments
Assignees
Labels
duplicate This issue or pull request already exists

Comments

@swattor
Copy link

swattor commented Aug 22, 2019

Summary

When logging into the web console, the following error is produced:

Not Found
client console not found

The "take me back" button returns you to the /oauth URL indicating that the login successfully completed

...

Steps to Reproduce

  1. Spin up stack
  2. Configure
  3. Attempt to login

ttn_config.txt

What do you see now?

...

What do you want to see instead?

...

Environment

...

How do you propose to implement this?

...

Can you do this yourself and submit a Pull Request?

...

@johanstokking
Copy link
Member

  1. Spin up stack
  2. Configure

Can you elaborate a bit on the second point?

Did you follow the Getting Started, especially the part where you need to create an OAuth client for the Console?

@swattor
Copy link
Author

swattor commented Aug 22, 2019

Ah.

See, the documentation is a bit confusing:

https://github.com/TheThingsNetwork/lorawan-stack/blob/master/doc/gettingstarted.md links to:
https://ttn.fyi/v3/getting-started which links to:
https://github.com/TheThingsNetwork/lorawan-stack/blob/v3.0.4/doc/gettingstarted.md

Which doesn't have the bit about the console.

I've now run the create OAuth client for the console, and now I get 'Internal Server Error'!

@swattor
Copy link
Author

swattor commented Aug 22, 2019

It's worth noting that I'm running this on a seperate machine (so accessing via http://remote-ip/ rather than http://localhost). I'm not sure whether that is relevant.

@swattor
Copy link
Author

swattor commented Aug 22, 2019

Tried various things, including starting again. While following the instructions gets me further, I'm now stuck with an "Internal Server Error" when I login.

@htdvisser
Copy link
Contributor

htdvisser commented Aug 23, 2019

Updated the redirect ttn.fyi/v3/getting-started to point to the latest (3.1.0) getting started guide.

@htdvisser
Copy link
Contributor

@swattor Can you please expand the Steps to Reproduce section with the exact steps you took? Without detailed steps we can't reproduce the issue. The issue template also asks you to upload your configuration, terminal output / logs and screenshots (you can redact sensitive information). Please do that so that we can investigate this further.

@htdvisser htdvisser self-assigned this Aug 23, 2019
@htdvisser
Copy link
Contributor

Seems like you're not the only one running into a 500 error, so marking this as a possible duplicate of #1232.

@htdvisser htdvisser added the duplicate This issue or pull request already exists label Aug 23, 2019
@swattor
Copy link
Author

swattor commented Aug 23, 2019

Yeah, I had tracked it down to something to do with oauth.

Looking at the logs provided in the duplicate, it looks very similar, or at least failing in the same way. I will try and run with debug and provide some useful info in that ticket.

@htdvisser
Copy link
Contributor

Hi @swattor, If you're able to compile and run The Things Stack from source, try it with the code in the Pull Request #1236

@fernandobarreto
Copy link

fernandobarreto commented Sep 6, 2019

Hi @htdvisser , I tried the last release of docker ttn stack (3.1.2) and the "Internal Server Error" still remains at console page. I'm trying to implement a private TTN service in our university for study.

@johanstokking
Copy link
Member

Can you enable debug logs on the server (TTN_LW_LOG_LEVEL=debug in Docker compose environment for the stack container) and copy server logs?

Also, can you as @htdvisser requested before, copy your exact steps and update the original comment in this issue?

@fernandobarreto
Copy link

I find out the problem, it was on certificates.... Thanks anyway.

@johanstokking
Copy link
Member

johanstokking commented Sep 9, 2019

Sure, you're welcome!

If there's anything to clarify in our documentation, please file an additional issue or pull request.

@GMouaad
Copy link

GMouaad commented Jan 17, 2020

I find out the problem, it was on certificates.... Thanks anyway.

Any Explanation how you resolved the issue please ?
I'm running the Stack on a VM, so i assumed it has smth to do with the redirects or csrf ??
I get the following response for token request:
{"code":16,"message":"error:pkg/errors/web:unknown (Unauthorized)","details":[{"@type":"type.googleapis.com/ttn.lorawan.v3.ErrorDetails","namespace":"pkg/errors/web","message_format":"Unauthorized","attributes":{"message":"No auth cookie"},"code":16}]}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

5 participants