I solved it .
It was mix of small little problems that together hindered the correct
answer:
- changed in golang webserver HOST = 127.0.0.1
- capitalized the first letter of each element of the Puser struct in order
to make it visible to json decoder
- used correctly the curl command:
curl -d'{"fi
> Subject: Can someone explain me why "curl: (7) Failed to connect to
> 127.0.0.1 port 2000: Connection refused" ?
>
> Hi!,
>
> I do not understand why it says "curl: (7) Failed to connect to 127.0.0.1 port
> 2000: Connection refused" :
> curl -X PO
Hi!,
I do not understand why it says "curl: (7) Failed to connect to 127.0.0.1
port 2000: Connection refused" :
curl -X POST -F 'first_name=pinco' -F 'last_name=pallo' -F
'company_name=Company' -F 'email=pinco.pa...@company.com' -F 'tel=
> On 15 Aug 2018, at 14:05, Sergey Kandaurov wrote:
>
>
>> On 15 Aug 2018, at 13:02, Gerben Wierda wrote:
>
> [..]
>
>> But nginx reports (apparently once per session):
>> 2018/08/15 11:34:48 [error] 242#0: *881 kevent() reported that connect()
>
> On 15 Aug 2018, at 13:02, Gerben Wierda wrote:
[..]
> But nginx reports (apparently once per session):
>2018/08/15 11:34:48 [error] 242#0: *881 kevent() reported that connect()
> failed (61: Connection refused) while connecting to upstream, client:
> 192.168.2.67,
ts (apparently once per session):
>2018/08/15 11:34:48 [error] 242#0: *881 kevent() reported that connect()
> failed (61: Connection refused) while connecting to upstream, client:
> 192.168.2.67, server: MYHOST, request: “GET
> /gerbentest/?delimiter=%2F&max-keys=1000&prefix
works fine.
But nginx reports (apparently once per session):
2018/08/15 11:34:48 [error] 242#0: *881 kevent() reported that connect()
failed (61: Connection refused) while connecting to upstream, client:
192.168.2.67, server: MYHOST, request: “GET
/gerbentest/?delimiter=%2F&max-keys=1000&am
nt end and I have the
>> backend with nginx some applications in php7 with mariadb, reviewing
>> the log I see a lot of errors like this:
>>
>> 2018/05/09 17:44:58 [error] 14633#14633: *1761 connect() failed (111:
>> Connection refused) while connecting to upstream,
or] 14633#14633: *1761 connect() failed (111:
> Connection refused) while connecting to upstream, client:
> 186.77.203.203, server: web.mydomain.com, request: "GET
> /imagenes/slide7.jpg HTTP/2.0", upstream:
> "http://192.168.11.7:80/imagenes/slide7.jpg"
hello list, I have a reverse proxy with nginx front end and I have the
backend with nginx some applications in php7 with mariadb, reviewing
the log I see a lot of errors like this:
2018/05/09 17:44:58 [error] 14633#14633: *1761 connect() failed (111:
Connection refused) while connecting to
Yeah, it was a network issue. tcpdump helped.
Thanks
> On Dec 18, 2017, at 1:39 PM, Francis Daly wrote:
>
> On Mon, Dec 18, 2017 at 01:31:57PM -0600, Joel Parker wrote:
>
> Hi there,
>
>> network connectivity, firewall, etc. are all configured correctly but still
>> having issues when trying
On Mon, Dec 18, 2017 at 01:31:57PM -0600, Joel Parker wrote:
Hi there,
> network connectivity, firewall, etc. are all configured correctly but still
> having issues when trying to hit the proxy. It's is very strange, since the
> ports are listening. I even turned off the firewall and the same iss
t; > curl http://172.31.22.230/
> > curl: (7) Failed to connect to 172.31.22.228 port 80: Connection refused
>
> That suggests that the outside machine does not has network connectivity
> both to and from that IP address.
>
> Note that you have one address in the curl reque
ks
> curl 172.31.22.230 -works when running on the local machine
That suggests that the local machine has network connectivity to and
from that IP address.
> but when I try to run it from the outside, I get:
>
> curl http://172.31.22.230/
> curl: (7) Failed to connect to 172.31.22.228 por
port 80: Connection refused
I have made the config as simple as possible but have not figured out a way
to run
curl http://172.31.22.230 from another machine
Here is the config:
# cat nginx.conf
load_module modules/ndk_http_module.so;
load_module modules/ngx_http_lua_module.so;
user ec2-user ec2
decide do you want django to present itself as a uwsgi service,
or as a http service.
Then: configure django as the server, and configure nginx as the client
talking to that server.
> 2017/09/18 06:32:56 [error] 15451#0: *1 connect() to
> unix:home/workspace/project//
> tmp/uwsgi.s
nix sockets to http but still
> no joy .
>
> exact error
>
>
> 2017/09/18 06:32:56 [error] 15451#0: *1 connect() to
> unix:home/workspace/project//
> tmp/uwsgi.sock failed (111: Connection refused) while connecting to
> upstream, client: 1933
> .247.239.160, serve
access ) !!
I've checked over and over all the directory structures etc. Ive swtiched
from unix sockets to http but still
no joy .
exact error
2017/09/18 06:32:56 [error] 15451#0: *1 connect() to
unix:home/workspace/project//
tmp/uwsgi.sock failed (111: Connection refused) while conne
2 port 8080 (#0)
> * Trying 128.107.138.162...
> * Adding handle: conn: 0x7ffb9c003a00
> * Adding handle: send: 0
> * Adding handle: recv: 0
> * Curl_addHandleToPipeline: length: 1
> * - Conn 0 (0x7ffb9c003a00) send_pipe: 1, recv_pipe: 0
> * Failed connect to 128.107.138.162:
(0x7ffb9c003a00) send_pipe: 1, recv_pipe: 0
* Failed connect to 128.107.138.162:8080; Connection refused
* Closing connection 0
curl: (7) Failed connect to 128.107.138.162:8080; Connection refused
Also, my curl command with the proxy set in the command is trying to
simulate how the real request is
On Mon, Feb 01, 2016 at 01:00:04AM +, Radha Venkatesh (radvenka) wrote:
Hi there,
> server {
> listen 127.107.138.162:8080;
> However, when I use the curl command to send a request using the proxy like
> this, I see a "Connection Refused"
&g
/rhesos/api/v1/ping;
}
}
}
However, when I use the curl command to send a request using the proxy like
this, I see a "Connection Refused"
curl -v -x 'http://:@128.107.138.162:8080'
http://10.154.181.43:8080/rhesos-server/rhesos/api/v1/ping
* About to connect() to p
Thanks Maxim, that explains it
Would be nice if documentation mentioned this fact, or nginx would spit out
some errors about the conflicting config ;)
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,257064,257107#msg-257107
___
nginx mailing l
Hello!
On Thu, Mar 05, 2015 at 09:58:37PM -0500, Fry-kun wrote:
> So it looks like the ssl config is valid per-port only. If I set up a server
> on a different port with different ssl config, it works.
> Is this a bug or is it by design?
This is by design. Before some protocol-specific handshak
"Connection refused", generally means that your server (sometimes this can
be a firewall too - although firewalls tend to more often just silently drop
packets) is sending a RST packet to an attempt to connect. Check with
netstat and see if Nginx is bound to your public IP on :443
A
So it looks like the ssl config is valid per-port only. If I set up a server
on a different port with different ssl config, it works.
Is this a bug or is it by design?
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,257064,257086#msg-257086
__
Also noticed that http-level config causes www.foo.com to show errors on
https://www.200please.com/
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,257064,257065#msg-257065
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailma
starts freezing up randomly after a few
seconds -- though sometimes comes back for a short while.
curl from outside reports error as "connection refused"; using curl
localhost:443 responds properly with "* SSL: no alternative certificate
subject name matches target host name 'l
Hello!
On Mon, Dec 15, 2014 at 12:28:39PM -0500, jurerickporras wrote:
> i have the same problem . how to fix this please help
As already explained in this thread, the "fix" is to make sure the
response is in cache. If it's there, nginx will return it once
configured to do so.
--
Maxim Doun
i have the same problem . how to fix this please help
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,255408,255502#msg-255502
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
After adding the following:
proxy_cache_valid 200 302 301 10m;
It appears to be working. It's unclear to me why:
proxy_cache_valid any 10m;
Wasn't working, for me.
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,255408,255441#msg-255441
__
Thanks, I've tried this. My amended configuration is below. However, I'm
still getting the same error when the upstream goes away. The cache
directory is now being populated correctly however. Any ideas?
--
user www-data;
worker_processes 4;
pid /run/nginx.pid;
events {
worker_co
Hello!
On Wed, Dec 10, 2014 at 10:00:25PM -0500, new299 wrote:
> When the upstream goes away nginx gives the error "502 Bad Gateway
> nginx/1.4.6 (Ubuntu)". The log contains:
>
> " [error] 2624#0: *48941 connect() failed (111: Connection refused) while
> connec
On Wed, Dec 10, 2014 at 11:45:26AM -0500, new299 wrote:
> Hi,
>
> I'm using nginx as a reverse proxy, but I can't get nginx to serve requests
> from its cache when the upstream server is refusing connections. I
> understood that "proxy_cache_use_stale error" should allow me to do this,
> but it do
When the upstream goes away nginx gives the error "502 Bad Gateway
nginx/1.4.6 (Ubuntu)". The log contains:
" [error] 2624#0: *48941 connect() failed (111: Connection refused) while
connecting to upstream,"
Rather than serving it from cache as I would expect. It should be ca
Hello!
On Wed, Dec 10, 2014 at 11:45:26AM -0500, new299 wrote:
> I'm using nginx as a reverse proxy, but I can't get nginx to serve requests
> from its cache when the upstream server is refusing connections. I
> understood that "proxy_cache_use_stale error" should allow me to do this,
> but it do
/nginx-proxy-cache-use-stale-not-working-when-connection-refused
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,255408,255408#msg-255408
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
37 matches
Mail list logo
