Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot deploy to production server #319

Open
guilhermejccavalcanti opened this issue Aug 19, 2017 · 2 comments
Open

Cannot deploy to production server #319

guilhermejccavalcanti opened this issue Aug 19, 2017 · 2 comments

Comments

@guilhermejccavalcanti
Copy link

I'm struggling with Tomcat 8.0.32 and Play 2.4.x, but only in the production server! Locally, the same environment works like a charm.

In particular, when I deploy as ROOT.war, production's tomcat is unable to route the URLs and returns 404. For instance, the first access redirects from index to /login, but it returns 404 instead of the corresponding view.

Now, the weird facts: if I deploy to a sub-context instead of ROOT.war (for instance, app.war), the routing works. Unfortunately this is not a option since reverse routing is bugged in Play 2.4 in sub-contexts (playframework/playframework#4977).

Again, locally everything works. I'm using the same version of tomcat in both enviroments, the same .xml's (differing only in the ports). Any tip?

@yanns
Copy link
Member

yanns commented Aug 23, 2017

If you deploy locally with Tomcat as ROOT.war, it works?

@guilhermejccavalcanti
Copy link
Author

Unfortunatelly not. I changed to another server where I could deploy with "sbt dist" , no need for tomcat. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants