Azure pre-configured VM - fails to load after changing config
I've been running Wowza instances in Azure for about a year now (custom built) and decided to try the recently introduced pre-configured VMs. Initially everything went fine following the provided guide.
However, once I make changes via the Management Console, or change my own custom code, and restart Wowza, the system doesn't return to operational. The management page remains up, but it is unable to contact the underlying API. Attempting to reach the server at port 1935 shows that Wowza is down/unresponsive.
I am able to verify via SSH that both the Engine & Manager are running. I do not see any errors logged (in fact the normal log files are not even touched) so it appears the issue occurs prior to my code being loaded.
Rebooting the VM itself does not fix the problem either.
Any help you can offer on how to debug or find helpful startup logs would be great.
It does suggest a bug in the Azure infrastructure. If the reboot in the command line works, and assuming that is what the DashBoard request tries to do behind the scenes then it would be something to open a support request with Azure.
As you have checked Wowza is running as it should be then it suggests a network/firewall set up problem after the reboot in the Azure DashBoard infrastructure.