As I understand, during certificate creation you point name of server, which can be verified using this certificate,
Not user, name, but server name:
DEBUG Connected to gRPC server Address=localhost:1900
FATAL Could not start client for gRPC proxy error=x509: certificate is valid for conf-discovery, not localhost
I think you need include the same server name in the certificate, as you set as server-address in discovery configuration.
I’m not using the docker container. I’m trying to start ttn backbone under windows, building it from github source code.
After doing so, starting up the server, I still get the error x509. In my case I am using docker, maybe it is related to the fact that the docker has to know the certificate that I am using as well ( which I have tried as well wihtouth success)
I think you can try opposite solution:
remove “server-address” line from conf file. Assuming localhost for server.
And generate cet using:
$ ttn discovery gen-cert localhost --config ./discovery/ttn.yml
Also note, that there are typo in line
master-aut-servers:
Need to be corrected to
master-auth-servers:
Also note, that during cert generation you use config in ./discovery folder while your key folder is .env/discovery.
I am running a private TTN backend, I have a gateway that was registered on www.console.thethingsnetwork.org/gateways/eui-0000024b080e100b. I can’t get the gateway status, when I use ttnctl (ttnctl gateways status eui-0000024b080e100b or 0000024b080e100b), output error “can not find GatewayID”. Cuold I get those access auth-tokens with the command ttnctl components token for router, broker ? and set server-address-announce to a public IP, how to registe gateways to both my private and public TTN back_end?
Ok so I have got everything set up and it is almost all working - but I’m not able to see packets being sent from my device to the app.
I am running ttnctl subscribe - and I can see a successful join:
> INFO Connecting to MQTT… MQTT Broker=tcp://localhost:1883 Username=
> INFO Connected to MQTT
> INFO Subscribed to activations
> INFO Subscribed to uplink
> INFO Activation
> AppID: priv-test
> DevID: priv_pi
> AppEUI: 70B3D57EF00043A4
> DevEUI: 00333E8BE219B599
> DevAddr: 26000769
…so I thought I was ready to party, but unfortunately I don’t see any subsequent packets coming through - ttnctl subscribe stays silent.
I’m trying to setup a private routing server on my Debian 8 VM.
I’m following your post. But i strand at the same point as Vitalypru mentioned on dec 1st. 2016.
So i took de /develop/ download. And i still run in to it.
Still trying to figure out why my private backend isn’t quite working. ttnctl subscribe shows activations, but doesn’t show messages from my device.
I can see the message appearing on lora-gateway-bridge:
INFO[1035] gateway: rxpk packet received addr=192.168.1.50:33693 data=“QDQsASaAAAABa4mwRxqg26nIsaliN2ALza2hL2AabxKI6bjBIw==” mac=008000000000a052
but all the other services don’t seem to show anything, whereas they all display stuff during the activation.
I noticed the network server showed it was using the public ttn as the Discovery Server, so I have added discovery address: "localhost:1900 to its ttn.yml - so it now points to the local discovery server but that hasn’t made any difference:
> INFO Initializing The Things Network Auth Servers=map[ttn-account-v2:https://account.thethingsnetwork.org] ComponentID=mynetwork-networkserver Description= Discovery Server Address=localhost:1900 Monitors=map
> INFO Initializing Network Server Database=localhost:6379/0 NetID=19 Server=0.0.0.0:1903
> INFO Starting
> INFO Using DevAddr prefix 26000000/20 (otaa,abp,world,local,private,testing)
> INFO ttn: Got public keys for token validation
The deafening silence from the forum forced me to start again.
This time it worked, but I can’t say with certainty what the cause of the problem was. I think I probably screwed up the various security keys somewhere - it is fiddly and looks easy to mess up. There is now uplink activity in the handler as well as the bridge logs, and the uplink message appears in ttnctl subscribe.
Hellol. I’ve set up my private TTN backned instance following this article [https://www.thethingsnetwork.org/article/setting-up-a-private-routing-environment]. Everything seems to work right. All components seems to work. Using ttnclt i can register a device, create an app and simulate an upload message that is published in its corresponding MQTT path. BUT when I try with a real deployment (a Kerlink GW and a SoluM LoRa mote, Gateway seems to work, JOIN requests from the mote are accepted but when I try to send data from the mote to the MQTT server, nothing appears. The router debug prints: NO BROKERS TO FORWARD MESSAGE TO
Here is the the Debug line printed by the router:
e[90m DEBUGe[0m No brokers to forward message to e[90mAppPayloadSizee[0m=16 e[90mCodingRatee[0m=4/5 e[90mCountere[0m=1 e[90mDataRatee[0m=SF12BW125 e[90mDevAddre[0m=26000F60 e[90mDownlinkOptionse[0m=2 e[90mFCnte[0m=1 e[90mFrequencye[0m=867300000 e[90mGatewayIDe[0m=eui-0000024b080306b5 e[90mModulatione[0m=LORA e[90mPayloadSizee[0m=29 e[90mPorte[0m=2 e[90mRSSIe[0m=-25 e[90mSNRe[0m=9
HI,
I have also installed my private TTN backend following https://www.thethingsnetwork.org/article/setting-up-a-private-routing-environment.
I will rely on The Things Network community account server (account.thethingsnetwork.org) so I can use my TTN account to manage the devices on my local network.
Locally everything seems to work right, but on the console of The Things Network I can only view the application and not the devices locally registered.
Suggestions?
I have just set up a private routing environment following Hylke’s guide from https://www.thethingsnetwork.org/article/setting-up-a-private-routing-environment. (the non-docker version)
I have started all components and tried to register a gateway to my local environment. Although the ttnctl config file seems to point to localhost, the gateway is registered to the TTN web console environment. I have also tried to bypass the config file by configuring the various components using the command arguments. If I have understood correctly, a gateway could be registered to the public TTN or the private exclusively.
Am I missing something?
When I start the local discovery server I get the following:
./ttn-linux-amd64 discovery --config ./discovery/ttn.yml
Using config file: ./discovery/ttn.yml
INFO Initializing The Things Network Auth Servers=map[ttn-account-v2:https://account.thethingsnetwork.org local:file://discovery/server.pub] ComponentID=mynetwork-discovery Description= Discovery Server Address:1900=discover.thethingsnetwork.org Monitors=map
INFO Initializing Discovery Database=localhost:6379/0 HTTP Proxy=0.0.0.0:8080 Server=0.0.0.0:1900
INFO Starting
INFO ttn: Got public keys for token validation
I am suspecting there is an issue with the discovery server address setting there.
I configured my local private environment. I can connect to the handler by MQTT and receive uplink message and send downlink message. This works fine! But, there is something I do not understand regarding the rest API of my private handler. How can I use them to get the app list with an HTTP Get request? What should I specify in the request header as an Authorization?
I tried using it too nodejs sdk to perform an HTTP request with ttn.manager.HTTP(options) but the request failed.
Can someone help me?
Do you have minimal requirement for a setup with less than 100 nodes ? I saw that you provide ARM blobs.
I am thinking off small private network where there is no internet connection is available, maybe on a NXP i.MX6 board
( which I have tried as well wihtouth success)