Thanks, this has been fixed.
1 Like
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?
1 Like
I have created a new topic Good day,
When expect finish of migration from LoRa to ChirpStack?
1 Like
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