This article documents the activation and setup errors in Remote Staging, and lists steps to resolve the issue or avoid it altogether. If users want to know about activating staging in general, please see Enable Remote Live Staging.
Resolution
Error: Users are unable to publish content to Remote Staging.
Summary: Users are attempting to publish content to a remote live server from their staged environment but encounter errors.
Common Causes
- Servers are missing the correct
tunnel.servlet.hosts.allowed=in the remote server’sportal-ext.properties. - SSL has been improperly configured.
Recommended Solution
As already explained on the user interface, and in other documentation, put the tunnel.servlet.hosts.allowed= setting in remote server's portal-ext.properties with the IP address of the staged server.
Alternately, users can use the Control Panel on the Remote Server. To use the Control Panel, execute the following steps:
- Navigate to Control Panel > Configuration > System Settings
- Search for the
Tunnel Auth Verifierssetting and click it.(For users working on DXP 7.1, the setting has been renamed Tunnel Authentication)
- Click on
/api/liferay/do. - In the list of Hosts allowed, enter the URL of the Staged Server.
- Click Update
If users desire to publish content across a secure connection, enable the application server's SSL connections and consult the appropriate application server documentation.
Prevention Tips
-
If the user has enabled SSL, ensure that Java security files have been generated correctly and that they are in the right file folder for each application server. Ensure that the application server's secure ports have been activated (e.g. 8443, in most cases).
-
Ensure that the target's IP, port, and site ID (e.g. 10444) are correct in the staged server.
Additional Information
- Staging Page Publication (Portal 6.2)
- How to enable SSL in Apache Tomcat
- How to enable SSL in JBoss EAP (or JBoss 7.x)