This helps us to proactively resolve potential issues, rather than reacting to a downtime once an error has happened.įirewalls are the bedrock of server security. That is why Dedicated Server Admins audit our customer servers at least once a month.ĭuring this audit, we detect possible performance bottlenecks, security loopholes and hardware issues. How Bobcares prevents configuration errorsĪs a quick aside, here’s how we prevent server errors related to config issues.Ĭonfiguration errors are generally caused by stale server settings that’s not adjusted for new traffic or site upgrades. We are online 24/7 and can attend your ticket within a few mins. If you need help fixing a similar error, click here to talk to our Nginx admins. If you are not familiar with PHP or web server settings, it is best to ask a server administrator. WARNING: server reached max_children setting (30), consider raising itĮRROR: unable to read what child say: Bad file descriptor (9) this error here says the PHP application reached the maximum limit of processes (defined by pm.max_children setting) allowed. You really need to scan the error log and pay attention to what the error says.įor eg. There is no easy way to find out a configuration error. Capacity limits (like no: of connections per IP) set too restrictively causing legit visits to fail.Incorrect memory or file limits set for PHP applications.Apache firewall settings (mod_security) syntax error causing Apache to crash.DB login details set incorrectly after a recent migration, restore or upgrade.DNS resolver misconfigured in Nginx causing domain lookups to fail.Some configuration issues that we’ve seen are: If even one of these services have a wrong config entry, that service will fail to respond, and Nginx will show “502 bad gateway” error. This includes DNS resolution, Apache processes, PHP services, DB server, etc. Your Nginx server and the backend services relies on many sub-systems to work properly. We are online 24/7 and can help you in a few minutes. If your server is currently under high load, and you need urgent help, click here to contact our Emergency Server Support techs.
![festify bad gateway festify bad gateway](https://www.solos-art.com/wp-content/uploads/morris-house1-1024x436.jpg)
The we find out which service is abusing that resource, and from that point, find out which user in that service owns the abusive script or software.Ĭlick here to know more about high load troubleshooting. To troubleshoot a high load issue, first we figure out which resource is being abused (I/O, Memory, CPU or Net).
![festify bad gateway festify bad gateway](https://i0.wp.com/cdnssl.ubergizmo.com/wp-content/uploads/2020/01/502-Bad-Gateway-Error.png)
![festify bad gateway festify bad gateway](https://www.lifewire.com/thmb/BJmj6COwHibweJyK33AY7LblpwY=/1663x1049/filters:no_upscale():max_bytes(150000):strip_icc()/001_502-bad-gateway-error-explained-2622939-5c6350c9c9e77c0001d323ab.jpg)
* Restarting PHP FastCGI Process Manager php-fpm If you suspect a backend service is unresponsive or failed, you can try killing all unresponsive processes and restarting the service.įor instance, here’s one way we kill defunct PHP-FPM processes and restart services. The reasons for service failure can range from traffic spikes and resource limits to disk errors and DDoS attacks. Some services that we’ve seen to fail are: So, if any of these services crash or freeze, Nginx won’t get any data from them, resulting in “502 Bad gateway” error. Nginx depends on backend services like PHP-FPM, database services and cache servers to run web applications.
![festify bad gateway festify bad gateway](https://www.outofbit.it/wp-content/uploads/2018/12/Error-502-1024x576.jpg)
We’ve listed the top 5 reasons for 502 Bad Gateway error, and how we fix them. You know something is messed up, because it says “ failed” and “ refused“.īut WHAT? You hardly have time to get a PhD in computer science. So, many web masters roll up their sleeves and look at the error log:Ĥ 08:34:43 949#949: * 7 connect() failed (111: Connection refused) while connecting to upstream, client:, server:, request: "GET /myurl-this/ HTTP/1.0", subrequest: "/redis-fetch", upstream: "redis://127.0.0.1:6379", host: "", referrer: "" 3 word error message – because Nginx doesn’t love you.