The purpose of the option to forcibly disable staging is to allow staging to be disabled even when the connection to the remote live site can't be established. However, this isn't working currently. When you select the option to forcibly disable remote staging, Liferay will still attempt to connect to the remote live site and fail if it cannot establish a connection.
This is happening because we don't properly set the "stagingType" parameter during the request to forcibly disable staging. The parameter should be set to TYPE_NOT_STAGED to communicate that we want the site to be unstaged, but it is instead set to TYPE_REMOTE_STAGING which tells the backend that we want to enable remote staging (which requires it to make requests to the remote live site).
Steps to Reproduce
1. Configure 2 instances of Liferay with different IP/ports and shared tunnel secrets in portal-ext, e.g.
2. Start each instance
3. Configure first instance to remote stage with 2nd instance
4. Shut down 2nd instance
5. Attempt to change port # of remote instance in first instance's staging settings. This fails
6. In resulting error message on page, click on 'forcibly disable'
Expected Result: Staging is disabled successfully.
Actual Result: Staging is not disabled, and the following error message appears in the logs:
ERROR [http-nio-8080-exec-1][SiteAdministrationPanelCategoryDisplayContext:212] Unable to connect to remote live: java.net.ConnectException: Connection refused (Connection refused)