iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Antihost offers VPS plans with one-click Coolify, NVMe storage and a 14-day free trial.
A 504 Gateway Timeout in Coolify means the reverse proxy reached the point of waiting for your application but did not receive a response within the configured period. Start by classifying when the error appears: an immediate 504 usually points to routing or Docker-network reachability, a failure after roughly 60 seconds usually points to a timeout, and intermittent failures can indicate isolation or an overloaded application. Check the proxy and application logs, verify DNS, firewall access, generated routes and internal ports, then repair the shared Docker network before increasing any timeout.
Coolify uses Traefik through the coolify-proxy container by default. The normal request path is public DNS and firewall access, then Traefik, then Docker networking to the application container. A break at any of those points can look like a gateway error, but each failure has a different fix.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
What a 504 means in Coolify
Coolify’s documentation defines a gateway timeout as a situation in which the Coolify proxy cannot get a response from the application within the configured timeout period. The proxy is alive, but the upstream application is too slow, unreachable over the expected network, still starting, or not answering the requested route.
| Status | What the proxy could do | Typical direction for investigation |
|---|---|---|
| 504 Gateway Timeout | The proxy waited for an upstream response and did not receive one in time. | Check Docker-network reachability, application readiness, saturation, long-running work and timeout settings. |
| 502 Bad Gateway | The proxy could not connect to the application at all. | Check whether the container is running, the generated route and target port are correct, and whether the application is listening. |
Do not treat every 504 as proof that the application needs a longer timeout. A container on an isolated custom network can be perfectly healthy from inside its own network and still be invisible to coolify-proxy. Conversely, a large upload or a genuinely slow report can be healthy but exceed the current proxy limit.
#1 Best Overall
- Powerful Turbo Fan:CAGIWIRU Electric Air Duster have reached speed up to 130000RPM,Can efficient remove dust and debris.With LED light and Three Adjustable Speed to meet with different cleaning tasks.
- With Attached USB C Fasting Charging cable.Charing 3 hours,Enjoy up to 240 minutes of use on the lowest setting, For third speed can use for 25mins.with four charging options to meet with your needs.
- Wide Application: attached 5 different nozzles,making it suitable for a variety of scenes, such as car,pet, pc, keyboards, and other electronic devices. It also serves for office and home clean duster.
- Handy Design & Portable:Cordless air duster electric nozzle is Light weight and small size, design and comfortable to hold and space saving, convenient to carry around. You can put it in your room or inside the car without taking up space.
- Economical &Reusable: Built durable materials with a long-lasting battery,our CAGIWIRU air duster it's a sustainable alternative to disposable air cans.
Use the timing to choose the first test
Immediate 504
If the browser returns 504 almost instantly, begin with reachability and configuration rather than timeout tuning. Verify the proxy container, the generated route, the target port and the Docker networks. An immediate failure leaves little time for an upstream request to run, so a missing route or an unreachable network is more likely than a slow endpoint.
Failure after about 60 seconds
A response after approximately one minute is Coolify’s documented timeout heuristic, not a universal measured limit. Treat it as evidence that a request was attempted but outlasted a configured deadline. Confirm this by checking proxy logs for timeout messages and application logs for a request that continued, stalled on a dependency, or was still processing.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Intermittent 504 responses
Intermittent errors can indicate network isolation, a container that is repeatedly restarting, dependency failures, or resource saturation. Compare successful and failed requests with timestamps in both log streams. If only some services in a Compose stack fail, inspect the network membership of each service rather than changing a global proxy timeout.
Verify the public request path before changing settings
Work from the outside in. A correct application container cannot answer a request that never reaches the server, and a working DNS record cannot compensate for a route that targets the wrong port.
- Confirm DNS. Check that the hostname used in the browser resolves to the public address of the server running Coolify. A record pointing at an old server can produce a gateway response from an entirely different proxy.
- Check firewall and security-group access. Allow the expected web traffic to the server and ensure host-level rules are not dropping or redirecting it. Coolify does not manage every provider firewall or security group on your behalf.
- Confirm that the proxy is running. The default integrated proxy is the
coolify-proxycontainer. A stopped or repeatedly restarting proxy must be repaired before application-level tests are meaningful. - Inspect the generated route. Ensure the configured domain matches the hostname being requested and that the route points to the intended service and internal port. A typo in a domain or port can leave the proxy waiting for an endpoint that does not exist.
- Verify the application’s listening address and port. The process must listen on the port configured in Coolify and, in most containerized web applications, on an address reachable from the container network rather than only an unavailable interface.
Complete these checks even when the page displays a familiar 504 template. The template identifies the responding proxy, not necessarily the container that was supposed to serve the request.
Rank #2
- Screen Cleaner is Your Screen’s New Bestfriend! - EVEO is proud to present a screen cleaner that’s perfectly suited for your TV. Meet your new screen cleaner, computer screen cleaner, laptop cleaner, iPad cleaner, Macbook,tv cleaner or any other electronic device. Our screen cleaner spray and wipe along with the included plush microfiber cloth, easily removes dust, fingerprints & other smudges on the screen’s surface. Clean effectively for a streak-free screen
- Gentle on your Screens - Our screen cleaner spray and wipes is compatible to be used even for the most sensitive LCD, LED, CRT, and OLED screens in proper use. Be at ease knowing that this product is compatible with all the major brands: LG, SONY, Samsung, Sharp, iPad, iPhone, Android screens, Kindle, PC monitors - we’ve got you covered! Can be used as LCD screen cleaner, tv cleaner, smart tv screen cleaner, and more
- Premium Super Soft Plush Microfiber Cloth - Included in this efficient screen cleaning kit. This screen cleaner spray and wipe has our signature plush microfiber cloth specially designed to comply with screens and monitors and leave them streak-free. Has been shown to effectively absorbs stubborn stains, zero streaks, and no fiber shedding. Always use this together with our screen cleaner for the best results
- Easy-to-Use Screen Cleaner Kit + microfiber cleaning cloth - The EVEO Screen Cleaning Kit will easily be your new favorite tool when it comes to taking care of the things you love most, quick and easy solution for a streak-free screen. Simply screw on the sprayer gun on the screen cleaner bottle. Spray the cleaning liquid onto the microfiber cloth, then wipe the screen until desired cleanliness & shine is achieved.
- Quality Screen Care Kit Worth Purchasing - Enjoy a convenient Screen Cleaner anytime, anywhere you need it. Your satisfaction is our top priority. We stand behind the quality of our products and that’s why, you shouldn’t be worrying at all. We manufacture the Best Screen Cleaner. and can be used for laptop cleaning kit, laptop screen cleaner, tv screen cleaner for smart tv. MacBook screen cleaner, monitor cleaner or screen cleaner spray for electronic devices with microfiber cleaning cloth
Inspect Docker network membership
Coolify documents custom Docker-network isolation as a primary 504 scenario. First list the networks and then show which networks each relevant container has joined:
Free tools Windows power users keep installed
One-click scans. No signup required.
docker network ls
docker ps --format "table {{.Names}}t{{.Networks}}"Find both coolify-proxy and the application container in the second command’s output. They need a reachable common network for the proxy to open a connection to the application. A Compose application commonly receives a resource-specific network by default; it does not automatically join the predefined coolify network just because it is deployed by Coolify.
How to interpret the output
- If the proxy and application share a network, continue by checking the generated route, target port and application logs. Shared membership does not prove that the process is listening, but it removes one major isolation cause.
- If they have no network in common, the proxy cannot reach the service through Docker DNS. Enable the predefined or shared Coolify network for the resource when that stack is intended to be publicly reached through Coolify.
- If a container is attached to an unexpected network, check the Compose or resource network configuration for an explicit custom network that replaced the expected shared connection.
After enabling the shared network, redeploy or restart the resource so that Docker recreates the proxy-to-container connections. Test again only after the new container and route are running; changing a Compose file without recreating the relevant containers leaves the old network attachments in place.
Read both log streams at the same time
Collect recent entries from the proxy and the application. Replace the placeholder with the actual container name shown by docker ps:
docker logs coolify-proxy --tail 200
docker logs <your-container-name> --tail 200Record the time of a failed request and compare both outputs around that timestamp.
Rank #3
- 【Large size】：Measuring 800 x 300 mm/ 31. 5×12 inches, which is wider and taller than others. Large mouse pad can perfectly fit your keyboard and mouse of any size, and there is also ample space for peripherals such as phones, tablets, etc.
- 【LED backlight mouse pad】：Blade Hawks RGB mouse pad provides 7 static modes and 7 dynamic modes will give you the options you are looking for. Power-off memory function remembers the last lighting mode you selected. The super glow fiber Chroma will give you a colorful gaming setup that you want.
- 【Anti-slip rubber base】：Made from Natural rubber, this gaming mousepad will firmly grip your desktop, allowing you to enjoy the ultimate precision in the games you are most passionate about. It also comes with a texture that enhances this ability even further.
- 【Smooth and waterproof surface】: Micro-textured cloth surface, for extremely precise mouse control and a smooth movement. When liquid splashes on the gaming mouse pad, it forms water droplets and slides down. Will not delay your work or gameplay.
- 【Plug and play】: This mouse and keyboard pad is powered by USB, plug and play, no driver required. One button control light modes. Press one time to change the lighting mode, press twice to change the brightness, press and hold about 3 seconds turn ON/OFF.
Patterns in the proxy log
- A timeout entry with no corresponding application request suggests a route, network or port problem.
- A timeout that names the application upstream shows that Traefik selected a route but did not receive a timely response.
- Repeated connection or name-resolution errors point toward network membership, container restarts or a stale route.
Patterns in the application log
- Startup migrations, dependency connection retries and readiness errors can explain why the first requests time out.
- Long database queries, exhausted worker pools, memory pressure or repeated restarts can make only some requests exceed the deadline.
- No log entry for a request that the proxy says it forwarded is a reason to return to network and target-port checks.
Logs prevent a common mistake: raising a timeout when the application is actually crashing, or rebuilding a network when the endpoint is simply performing a legitimate long-running operation.
Test the endpoint from inside the application container
A test from inside the container separates application behavior from DNS, TLS, firewall and proxy behavior. If a Coolify health check is enabled, execute the same lightweight request in the application’s Terminal, using the internal port:
curl --fail http://localhost:3000/healthReplace port 3000 and path /health with the values your application actually uses. The command must target the container’s internal listening port, not the public HTTPS port or an external hostname.
Reading the result
- A successful response shows that the process is answering locally. Continue with network membership, route generation and proxy logs.
- A connection-refused result means the process is not listening on that port, has not started, or is bound to an address that does not accept the request.
- A timeout or failed HTTP status can indicate application startup, dependency or readiness problems. Inspect the application log before touching proxy settings.
The final image must contain an HTTP client. Coolify’s health-check guidance notes that curl or wget must be available in the image. If neither exists, install one in the image or use an equivalent diagnostic method; do not assume a health check can run successfully just because the application itself serves HTTP.
Repair the common network and route failures
Join the predefined shared network
For a stack that should be published through Coolify, enable its predefined/shared network in the resource configuration instead of isolating it on a private custom network. Redeploy or restart after saving the change. Then verify with docker ps --format that both the recreated application container and coolify-proxy share the intended network.
Rank #4
- 【Softer and More Comfortable】Vaydeer wrist rest has unique diamond pattern, which is the combination of softness and aesthetics. The materials of wrist rest are improved into higher quality memory foam and covered with silky smooth lycra. The computer wrist rest makes you as comfortable and cushiony as like rest your wrists on clouds.
- 【Ergonomic Wrist Saver】The wrist rests for keyboard and mouse comes with a 17.32×3.15×0.83 inch keyboard wrist pad and a 5.94×3.15×0.83 inch mouse wrist support. Based on ergonomic design, the unique concave shape is the perfect fit for your wrist joints. The wrist rest pad fits most computer keyboards and laptops, improve hand and wrist posture, release your wrist and arm stress.
- 【Non-Slip Rubber Bottom】Featuring an anti-skid silicone base on the bottom, this wrist keyboard support stays firmly in place on your desk, preventing the padding from sliding around, ensuring stable and consistent wrist support during extended computer sessions.
- 【Better Experience & Pain Relief】Our keyboard arm rest is beneficial to alleviate the soreness caused by direct contact and friction between your arm and a hard desk surface, reducing the risk of wrist fatigue or carpal tunnel. The soft texture of memory foam can evenly distribute the pressure around your wrists and provide good support with just enough give.
- 【Helpful in Multiple Scenarios】Whether you're working, studying, writing, typing, gaming, this keyboard and mouse rest combo is an essential accessory to add comfort and support to your hands and wrists. It’s also a great gift for men, women, family, friend, coworker, gamer, teacher, etc.
Correct the target port
Use the port on which the process listens inside the container. Do not substitute the host-published port unless the deployment specifically uses that architecture. Confirm the value by checking the application configuration and by running the local health request against the same port.
Regenerate a stale route
If the domain or target port changed, redeploy the resource so Coolify regenerates the proxy configuration. A route generated for an old service name, old port or old hostname can continue producing gateway errors until the proxy receives the updated configuration.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchRecover a failed proxy or application container
Inspect restart loops and exit messages in the logs. Repair the underlying configuration, dependency or resource issue, then restart or redeploy. A proxy restart can briefly affect every public route on that Coolify server, so schedule it when a short interruption is acceptable and verify all domains afterward.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Increase the proxy timeout only for genuinely slow work
Timeout changes are appropriate for workloads such as large uploads, large downloads or an endpoint that is expected to take longer than the current deadline. They are not a substitute for a missing Docker network, a wrong port or an application that is stuck.
Coolify does not publish one universal timeout value that fits every installation. The correct setting depends on the application, request size, server capacity and surrounding infrastructure. Choose a value that covers the legitimate operation with margin, then confirm the result in proxy logs. Avoid setting an extremely large value indiscriminately: a blocked request can consume a worker, connection or memory for the entire interval and make an overload worse.
Best Value
- 【No Drill Mounted】Cable management tray can be assembled in as little as 3 minutes or less-simply. Side clips easily clampe the edge of desk, pass through the holes on the sides, and secure excess cables with baskets. Desk cable management supports inward or outward installation to meet your needs in different scenarios, and provides you with great convenience when collecting and organizing wires.
- 【Rubber Pad Protects Desk】Wire organizer under desk built-in soft rubber pads on the clamp protect your desk from scratches, so you will not damage your furniture or office.
- 【Sturdy and Beautiful】Cord management under desk is made of high-quality carbon steel and holds about 15 lbs. The wire basket has 2 holes on each side of the tray to enable your cables to pass freely. Cable baskets are suitable for desk thickness use from 0.4" to 2.4".
- 【Space Saving & Keep Organized】Desk cable management tray holds all your power cords, outlet strips, USB hubs and computer transformers hidden from your feet, and the data cables will not enter the vacuum cleaner to keep your desk clean and tidy. Desk wire organizer is also suitable for use in the kitchen and outdoors.
- 【Reduce Safety Risks】Cable tray under desk keeps all plugs away from your kids, no more worry about tripping. Using 2 holes wire tray saves extra space, helps you easily cabling and wire protection. The mesh design is not easy to accumulate dust, but avoids safety accidents caused by messy wires.
Use evidence to select a value
- Measure the slow operation from the application side and identify whether the delay is upload, download, computation or a dependency.
- Check that the application continues processing while the proxy waits; an application that stops responding needs an application or infrastructure fix instead.
- Raise the relevant proxy timeout in the deployment’s proxy configuration, redeploy if required, and repeat the same request.
- Watch both log streams for completion, a new timeout boundary or resource exhaustion. If another load balancer, firewall or client has a shorter limit, that component may still terminate the request first.
Configure health checks for readiness, not heavy workloads
Coolify describes a health check as a signal to Docker and Coolify that an application container is ready. A useful check is fast, local and representative of basic readiness. It should not run a report, trigger a migration or depend on a slow third-party API.
- Use the internal port and a dedicated endpoint such as
/healthwhen the application provides one. - Ensure the endpoint returns a success status only after the process can serve normal traffic.
- Keep the check lightweight so repeated probes do not create the same saturation that caused the 504.
- Make sure the image contains
curlorwget, or provide the client required by the configured check.
Health checks improve detection but do not repair network isolation. A container can report healthy to Docker while remaining unreachable by the proxy if it is attached only to a private network.
Understand the proxy options before replacing Traefik
Traefik is Coolify’s default integrated reverse proxy. Coolify also documents Caddy and a Custom (None) option. Changing the proxy is a platform-wide decision, not a narrow fix for one slow endpoint.
| Option | Network reachability | Route and label generation | TLS handling | Timeout and health-check control | Operational ownership and risk |
|---|---|---|---|---|---|
| Traefik | Uses the Docker networking path to the application; containers still need a reachable shared network. | Integrated Coolify route generation. | Handled through the integrated proxy configuration. | Configured in the proxy and application deployment; verify behavior in proxy logs. | Default Coolify path, so troubleshooting matches the platform’s normal assumptions. |
| Caddy | Still depends on a network path from the proxy to each service. | Uses the alternative integration’s generated configuration. | Managed by the chosen proxy integration. | Use that proxy’s timeout and health-check controls while preserving internal-port and network checks. | Requires understanding the alternative integration; changing it can interrupt every public route. |
| Custom (None) | Must be provided by the proxy or load balancer you operate. | You own route discovery or configuration. | You own certificates and renewal behavior. | You own timeout, retry and health-check policy. | Most operational responsibility; replacing the integrated proxy can affect all domains at once. |
For a single 504, keep Traefik and fix the documented failure in the request path unless you have a deliberate platform-wide reason to change proxies. Any replacement must preserve network reachability, route targets, TLS behavior, timeout policy and health checks for every public application.
Verify the fix and prevent a recurrence
- Request the affected domain from an external client and confirm the expected status and content.
- Repeat the previously failing upload, download or endpoint, not just a fast homepage request.
- Review
coolify-proxylogs for recurring timeout, connection or route errors. - Review the application log for restarts, dependency failures and saturation during the test.
- Keep a lightweight readiness health check enabled and confirm it uses the internal port.
- Monitor proxy logs and basic uptime so an intermittent failure is captured with a timestamp before containers restart and erase useful context.
The durable fix is the one that matches the evidence: restore a shared Docker network for isolation, correct DNS or firewall access for an external-path failure, repair the route or internal port for a configuration error, address application readiness or capacity for a slow service, and adjust the timeout only when the workload is legitimately longer than the current limit.
Recommended Free Tools
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
