Submit Feedback
Legacy Knowledge Base
Published Jun. 30, 2025

PaaS deployment fails with HTTP Error 408 Request Timeout

Written By

Sorin Pop

How To articles are not official guidelines or officially supporteddocumentation. They are community-contributed content and may not alwaysreflect the latest updates to Liferay DXP. We welcome your feedback toimprove How to articles!

While we make every effort to ensure this Knowledge Base is accurate, itmay not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with anyfeedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack"publication program, made available for informational purposes. Articlesin this program were published without a requirement for independentediting or verification and are provided "as is" withoutguarantee.

Before using any information from this article, independently verify itssuitability for your situation and project.

Issue

  • Today a build on DEV environment fails repeatedly (3 times) with the same error each time:

     

    Failed to deploy the services in /var/jenkins_home/workspace/xxx_dev/build on liferay.cloud. 
    HttpError: HTTP Error: 408 Request Timeout

Environment

  • PaaS

Resolution

  • The problem was that the webserver service was not deploying any more. This was corrected after fixing some errors in the nginx config files. We now understand that the problem was caused by these changes: https://learn.liferay.com/w/liferay-cloud/reference/breaking-changes#changes-to-the-web-server-service

    Also, after fixing this and the webserver service was deployed successfully, the site did not work, we noticed an error "error connecting to upstream server". The upstream server was at port 81 until now, but now it is on port 8081 (as on UAT env), we checked this on the shell:

    nginx@webserver-594864798d-kfgww:/$ curl 127.0.0.1:81 curl: (7) Failed to connect to 127.0.0.1 port 81: Connection refused
    nginx@webserver-594864798d-kfgww:/$ curl 127.0.0.1:8081
    nginx@webserver-594864798d-kfgww:/$

    So after changing the port to 8081, the site answers again.

Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?