Hi @eduard, thanks for all the details you provided in this thread.
We recently updated the Bitnami Magento cloud images it seems like this particular use case was not documented properly.
What is happening is that when you run "sudo /opt/bitnami/ctlscript.sh start", the underlying service manager (Provisioner) does not rely on Gonit and will start Varnish anyways. However, since it's running at port 80, it conflicts with Apache's port 80 which you just configured and causing this failure.
We're aware of the service manager usability issues, and we're currently evaluating different ways to solve this issue for good. Unfortunately we're not able to give an ETA for when a definitive fix will be provided, and we expect that some time will pass before that happen.
To workaround this issue for now, I would recommend one of the following options:
- Disable Varnish completely, by overriding the Varnish startup script:
$ sudo mv /opt/bitnami/scripts/varnish/start.sh /opt/bitnami/scripts/varnish/start.sh.disabled
$ sudo ln -s /bin/true /opt/bitnami/scripts/varnish/start.sh
- If you wanted to keep Varnish running (but in a different port), you would only need to change this value:
$ echo 'export VARNISH_PORT_NUMBER=81' | sudo tee -a /opt/bitnami/scripts/varnish-env.sh
Hope it works!
Note: We'll also work on updating our documentation so issues like these don't happen anymore.