Hello @imoteb This works as designed. We shutdown the engine if you click on save and exit. But we don't shutdown it, when you click on save. In the second case, you must shutdown the engine on your own. The engine is listening on every network interface, because a lot of our users have headless server installation and they need to open the engine configuration ui on another host. If you want to block access from other another host, you can use a firewall. Kind regards, Alex

Hello @imoteb This works as designed. We shutdown the engine if you click on save and exit. But we don't shutdown it, when you click on save. In the second case, you must shutdown the engine on your own. The engine is listening on every network interface, because a lot of our users have headless server installation and they need to open the engine configuration ui on another host. If you want to block access from other host, you can use a firewall. Kind regards, Alex

Hello @imoteb This works as designed. We shutdown the engine if you click on save and exit. But we don't shutdown it, when you click on save. In the second case, you must shutdown the engine on your own. The engine is listening on every network interface, because a lot of our users have headless server installation and they need to open the engine configuration ui on another host. Kind regards, Alex