Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.

Marco's avatar
Level 2

Tailwindcss on production server - app.js 504 gateway timeout

Have Laravel 5.5 install with tailwind through npm. All works well locally but on Digital Ocean server - Forge deployed - app.js gives a 504 Gateway Timeout. Have restarted server etc. Can't get it to work. Done fresh install - compared bootstrap 3 preset to tailwind. Bootstrap doesn't give 504 on app.js - tailwind does. Where's the problem, what am I missing here?

0 likes
4 replies
ejdelmonico's avatar

That error is only for setups that have a proxy or gateway and have trouble communicating to the other VM's. I really don't see how Tailwind could be the real issue. Is the install on a single VM?

If so, the problem has to be in how you are including Tailwind in Mix. You have to use postCSS process option I believe.

Marco's avatar
Level 2

You're right. It has nothing to do with Tailwind. Restarted project with Bootstrap 4 and same problem came back after half day of playing around. Tailwind was postCSS, bootstrap is Sass. So now ruling out any css preset or Mix as the cause.

Digital Ocean server setup: 1 GB Memory / 30 GB Disk / AMS3 - Ubuntu 16.04.1 x64. Very basic, single VM

If I look at web inspector / timeline in safari, then app.js has 10.150.35.18 as domain which is strange

ejdelmonico's avatar

That IP is probably the internal DO address. I would check all of your dns settings.

Marco's avatar
Level 2

There's just a A record with server ip

Please or to participate in this conversation.