Before Opening
Voltar para Before Opening
- Antes de Abrir um Ticket da API do Liferay
- Antes de Abrir um Ticket da Biblioteca de Documentos
- Antes de Abrir um Ticket de Autenticação
- Antes de Abrir um Ticket de Busca/Indexação
- Antes de Abrir um Ticket de Chave de Ativação
- Antes de Abrir um Ticket de Cluster
- Antes de Abrir um Ticket de Gerenciamento de Conteúdos Web
- Antes de Abrir um Ticket de Implantação do Portal
- Antes de Abrir um Ticket de Interface de Usuário (UI)
- Antes de Abrir um Ticket de LAR/Staging
- Antes de Abrir um Ticket de Segurança
- Antes de Abrir um Ticket Liferay de Performance
- Before Opening a Liferay Sync Ticket
- Before Opening an Accessibility Ticket
- Before Opening an Upgrade Ticket
- Before Opening a Shutdown/Inoperable System Ticket
- Before opening a ticket related to VPN on Liferay PaaS
Before opening a ticket related to VPN on Liferay PaaS
Note: please note that Liferay has renamed its Liferay Experience Could offerings to Liferay SaaS (formerly LXC) and Liferay PaaS (formerly LXC-SM).
The following article outlines a short checklist of questions to ask and steps to take before opening a ticket related to VPN on Liferay PaaS. By taking a moment to go through this checklist before opening a request, you are ensuring the fastest possible resolution for your particular issue.
If you can't get a "Connected" status:
- Make sure you are using one of the supported protocols: OpenVPN or IPsec (IKEv2).
- Are you sure your VPN is Client-to-Site? We do not support a Site-to-Site VPN in shared clusters.
- Site-to-Site VPNs are only supported with subscriptions that include a private cluster, and can only be configured with Google Cloud VPN.
- Can you connect to this VPN server using a Linux VPN client? If you can't, you most likely won't be able to connect to the VPN server using our Liferay Experience Cloud SM client.
- Do you have any Firewall role that might prevent the Liferay Experience Cloud SM client from connecting to your VPN server? You can check your firewall log to see if the Liferay PaaS client connection request is getting through.
If you get a "Connected" status but the VPN still does not seem to be working:
- Are you using
<vpn:port>instead of<ip_address:port>? After mapping an IP address and port on Liferay Experience Cloud SM, you must refer to it usingVPN:mapped_port.
Let's say you have mapped 192.168.0.0:8080 to vpn:8080. After that, if you need to use this IP+port on Liferay DXP, for example, you need to use the VPN:8080 terminology instead of 192.168.0.0:8080. - Do you have any HTTP service running on your private network? If yes, a good test is to map this service into a Liferay Experience Cloud SM port and try to run a
curlcommand from the Liferay Service shell to check the results. - Are you mapping the same IP and port combination to multiple Liferay Experience Cloud SM ports? If so, it is not possible to have a successful result. Each combination IP+port should be mapped into a unique Liferay Experience Cloud SM port.
Additional Information
On this page