The new name is very charisma. Congratulations, good name.
Already the old name was not very cool, it was very standard because it bears the name of technology.
Thank you for improving to this day. Before we met your project, we wrote and used our own servers. When we switched to your software, we jobs accelerated.
We have now received investment from the UK and are structuring. Once completed, we are planning to meet for sponsorship.
Thanks @brocaar for all your hard work on this - LoRaServer.io enabled us to provide our customers with a fully scalable, secure stack via MQTT+TLS when all that was available to us elsewhere was UDP.
I’m really looking forward to helping Chirpstack grow, and to help prove that OpenSource rather than trademark disputes over products that actually improve brand awareness is the way forward for the Internet of Things.
Thanks for all your hard work @brocaar. I have managed to update the Ubuntu packages and everything seems to be working fine, except that the Chirpstack Application Server GUI still uses the old LoRaServer logo.
That might be a caching issue 
Also make sure the process chirpstack-application-server is running on your machine.
Thank you @brocaar, for your valuable contribution and amazing hard work!
We are also trying to update & while upgrading, even we are facing a similar issue. Including the last seen for gateways, the database has also not been updated from loraserver_as to chirpstack_as. How do we manage that?
Thanks again!
Check the package versions that are installed on your system. When you upgraded, from which versions to which versions did you update? Did you check the chirpstack-application-server process as I described above?
the database has also not been updated from loraserver_as to chirpstack_as. How do we manage that?
The update doesn’t rename databases for you, there is no technical need for it 
You still do it yourself if you want.
We upgraded lora-app-server v3.3.0 to v3.5.0 , loraserver v3.2.0 to v3.4.0 & lora-gateway-bridge v3.3.0 to v3.4.0.
Yes, we did check it in journalctl and the services were up and running of the chirpstack-app-server.
But in the logs of chirpstack-network-server, we are finding following errors, probably the reason why we are not getting the device and gateway last seen…
Nov 04 12:45:18 siotel-prod-gj-13 chirpstack-network-server[19126]: time="2019-11-04T12:45:18Z" level=info msg="finished unary call with code OK" ctx_id=601dc9ee-92c8-484e-acf6-e9bc537354cb grpc.code=OK grpc.method=GetGateway grpc.service=ns.NetworkServerService grpc.start_time="2019-11-04T12:45:18Z" grpc.time_ms=1.437 peer.address="10.0.20.11:43404" span.kind=server system=grpc
Nov 04 12:45:22 siotel-prod-gj-13 chirpstack-network-server[19126]: time="2019-11-04T12:45:22Z" level=info msg="gateway/mqtt: uplink frame received" gateway_id=506f980000000777 uplink_id=97cc2c2b-8d03-4a34-af5a-d4b07e35928b
Nov 04 12:45:22 siotel-prod-gj-13 chirpstack-network-server[19126]: time="2019-11-04T12:45:22Z" level=info msg="uplink: frame(s) collected" ctx_id=cd631d58-a9ec-4e36-8045-b346010f573d mtype=ConfirmedDataUp uplink_ids="[97cc2c2b-8d03-4a34-af5a-d4b07e35928b]"
Nov 04 12:45:22 siotel-prod-gj-13 chirpstack-network-server[19126]: time="2019-11-04T12:45:22Z" level=info msg="device gateway rx-info meta-data saved" ctx_id=cd631d58-a9ec-4e36-8045-b346010f573d dev_eui=506f980000000404
Nov 04 12:45:22 siotel-prod-gj-13 chirpstack-network-server[19126]: time="2019-11-04T12:45:22Z" level=info msg="device-session saved" ctx_id=cd631d58-a9ec-4e36-8045-b346010f573d dev_addr=00000404 dev_eui=506f980000000404
Nov 04 12:45:22 siotel-prod-gj-13 chirpstack-network-server[19126]: time="2019-11-04T12:45:22Z" level=info msg="sent uplink meta-data to network-controller" ctx_id=cd631d58-a9ec-4e36-8045-b346010f573d dev_eui=506f980000000404
Nov 04 12:45:22 siotel-prod-gj-13 chirpstack-network-server[19126]: time="2019-11-04T12:45:22Z" level=error msg="finished client unary call" ctx_id=cd631d58-a9ec-4e36-8045-b346010f573d error="rpc error: code = Unimplemented desc = unknown service as.ApplicationServerService" grpc.code=Unimplemented grpc.duration="425.715µs" grpc.method=HandleUplinkData grpc.service=as.ApplicationServerService span.kind=client system=grpc
Nov 04 12:45:22 siotel-prod-gj-13 chirpstack-network-server[19126]: time="2019-11-04T12:45:22Z" level=error msg="publish uplink data to application-server error" ctx_id=cd631d58-a9ec-4e36-8045-b346010f573d error="rpc error: code = Unimplemented desc = unknown service as.ApplicationServerService"
Nov 04 12:45:22 siotel-prod-gj-13 chirpstack-network-server[19126]: time="2019-11-04T12:45:22Z" level=info msg="gateway/mqtt: publishing gateway command" command=down downlink_id=cd631d58-a9ec-4e36-8045-b346010f573d gateway_id=506f980000000777 qos=0 topic=gateway/506f980000000777/command/down
Nov 04 12:45:22 siotel-prod-gj-13 chirpstack-network-server[19126]: time="2019-11-04T12:45:22Z" level=info msg="device-session saved" ctx_id=cd631d58-a9ec-4e36-8045-b346010f573d dev_addr=00000404 dev_eui=506f980000000404
Nov 04 12:45:22 siotel-prod-gj-13 chirpstack-network-server[19126]: time="2019-11-04T12:45:22Z" level=info msg="downlink-frames saved" ctx_id=cd631d58-a9ec-4e36-8045-b346010f573d token=52579
Nov 04 12:45:22 siotel-prod-gj-13 chirpstack-network-server[19126]: time="2019-11-04T12:45:22Z" level=info msg="backend/gateway: downlink tx acknowledgement received" downlink_id=cd631d58-a9ec-4e36-8045-b346010f573d gateway_id=506f980000000777
Nov 04 12:45:22 siotel-prod-gj-13 chirpstack-network-server[19126]: time="2019-11-04T12:45:22Z" level=info msg="sent downlink meta-data to network-controller" ctx_id=cd631d58-a9ec-4e36-8045-b346010f573d
That looks like a misconfiguration somewhere. It looks quite simmilar to Problem with LoraServer and LoraAppServer API?.
I got some questions why ChirpStack. These pages give a bit more background behind the LoRa modulation and what a chirp is:
Hi @brocaar, we checked and the entry in the routing_profile table in loraserver_ns database is correct and all the host:port in the chirpstack-app-server configuration file are as follows:
[application_server.api]
# ip:port to bind the api server
bind="0.0.0.0:8001"
public_host="localhost:8001"
[application_server.external_api]
# ip:port to bind the (user facing) http server to (web-interface and REST / $
bind="0.0.0.0:8080"
[join_server]
# ip:port to bind the join-server api interface to
bind="0.0.0.0:8003"
chirpstack network-server configuration file is set to:
[network_server.api]
# ip:port to bind the api server
bind="0.0.0.0:8001"
[join_server.default]
# hostname:port of the default join-server
#
# This API is provided by LoRa App Server.
server="http://localhost:8003"
We cannot see the gateways and applications page on chirpstack-app-server GUI. Do we have to delete the network-server entity on chirpstack-app-server GUI and register everything again?
Also, the link for ansible-playbook given on https://www.chirpstack.io/guides/ansible-vagrant/ , appears to be broken as I could not see the repo on github. It would be very kind of you if you could provide us with the same. 
Somebody reported (and fixed) a bug in the init script, which might cause this due to a service restart issue. Stay tuned for a bugfix release
Thanks, this has been fixed.
Hi @brocaar, we updated to the latest release with bugfixes. Now, two cases were generated:
On the system where chirpstack-network-server , chirpstack-application-server, chirpstack-gateway-bridge were all on one instance/VM , the update made everything work fine.
But on a distributed system, where chirpstack-application-server was on a different instance and chirpstack-network-server + chirpstack-gateway-bridge was on another different instance, we could not see the last seen of the gateways as well as it is not able to get devices from the applications tab, on clicking it is showing “object does not exists.” We checked the host:port in all the config files, and the entries are correct. How can we solve this?
Thank you!
I think it is better to move this discussion outside this topic Mind creating a new topic?
Good day,
When expect finish of migration from LoRa to ChirpStack?
Hello!, I tried to update the app following the steps shown in the post. I got this:
Get:9 https://artifacts.chirpstack.io/packages/3.x/deb stable InRelease [14.0 kB]
Err:9 https://artifacts.chirpstack.io/packages/3.x/deb stable InRelease
The following signatures were invalid: EXPKEYSIG CFF064C9D12ECB34 Orne Brocaar info@brocaar.com
Reading package lists… Done
N: Ignoring file ‘artifacts_loraserver_io_packages_3_x_deb.list.save2’ in directory ‘/etc/apt/sources.list.d/’ as it has an invalid filename extension
W: GPG error: https://artifacts.chirpstack.io/packages/3.x/deb stable InRelease: The following signatures were invalid: EXPKEYSIG CFF064C9D12ECB34 Orne Brocaar info@brocaar.com
E: The repository ‘https://artifacts.chirpstack.io/packages/3.x/deb stable InRelease’ is not signed.
N: Updating from such a repository can’t be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
boxadm@loraboxvm0001:/etc/apt/sources.list.d$
Any ideas?
Got this same error here when updating the packages.
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://artifacts.chirpstack.io/packages/3.x/deb stable InRelease: The following signatures were invalid: EXPKEYSIG CFF064C9D12ECB34 Orne Brocaar info@brocaar.com
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://artifacts.chirpstack.io/packages/2.x/deb stable InRelease: The following signatures were invalid: EXPKEYSIG CFF064C9D12ECB34 Orne Brocaar info@brocaar.com
W: Failed to fetch https://artifacts.chirpstack.io/packages/3.x/deb/dists/stable/InRelease The following signatures were invalid: EXPKEYSIG CFF064C9D12ECB34 Orne Brocaar info@brocaar.com
W: Failed to fetch https://artifacts.loraserver.io/packages/2.x/deb/dists/stable/InRelease The following signatures were invalid: EXPKEYSIG CFF064C9D12ECB34 Orne Brocaar info@brocaar.com
W: Some index files failed to download. They have been ignored, or old ones used instead.
This has nothing to do with the rename. What happened is that the GPG key expired and you need to re-fetch it to receive the updated key:
sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 1CE2AFD36DBCCA00