On bundle install showing error : `fetch_http': bad response Service Unavailable 503 - ruby-on-rails

In command prompt when I run bundle install
I got an error showing there
`fetch_http': bad response Service Unavailable 503
If anybody else faced such error before?

#ruby,
I suppose there will be some problem with your Internet connection. Please recheck your connection.
Or any plugin/gem is unfetchable.
503 ->Service Unavailable
That means:
Server cannot respond due to maintenance or overloading. For example, a servlet might return this header if some thread or database connection pool is currently full. Server can supply a Retry-After header.

Related

Docker "The proxy server received an invalid response from an upstream server." after system reboot

I'm running a Docker MERN stack on CentOS 7 with WHM, CPanels and Apache, everything works fine until I reboot the server. I get the following error on the webpage:
The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request
Reason: Error reading from remote server
Additionally, a 502 Bad Gateway error was encountered while trying to use an ErrorDocument to handle the request.
After searching around stackoverflow I found that if I run this command my problem is solved:
iptables -t filter -F
My question is, whats causing my problem? How do I configure my server so I don't need to run this command everytime my server reboots? Do I make a script to run this command everytime it restarts? Do I configure iptables?
Just to answer my own question, I was dumb and forgor to open proper outbound ports, I only opened inbound ports.

An Error occurred delivering to the app store

I am trying to release my project to the app store. However I get this error:
'An Error occurred delivering to the app store.'
First I tried to release it directly from Xcode. Following the advice I found on here, I then tried it using Transporter. The same error occurred but I got an extended delivery log:
[2019-10-29 14:04:49 WITA] INFO: An error occurred checking the HEAD for: https://contentdelivery.itunes.apple.com/transporter/repositories/j2se8/latest/repository.xml Unable to tunnel through proxy. Proxy returns "HTTP/1.1 502 Bad Gateway" Exception's name: java.io.IOException, Exception's message: Unable to tunnel through proxy. Proxy returns "HTTP/1.1 502 Bad Gateway"
Can someone help me fix this or point me in the right direction please, as I'm pretty lost with it.
Many thanks
Try following
Go to Preferences > Network > Advanced > Proxies and make sure "Auto Proxy Discovery" and "Automatic Proxy Configuration" are checked but none of the other proxy options are checked.

503, Service Unavailable error was encountered while trying to use an ErrorDocument to handle the request

Sometimes the following error appears:
Service Unavailable
The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.
Additionally, a 503 Service Unavailable error was encountered while trying to use an ErrorDocument to handle the request.
How can I fix it?

Disconnecting client with error: client socket write error: Broken pipe - passenger 5.0.2

When I start Phusion Passenger Standalone web server (version 5.0.2), I see the following error in the log (even though everything works fine otherwise):
ServerKit/Server.h:892 ]: [Client 1-1] Disconnecting client with error: client socket write error: Broken pipe (errno=32)
Any idea what might be causing it?
Note: I start the server with foreman start and I stop it with control-c.
Passenger author here. Actually, the issue maxd linked to has got nothing to do with it.
The "Disconnecting client with error: client socket write error: Broken pipe" is a harmless informational message. It's quite normal, but I forgot to give it a lower logging level. I will do that in the next release. You can safely ignore this message. Nothing bad is going on.

Passenger error when lots of concurrent calls

While doing a load test I found passenger throwing below error at first when lots of concurrent requests hit server. And, client side it gives 502 error code. However, after some requests say 1000- 2000 requests its works fine.
2013/07/23 11:22:46 [error] 14131#0: *50226 connect() to /tmp/passenger.1.0.14107/generation-
0/request failed (11: Resource temporarily unavailable) while connecting to upstream, client: 10.251.18.167, server: 10.*, request: "GET /home HTTP/1.0", upstream: "passenger:/tmp/passenger.1.0.14107/generation-0/request:", host: hostname
Server Details.
Passenger 4.0.10
ruby 1.9.3/2.0
Server Ec2 m1.xlarge
64-bit 4core 15gb
Ubuntu 12:24 LTS
Its a web server which servers dynamic webpages for rails framework
Can somebody suggest what the issue might be?
A "temporarily unavailable" error in that context means the socket backlog is full. That can happen if your app cannot handle your requests fast enough. What happens is that the queue grows and grows, until it's full, and then you start getting those errors. In the mean time your users' response times grow and grow until they get an error. This is probably an application-level problem so it's best to try starting there. Try figuring out why your app is slow, at which request it is slow, and fix that. Or maybe you need to scale to more servers.

Resources