I’m setting up the TTN CLI for use with the au1 v3 network cluster. When I run the command ttn-lw-cli login, I get the following response:
INFO Opening your browser on https://au1.cloud.thethings.network/oauth/authorize?client_id=cli&redirect_uri=local-callback&response_type=code
INFO After logging in and authorizing the CLI, we'll get an access token for future commands.
INFO Waiting for your authorization...
The web browser opens to a blank white screen. Inspect element shows the HTML as:
<html> = 0
<head></head>
<body></body>
</html>
If I use enter the same URL, switching au1.cloud.thethings.network for eu1.cloud.thethingnetwork it loads the login screen.
The contents of the .ttn-lw-cli.yml file are:
oauth-server-address: 'https://au1.cloud.thethings.network/oauth'
identity-server-grpc-address: 'au1.cloud.thethings.network:8884'
gateway-server-grpc-address: 'au1.cloud.thethings.network:8884'
network-server-grpc-address: 'au1.cloud.thethings.network:8884'
application-server-grpc-address: 'au1.cloud.thethings.network:8884'
join-server-grpc-address: 'au1.cloud.thethings.network:8884'
device-claiming-server-grpc-address: 'au1.cloud.thethings.network:8884'
device-template-converter-grpc-address: 'au1.cloud.thethings.network:8884'
qr-code-generator-grpc-address: 'au1.cloud.thethings.network:8884'
I’ve chosen to manually create the configuration file.
Any suggestions on how to fix?
1 Like
htdvisser
March 12, 2021, 8:43am
2
The OAuth server is in our eu1 cluster, so changing this to https://eu1.cloud.thethings.network/oauth should work.
CC: @benolayinka for fixing the docs
2 Likes
Thanks mate. Just reading up about the addresses here . Should I change the identity-server-grpc-address to eu1.cloud.thethings.network:8884 as well?
Also, if following the “Generate configuration file steps”, the command ttn-lw-cli use au1.cloud.thethings.network generates the following:
base:
config: []
log:
level: info
credentials-id: au1.cloud.thethings.network
input-format: json
output-format: json
allow-unknown-hosts: false
oauth-server-address: https://au1.cloud.thethings.network/oauth
identity-server-grpc-address: au1.cloud.thethings.network:8884
gateway-server-enabled: true
gateway-server-grpc-address: au1.cloud.thethings.network:8884
network-server-enabled: true
network-server-grpc-address: au1.cloud.thethings.network:8884
application-server-enabled: true
application-server-grpc-address: au1.cloud.thethings.network:8884
join-server-enabled: true
join-server-grpc-address: au1.cloud.thethings.network:8884
device-template-converter-grpc-address: au1.cloud.thethings.network:8884
device-claiming-server-grpc-address: au1.cloud.thethings.network:8884
qr-code-generator-grpc-address: au1.cloud.thethings.network:8884
insecure: false
ca: ""
dump-requests: false
Perhaps make an adjustment to the function to keep the oauth-server-address and identity-server-grpc-address pointing to the eu1 cluster?
Otherwise, add a note suggesting to manually create the configuration file for those not using the eu1 cluster?
system
April 12, 2021, 10:22am
4
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.