I have to network servers, sharing the same database behind a load-balancer. This worked well so far. after upgrading to version 3.6.0 and App Server to Version 3.6.1 i have the following problem:
–> Adding a new Gateway:
Error via API and Gui: Object does not exist --> Object seams to be the Network-Server
So i checkt the Network Server and just wanted to update it in the GUI (do no changes to it, just save it again) --> Object does not exist
When i check the database from chripstack app server, there is the right entry for the network server with the url from the load balancer
also, it seams to work. i still can recive data from sensors/nodes via gateways allready registerd
as i have a test enviroment and a productiv enviroment - i wanted to make sure that they dont disturb each other. as the app server has the Application-server identifier - i wanted to change this, so my enviroments have different ID’s.
Of Course it is not recommended to change - but i did…
So AppServer could not find the routing-profile-id anymore and therefore the problems came up.
i could solve it by change it back.