Socket error 111 python

Generally, in python, the connection error is not something that you will face every day, but it can sometimes happen due to various reasons. One such reason is the connection Refuse. This causes the generation of ConnectionRefusedError errno 111 connection refused message. If you are facing this error message in your coding, this might help you.

What is socket error?

A socket programming in python is used to form a bidirectional communications channel. It is generally a process of making the two unrelated network nodes communicate with each other by making a connection. This connection can be made if you know the IP address of the server.

What is ConnectionError?

Whether you are someone new to the python language or not, you must be aware of the term connection error. As suggested by the name, it is a class of exception errors related to the errors generated due to issues in the connection. It is a type of socket error that is observed in many other libraries and platforms.

In python, the ConnectionError is generally referred to as an error generated by the failure in any of the internal connections that are the connection between the application and the DBMS server mediating a peer. This type of error can be caused by various failures, such as local errors caused by the errors reported directly to the user interface programs, then local and remote errors caused while trying to connect from the local communication server to the remote communication server and the server installation. These ConnectionErrors also report directly to the applications.

Types Of ConnectionError

There are mainly three subclasses of ConnectionError such as ConnectionAbortedError, ConnectionResetError, and ConnectionRefusedError. These errors generally arise when the error is raised due to the attempt the interruption in connection with the actions of peers.

The ConnectionRefusedError errno 111 connection refused is a subclass of the ConnectionError which is caused when the peer refuses the attempts for the connection between the application and the server. This type of error corresponds to errno ECONNREFUSED messages.

The ConnectionRefusedError errno 111 connection refused is generated when the initial SYN packet to the host to be connected was responded with an RST packet instead of a SYN+ACK packet. This resulted in the declination of the program on the remote computer that needed to be connected.

This type of error can cause by many libraries and computing platforms, but the solutions to this problem are similar.

The generation of the error can be understood efficiently by using an example:

As the connection has to be made from both end so it is done in two parts:

The Server script:

The client script:

These codes might seem good, but this will result in the socket.error: [Errno 111] Connection refused message.

How to solve the ConnectionRefusedError errno 111 connection refused?

As this is a connection-based error, so the errors have to be checked on both ends that is, on the client and the server end. The ConnectionRefusedError errno 111 connection refused can be resolved using one of the following reasons.

Checking the connection

• Ensure the IP address is of the client, and both servers are on the same LAN. If the servers are not on the same router or firewall, then you may face traffic blocking.
• Make sure that the port is listening to the server and if not then try “netstat -ntulp”.
• Make sure that you are accepting the connections to the server.
• Make sure you have access to the port server of the client.

Selectively restrict the listening socket

In the example for the generation of the ConnectionRefusedError by the server you can see that there is a line as follows:

host = socket.gethostname() #Get the local machine name
port = 98406 # Reserve a port for your service
s.bind((host,port)) #Bind to the port

Instead of the above code, you can try:

port = 98406 # Reserve a port for your service
s.bind(('', port)) #Bind to the port

This way, the listening socket will not be too restricted and will ensure the connection precisely on both ends.

Proper guidance to get an IP address

To avoid ConnectionRefusedError errno 111 connection refused while coding you need to make sure to get the right IP address for that you have to put the hostname and port number for the receiver end correctly.

Due to DNS resolution, the hostname might not get translated into the local address and returned properly. So instead of the usual code:

host = socket.gethostname() #Get the local machine name
port = 98406 # Reserve a port for your service
s.bind((host,port)) #Bind to the port

You can try the code below.

host = socket.gethostbyname("localhost")
s.connect((host, port))

FAQ

How do you fix a socket error?

As the ConnectionRefusedError errno 111 connection refused is a type of socket error, resolving this may help in resolving the former error.

• This error can be fixed by specifying the port number for which you can use the following code:

m SimpleHTTPServer (Port Number)

• You can also free up the port by terminating the previous programs.

What is the socket address in computer networks?

The socket address is a crucial part of establishing the connection. It is generally a combination of two identifiers, that is both IP address and port number. It is defined in a header where it is specified by a data structure.

Conclusion

The ConnectionRefusedError errno 111 connection refused is a socket error that results when there is a failure in the establishment of connection when the connection is refused. Which can later be resolved by managing the data necessary for establishing the connection.

References

1. Dizzy coding
2. GeeksforGeeks socket programming

To learn more about some common errors follow python clear’s errors section.

1. Why the ConnectionRefusedError: [Errno 111] Connection refused Occurs in Python
2. How to Solve the ConnectionRefusedError: [Errno 111] Connection refused in Python
3. Conclusion

This error indicates that the client cannot connect to the port on the server script’s system. Since you can ping the server, it should not be the case.

This might be caused by many reasons, such as improper routing to the destination. The second possibility is that you have a firewall between your client and server, which may be either on the server or the client.

There shouldn’t be any routers or firewalls that may stop the communication since, based on your network addresses, both the server and the client should be on the same Local Area Network.

Why the ConnectionRefusedError: [Errno 111] Connection refused Occurs in Python

This error arises when the client cannot access the server because of an invalid IP or port or if the address is not unique and used by another server.

The connection refused error also arises when the server is not running, so the client cannot access the server as the server should accept the connection first.

Code example:

# server code
import socket

s = socket.socket()
host = socket.gethostname()
port = 1717
s.bind((host, port))

s.listen(5)
while True:
    c,addr = s.accept()
    print("Got connection ", addr)
    c.send("Meeting is at 10am")
    c.close()

# client code
import socket

s = socket.socket()
host = '192.168.1.2'
port = 1717

s.connect((host,port))
print(s.recv(1024))
s.close

Output:

socket.error: [Errno 111] Connection refused

How to Solve the ConnectionRefusedError: [Errno 111] Connection refused in Python

Try to keep the receiving socket as accessible as possible. Perhaps accessibility would only take place on one interface, which would not impact the Local Area Network.

On the other hand, one case can be that it exclusively listens to the address 127.0.0.1, making connections from other hosts impossible.

Code example:

import socket

s = socket.socket()
host = socket.gethostname()
port = 1717
s.bind(('', port))

s.listen(5)
while True:
    c,addr = s.accept()
    print("Got connection ", addr)
    c.send("The Meeting is at 10 am")
    c.close()

import socket

s = socket.socket()
host = socket.gethostname()
port = 1717
s.bind(('', port))

s.connect((host, port))
print(s.recv(1024))
s.close()

Output:

Got connection('192.168.1.2')
The meeting is at 10 am

When you run the command python server.py, you will receive the message Got connection. At the same time when you run the command python client.py, you will receive a message from the server.

The DNS resolution can be the other reason behind this problem. Since the socket.gethostname() returns the hostname, an error will be returned if the operating system cannot translate it to a local address.

The Linux operating system can edit the host file by adding one line.

host = socket.gethostname()
port = 1717
s.bind((host,port))

Use gethostbyname

host = socket.gethostbyname("192.168.1.2")
s.bind((host, port))

Thus, you must use the identical technique on the client and server sides to access the host. For instance, you would apply the procedure described above in a client’s case.

You can also access through local hostname hostnamehost = socket.gethostname() or specific name for local host host = socket.gethostbyname("localhost").

host = socket.gethostname()
s.connect((host, port))

host = socket.gethostbyname("localhost")
s.connect((host, port))

Conclusion

ConnectionRefusedError in Python arises when the client cannot connect to the server. Several reasons include the client not knowing the IP or port address and the server not running when the client wants to connect.

There are several methods mentioned above to resolve this connection issue.

ConnectionRefusedError: [Errno 111] Connection Refused

This error indicates that the client cannot connect to the port on the server script’s system. Since you can ping the server, it should not be the case.

This might be caused by many reasons, such as improper routing to the destination. The second possibility is that you have a firewall between your client and server, which may be either on the server or the client.

There shouldn’t be any routers or firewalls that may stop the communication since, based on your network addresses, both the server and the client should be on the same Local Area Network.

Why the ConnectionRefusedError: [Errno 111] Connection refused Occurs in Python

This error arises when the client cannot access the server because of an invalid IP or port or if the address is not unique and used by another server.

The connection refused error also arises when the server is not running, so the client cannot access the server as the server should accept the connection first.

How to Solve the ConnectionRefusedError: [Errno 111] Connection refused in Python

Try to keep the receiving socket as accessible as possible. Perhaps accessibility would only take place on one interface, which would not impact the Local Area Network.

On the other hand, one case can be that it exclusively listens to the address 127.0.0.1 , making connections from other hosts impossible.

When you run the command python server.py , you will receive the message Got connection . At the same time when you run the command python client.py , you will receive a message from the server.

The DNS resolution can be the other reason behind this problem. Since the socket.gethostname() returns the hostname, an error will be returned if the operating system cannot translate it to a local address.

The Linux operating system can edit the host file by adding one line.

Use gethostbyname

Thus, you must use the identical technique on the client and server sides to access the host. For instance, you would apply the procedure described above in a client’s case.

You can also access through local hostname hostnamehost = socket.gethostname() or specific name for local host host = socket.gethostbyname(«localhost») .

Conclusion

ConnectionRefusedError in Python arises when the client cannot connect to the server. Several reasons include the client not knowing the IP or port address and the server not running when the client wants to connect.

There are several methods mentioned above to resolve this connection issue.

Zeeshan is a detail oriented software engineer that helps companies and individuals make their lives and easier with software solutions.

Источник

«socket.error: [Errno 111] Connection refused» while training on ADE20K #215

I am getting following error after few data iteration @ 551/22210:

File «train.py», line 201, in
trainer.training(epoch)
File «train.py», line 142, in training
for i, (data, target) in enumerate(tbar):
File «/usr/local/lib/python2.7/dist-packages/tqdm/_tqdm.py», line 930, in iter
for obj in iterable:
File «/usr/local/lib/python2.7/dist-packages/mxnet/gluon/data/dataloader.py», line 222, in next
return self.next()
File «/usr/local/lib/python2.7/dist-packages/mxnet/gluon/data/dataloader.py», line 218, in next
idx, batch = self._data_queue.get()
File «/usr/lib/python2.7/multiprocessing/queues.py», line 117, in get
res = self._recv()
File «/usr/local/lib/python2.7/dist-packages/mxnet/gluon/data/dataloader.py», line 88, in recv
return pickle.loads(buf)
File «/usr/lib/python2.7/pickle.py», line 1388, in loads
return Unpickler(file).load()
File «/usr/lib/python2.7/pickle.py», line 864, in load
dispatchkey
File «/usr/lib/python2.7/pickle.py», line 1139, in load_reduce
value = func(*args)
File «/usr/local/lib/python2.7/dist-packages/mxnet/gluon/data/dataloader.py», line 53, in rebuild_ndarray
fd = multiprocessing.reduction.rebuild_handle(fd)
File «/usr/lib/python2.7/multiprocessing/reduction.py», line 156, in rebuild_handle
conn = Client(address, authkey=current_process().authkey)
File «/usr/lib/python2.7/multiprocessing/connection.py», line 169, in Client
c = SocketClient(address)
File «/usr/lib/python2.7/multiprocessing/connection.py», line 308, in SocketClient
s.connect(address)
File «/usr/lib/python2.7/socket.py», line 228, in meth
return getattr(self._sock,name)(*args)
socket.error: [Errno 111] Connection refused

I am using latest nightly of MXNET along with Sync BatchNorm, This error comes with and without SyncBatchNorm layer.

I am using MXNET docker

Any help is much appreciated.

The text was updated successfully, but these errors were encountered:

Источник

ConnectionRefusedError: [Errno 111] Connection refused

I get «connection refused 111» when trying to communicate over sockets in Python. When the connection is refused, THE LISTENER STOPS LISTENING. Same problem occurs using import of multiprocessing.connection, socket, zeromq.

My feeling is that the link between Python and the OS/network doesn’t work. However the NC and socket commands issued in a ubuntu terminal can communicate over the same port.

Notwithstanding the inconvenience it’s causing me, there is obviously a severe security risk if an invalid connection request causes a socket to stop listening. Ideal for denial of service attacks.

I have two programs:

When I start the listener (f5 in IDLE), it seems to start ok.

and the socket starts listening:

ss -lt

State Recv-Q Send-Q Local Address:Port Peer Address:Port Process

LISTEN 0 1 192.168.1.100:16001 0.0.0.0:*

However, when I start the client (f5 in IDLE) I get this:

and the listening socket disappears.

ss -lt

State Recv-Q Send-Q Local Address:Port Peer Address:Port Process

LISTEN 0 5 127.0.0.1:ipp 0.0.0.0:* LISTEN 0 1 127.0.0.1:36093
0.0.0.0:*
LISTEN 0 5 [::1]:ipp [::]:*

Ive tried changing port numbers, setting FW rules, IP addresses from hard-coded to «localhost», . remote client (on Windows) etc etc. Nothing works although symptoms vary.

Ive tried programming the connection using the «socket import» and have exactly the same results. zeromq doesn’t work either.

However the NC and socket commands issued in a terminal can communicate over the same port.

fwiw Im running Ubuntu 20.04.2 LTS. Apart from the one client I tried on windows, all testing is done on a single ubuntu system. Its a fairly new install, so its unlikely I’ve broken something.

Please can someone tell me what I’m doing wrong?

My feeling is that the link between Python and the OS/network doesn’t work.

Notwithstanding the inconvenience it’s causing me, there is obviously a severe security risk if an invalid connection request causes a socket to stop listening. Ideal for denial of service attacks.

1 Answer 1

I couldn’t reproduce your issue, thus not sure what’s the problem. But, some remarks.

I added a simple ping-pong exchange to your code:

and also changed the listening address to one from the link-local subnet 127.0.0.0/8 .

Then simply using 2 terminal tabs/windows, run t2.py then t1.py 3 times:

The server process continues to run, as expected. The client tab:

Please pay attention. You may think these things you named are the same — but they are significantly different:

multiprocessing.connection, socket, zeromq.

The python-builtin import socket module is direct translation of the classic BSD sockets API. The «sockets API» is what defines such things as: port, listening on a port, connecting to a port, accepting a connection, send , recv , close and a few more functions. A book on network programming may help (e.g. this one as a random example — I don’t endorse it). The sockets API is almost 40 years old, so you’ll also easily find free learning materials online.

Next, import multiprocessing module. It’s a completely different story. It provides helpers for multi-process Python programs. Those create multiple PIDs and can run on multiple processor cores. Almost certainly you’ll want these processes to talk to each other to do useful work. This is where sockets come handy: since processes are isolated by OS from each other, network provides a way to build that communication (even if it’s localhost-only). The sub-module multiprocessing.connection provides ergonomic helpers exactly for that.

Next, ØMQ is altogether a separate project (it’s not python-builtin; neither it’s python-specific). It does something interesting; it redefines another «socket API». ØMQ socket ≠ BSD socket. Zeromq sockets can do things which BSD sockets can’t (pub/sub, fanout, app-level routing). Zeromq sockets are built «on top of» BSD sockets; if you have troubles with the lower-level API, I would recommend to approach ZMQ only after you get comfortable with bare basic sockets.

Nothing works although symptoms vary.

Again, you should get comfortable with interpreting network failure modes. The raised error codes have precisely defined meanings. For example, the classic Connection refused errno 111 means that the initial SYN packet to the host you connect() to was responded with an RST packet instead of the normal SYN+ACK — which usually happens when there’s no program listening to the given port on the remote computer you connect() to.

One more remark with regards to your security concerns. You should always assume that the network is adversarial (hostile), regardless if it’s indeed true at that point in space & time — even the localhost network. This is why the higher-level multiprocessing API has the authkey parameter; it’s practically always needed. The password bytestring is one of the worst values for authkey imaginable, try something better. An active network adversary could, theoretically, explain your issue; there’s something called «RST injection attack». You might’ve simply exhausted the listen backlog/SOMAXCONN, too.

Источник

socket.error: [Errno 111] Connection refused [JIRA: CLIENTS-41] #375

I am using RIAK Python client for my project and RIAK amazon instance.I got this error while running my project and its related to RIAK instance.My error log is :-
Traceback (most recent call last):
File «ironjob/ai/index.py», line 36, in application
returnval = mManager.process(api)
File «ironjob/ai/ironMainManager.py», line 94, in process
return self.mUserManager.process(listitem)
File «ironjob/ai/ironUserManager.py», line 27, in process
return self.userVerification(listitem)
File «ironjob/ai/ironUserManager.py», line 62, in userVerification
self.mCacheManager.addData(BUCKET_AI, datadict[KEY_SESSID], sessionData, cacheStart=1, cacheEnd=3, timeout=60)
File «ironjob/ai/ironCacheManager.py», line 55, in addData
self.mRiakClient.addData(bucket, key, dataVals, nestedKey=innerKey, timeout=timeout)
File «ironjob/ai/ironRiakClient.py», line 53, in addData
currentData = <> if bucket.get(key).get_data() == None else bucket.get(key).get_data()
File «build/bdist.linux-x86_64/egg/riak/bucket.py», line 326, in get
File «build/bdist.linux-x86_64/egg/riak/riak_object.py», line 459, in reload
File «build/bdist.linux-x86_64/egg/riak/transports/pbc.py», line 251, in get
File «build/bdist.linux-x86_64/egg/riak/transports/feature_detect.py», line 76, in quorum_controls
File «build/bdist.linux-x86_64/egg/riak/util.py», line 61, in get
File «build/bdist.linux-x86_64/egg/riak/transports/feature_detect.py», line 95, in server_version
File «build/bdist.linux-x86_64/egg/riak/transports/pbc.py», line 178, in _server_version
File «build/bdist.linux-x86_64/egg/riak/transports/pbc.py», line 206, in get_server_info
File «build/bdist.linux-x86_64/egg/riak/transports/pbc.py», line 528, in send_msg_code
File «build/bdist.linux-x86_64/egg/riak/transports/pbc.py», line 559, in send_pkt
File «build/bdist.linux-x86_64/egg/riak/transports/pbc.py», line 113, in maybe_connect
File «build/bdist.linux-x86_64/egg/riak/transports/connection.py», line 166, in maybe_connect

File «», line 1, in connect
socket.error: [Errno 111] Connection refused

Please help me out.Thanks in advance.

The text was updated successfully, but these errors were encountered:

Connection refused means exactly what it says. Whatever port you tried to connect to, the Riak server is not listening on or is otherwise inaccessible. Possible causes/solutions:

Источник

connect() failed (111: Connection refused) while connecting to upstream

I’m experiencing 502 Gateway errors when accessing a PHP file in a directory ( http://example.com/dev/index.php ). The logs simply says this:

I’ve never experienced this before. What is the solution for this type of 502 Gateway error?

This is the nginx.conf :

8 Answers 8

It sounds like you haven’t started and configured the backend for Nginx. Start php-fpm and add the following to nginx.conf , in the http context:

This answer is only for those who get an error like this:

connect() failed (111: Connection refused) while connecting to upstream, client . fastcgi://[::1]:9000

Rewrite your nginx config to use ip, not dns. For instance, 127.0.0.1 instead of localhost , or remove the ipv6 alias from /etc/hosts.

Got errors like this too. Problem was my abstract backend referencing two servers. php-fpm was only listing to socket.

Had the same problem with proxied requests to a Node server listening on port 5000. Requests would result with 200 OK but sometime 502 Bad Gateway randomly. NGINX showed the error:

1. Set node HTTP server to listen strictly for ipv4 by including localhost as host: server.listen(5000, ‘localhost’);
2. Removed any ipv6 listen directives ( listen [::]:80; or listen [::]:443 ssl default_server; ).
3. Changed location block proxy_pass to use IPs: proxy_pass http://127.0.0.1:5000 (not proxy_pass http://localhost:5000 ).

Hope this helps someone.

In my case the error was a bad location for the error_log file for php5.6-fpm service and thus the php-fpm service was failing to start and nginx was not able to connect to it. You can find it in /etc/php/5.6/fpm/php.ini (you can replace 5.6 with the version you are running).

Same problem has occured for me and finally I found firewalld was blocking required ports after installation and I was missing to open ports in firewall (port 9000 in your logs).

Just in case somebody is deperately trying to fix their problem just to realize there is nothing wrong with their reverse proxy setup:

In my case, the error persisted even after I’ve removed all location directives but a single one that only provides static content.

The error message was caused because Nginx wasn’t able to log it’s log to the syslog server:

Summary:

If you are using a syslog log server, make sure it is available. To test whether the error originates from the logging setup, comment out all logging configs so that Nginx falls back to the native logging scheme.

I hope this saves some people time debugging a fully valid reverse proxy config, just to fid the error somewhere else 😀

Источник

ConnectionRefusedError: [Errno 111] Connection Refused

This error indicates that the client cannot connect to the port on the server script’s system. Since you can ping the server, it should not be the case.

This might be caused by many reasons, such as improper routing to the destination. The second possibility is that you have a firewall between your client and server, which may be either on the server or the client.

There shouldn’t be any routers or firewalls that may stop the communication since, based on your network addresses, both the server and the client should be on the same Local Area Network.

Why the ConnectionRefusedError: [Errno 111] Connection refused Occurs in Python

This error arises when the client cannot access the server because of an invalid IP or port or if the address is not unique and used by another server.

The connection refused error also arises when the server is not running, so the client cannot access the server as the server should accept the connection first.

How to Solve the ConnectionRefusedError: [Errno 111] Connection refused in Python

Try to keep the receiving socket as accessible as possible. Perhaps accessibility would only take place on one interface, which would not impact the Local Area Network.

On the other hand, one case can be that it exclusively listens to the address 127.0.0.1 , making connections from other hosts impossible.

When you run the command python server.py , you will receive the message Got connection . At the same time when you run the command python client.py , you will receive a message from the server.

The DNS resolution can be the other reason behind this problem. Since the socket.gethostname() returns the hostname, an error will be returned if the operating system cannot translate it to a local address.

The Linux operating system can edit the host file by adding one line.

Use gethostbyname

Thus, you must use the identical technique on the client and server sides to access the host. For instance, you would apply the procedure described above in a client’s case.

You can also access through local hostname hostnamehost = socket.gethostname() or specific name for local host host = socket.gethostbyname(«localhost») .

Conclusion

ConnectionRefusedError in Python arises when the client cannot connect to the server. Several reasons include the client not knowing the IP or port address and the server not running when the client wants to connect.

There are several methods mentioned above to resolve this connection issue.

Zeeshan is a detail oriented software engineer that helps companies and individuals make their lives and easier with software solutions.

Источник

Python-сообщество

Уведомления

#1 Авг. 9, 2014 15:05:26

socket.error: [Errno 111] Connection refused

Добрый день, помогите решить проблему, сижу я на лиyeксе ubuntu-13.10-x86, работает скрипт постоянно и почему то периодически выскакивает вот такая ошибка, я не могу понять в чем проблема, при этом скрипт иногда оживает почему то сам, иногда помогает перезагрузка сервера, могли бы новичку помочь решить этот вопрос, спасибо:

File “./test.py”, line 135, in
main()
File “./test.py”, line 114, in main
s.connect((args, opts.port))
File “/usr/lib/python2.7/socket.py”, line 224, in meth
return getattr(self._sock,name)(*args)
socket.error: Connection refused
Traceback (most recent call last):
File “./test.py”, line 135, in
main()
File “./test.py”, line 114, in main
s.connect((args, opts.port))
File “/usr/lib/python2.7/socket.py”, line 224, in meth
return getattr(self._sock,name)(*args)
socket.error: Connection refused
Traceback (most recent call last):
File “./test.py”, line 135, in
main()
File “./test.py”, line 114, in main
s.connect((args, opts.port))
File “/usr/lib/python2.7/socket.py”, line 224, in meth
return getattr(self._sock,name)(*args)
socket.error: Connection refused

#2 Авг. 9, 2014 15:06:45

socket.error: [Errno 111] Connection refused

паралельно на другом сервере этот же скрипт работает сейчас, но спустя какое то время будет тоже ругаться….

#3 Авг. 11, 2014 03:14:23

socket.error: [Errno 111] Connection refused

Если поможете мне, то я помогу вам.
Я вчера потерял 100 гривен, скажите где они? я их даже не искал, мне лень. решил сразу же на форум написать, ведь здесь все экстрасенсы! буду очень благодарный.

Надеюсь вы поняли что я хотел этим сказать?!

#4 Авг. 11, 2014 09:22:31

socket.error: [Errno 111] Connection refused

terabayt
Если поможете мне, то я помогу вам.Я вчера потерял 100 гривен, скажите где они? я их даже не искал, мне лень. решил сразу же на форум написать, ведь здесь все экстрасенсы! буду очень благодарный.Надеюсь вы поняли что я хотел этим сказать?!

Это значит, что я пошёл искать 100 грн!

#5 Авг. 11, 2014 12:39:54

socket.error: [Errno 111] Connection refused

Добрый день, noob_saibot
отправил вам личное сообщение с кодом,

#6 Авг. 11, 2014 13:26:02

socket.error: [Errno 111] Connection refused

STEVENSW
отправил вам личное сообщение с кодом,

#7 Авг. 11, 2014 14:31:35

socket.error: [Errno 111] Connection refused

Отредактировано noob_saibot (Авг. 11, 2014 14:32:04)

#8 Авг. 11, 2014 23:18:19

socket.error: [Errno 111] Connection refused

Добрый вечер, ну кто мне сможет объяснить проблему, сервак перегружаю вроде как работать начинает, а потом опять такая же проблема…. Может айпи менять…

Источник

socket.error: [Errno 111] Connection refused [JIRA: CLIENTS-41] #375

Comments

riteshbabu commented Oct 17, 2014

I am using RIAK Python client for my project and RIAK amazon instance.I got this error while running my project and its related to RIAK instance.My error log is :-
Traceback (most recent call last):
File «ironjob/ai/index.py», line 36, in application
returnval = mManager.process(api)
File «ironjob/ai/ironMainManager.py», line 94, in process
return self.mUserManager.process(listitem)
File «ironjob/ai/ironUserManager.py», line 27, in process
return self.userVerification(listitem)
File «ironjob/ai/ironUserManager.py», line 62, in userVerification
self.mCacheManager.addData(BUCKET_AI, datadict[KEY_SESSID], sessionData, cacheStart=1, cacheEnd=3, timeout=60)
File «ironjob/ai/ironCacheManager.py», line 55, in addData
self.mRiakClient.addData(bucket, key, dataVals, nestedKey=innerKey, timeout=timeout)
File «ironjob/ai/ironRiakClient.py», line 53, in addData
currentData = <> if bucket.get(key).get_data() == None else bucket.get(key).get_data()
File «build/bdist.linux-x86_64/egg/riak/bucket.py», line 326, in get
File «build/bdist.linux-x86_64/egg/riak/riak_object.py», line 459, in reload
File «build/bdist.linux-x86_64/egg/riak/transports/pbc.py», line 251, in get
File «build/bdist.linux-x86_64/egg/riak/transports/feature_detect.py», line 76, in quorum_controls
File «build/bdist.linux-x86_64/egg/riak/util.py», line 61, in get
File «build/bdist.linux-x86_64/egg/riak/transports/feature_detect.py», line 95, in server_version
File «build/bdist.linux-x86_64/egg/riak/transports/pbc.py», line 178, in _server_version
File «build/bdist.linux-x86_64/egg/riak/transports/pbc.py», line 206, in get_server_info
File «build/bdist.linux-x86_64/egg/riak/transports/pbc.py», line 528, in send_msg_code
File «build/bdist.linux-x86_64/egg/riak/transports/pbc.py», line 559, in send_pkt
File «build/bdist.linux-x86_64/egg/riak/transports/pbc.py», line 113, in maybe_connect
File «build/bdist.linux-x86_64/egg/riak/transports/connection.py», line 166, in maybe_connect

File «», line 1, in connect
socket.error: [Errno 111] Connection refused

Please help me out.Thanks in advance.

The text was updated successfully, but these errors were encountered:

Источник

Forums

[Errno 111] Connection refused

I am totally new at Django and while using its ‘send_mail’ function, I get this error: [Errno 111] Connection refused I think that’s the issue with the firewall.

Our firewall shouldn’t block anything like that going out from PythonAnywhere. What do you have in the email server settings (like EMAIL_HOST and EMAIL_USE_TLS) in your settings.py?

settings.py doesn’t have anything related to email. The default email host is set as ‘localhost’.’EMAIL_USE_TLS’ is set as ‘false’. I am using: send_mail(data[‘subject’],data[‘message’],data[’email’], [‘myemail@**.com’])

Ah, right. We don’t provide an SMTP server right now (it would make it too easy for spammers to use us), so you’ll need to specify one in EMAIL_HOST. Do you have access to one that you can use?

Oh.I will use my own. Thank you.

Hi I have the same problem, but I don’t have access to an SMTP server -any suggestions appreciated. Preferably free 🙂 I’d only need to send a very low volume

@signalstrength You can use Gmail’s SMTP server. I searched for you and found: http://www.jangosmtp.com/Pricing.asp If you can provide convincing reason for mailing(testing?), I could share my SMTP server.

As Aatishnn said the easiest public SMTP server to use would probably be gmail’s. You can configure it to accept emails from addresses other than your own. Good instructions are here: http://support.google.com/mail/bin/answer.py?hl=en&answer=22370

@aatishnn ah great thanks I’ll try Gmail. jangosmtp.com also looks interesting. I’d just be using it to experiment and for learning purposes, wouldn’t ask to share anyone’s for such things! Thanks again

Hi, I’m getting the same exception, I didn’t setup or change any mail settings, but I’m making calls to the twitter API.

You’ll need to setup your email settings then! If you still get issues then please post the full traceback from your error logs. You need to specify mail settings for Django. It has no way of knowing how you want to send email.

@hansel, I’m not trying to send emails and I probably won’t need it to do so soon, do I still need to setup email settings?

Here’s the traceback:

File «/usr/local/lib/python2.7/site-packages/django/core/handlers/base.py» in get_response 111. response = callback(request, callback_args, *callback_kwargs)

File «/home/iahvector/twitterWebApp/TwitterWebApp/twitterApp/views.py» in index 26. resp, content = client.request(settings.REQUEST_TOKEN_URL, «GET»)

File «/usr/local/lib/python2.7/site-packages/oauth2/init.py» in request 682. connection_type=connection_type)

File «/usr/local/lib/python2.7/site-packages/httplib2/init.py» in request 1597. (response, content) = self._request(conn, authority, uri, request_uri, method, body, headers, redirections, cachekey)

File «/usr/local/lib/python2.7/site-packages/httplib2/init.py» in _request 1345. (response, content) = self._conn_request(conn, request_uri, method, body, headers)

File «/usr/local/lib/python2.7/site-packages/httplib2/init.py» in _conn_request 1281. conn.connect()

File «/usr/local/lib/python2.7/site-packages/httplib2/init.py» in connect 1052. raise socket.error, msg

Exception Type: error at / Exception Value: [Errno 111] Connection refused

Ah okay, so you are getting an error when trying to connect to some kind of twitter API? The problem the original poster had was a problem sending email.

Though having visited your web app I’m not sure that it is actually your problem. Check the error logs of your web app and see what’s happening there. It’s a misconfigured django app. Start by fixing the problem in the error logs and see what comes up then. Your problem isn’t related to this one at all.

OK, I’m sorry, I’ll start a new post with my problem.

I’m getting the same error ([Errno 111] Connection refused) when trying to send emails using the gmx SMTP server.

Yup, that’s because you have a free account. Free accounts only have HTTP/S access to the outside Internet, and only to a set of whitelisted sites. They also have access to the Gmail mail servers. But they can’t access other mail servers, which is why you’re getting that error.

So, what account I should have to use non-whitelist API? Is it enough the Hack account?

So, what account I should have to use non-whitelist API? Is it enough the Hack account?

Yes, all paying accounts have unrestricted internet. Let us know if everything works OK?

Yes, it is OK. Thanks, harry.

Thanks for working for poor people. We have more restrictions but thanks anyway. I’ve being uploading code and trying it for hours now with less bandwith than what you have on any of your phones just to realize that I can’t connect to what I need to use cause I have a free account. Well, I guess I’m back to openshift.

We’re always happy to add new sites to the whitelist, if they have an official public API?

I’m trying to connect to webmail.nauta.cu and all the mail servers on nauta.cu. Is there any motive you should make a white list? I mean I love this site but it is unconfortable on a free account. All the other hosting services I have found only reduce bandwith o server storage and memory but you have to be connected over ssh wich I can’t use. I find the web consoles an all the enviroment really nice. I can do my work, push it to github and then pull it from the console. Almost like Im on my pc, but limitations are killing me and I can’t afford even the cheapest of your offers cause I don’t even have a credit card. (I would love to pay if I had that money)

Drop us an email? Maybe there’s something we can do.

send_mail(email, massage, send_from, send_to, fail_silently=False) Traceback (most recent call last): File «/home/Misha1986/.virtualenvs/env/lib/python3.5/site-packages/django/core/management/commands/shell.py», line 69, in handle self.run_shell(shell=options[‘interface’]) File «/home/Misha1986/.virtualenvs/env/lib/python3.5/site-packages/django/core/management/commands/shell.py», line 61, in run_shell raise ImportError ImportError During handling of the above exception, another exception occurred: Traceback (most recent call last): File » «, line 1, in File «/home/Misha1986/.virtualenvs/env/lib/python3.5/site-packages/django/core/mail/init.py», line 61, in send_mail return mail.send() File «/home/Misha1986/.virtualenvs/env/lib/python3.5/site-packages/django/core/mail/message.py», line 292, in send return self.get_connection(fail_silently).send_messages([self]) File «/home/Misha1986/.virtualenvs/env/lib/python3.5/site-packages/django/core/mail/backends/smtp.py», line 100, in send_messages new_conn_created = self.open() File «/home/Misha1986/.virtualenvs/env/lib/python3.5/site-packages/django/core/mail/backends/smtp.py», line 58, in open self.connection = connection_class(self.host, self.port, **connection_params) File «/usr/lib/python3.5/smtplib.py», line 251, in init (code, msg) = self.connect(host, port) File «/usr/lib/python3.5/smtplib.py», line 335, in connect self.sock = self._get_socket(host, port, self.timeout) File «/usr/lib/python3.5/smtplib.py», line 306, in _get_socket self.source_address) File «/usr/lib/python3.5/socket.py», line 711, in create_connection raise err File «/usr/lib/python3.5/socket.py», line 702, in create_connection sock.connect(sa) ConnectionRefusedError: [Errno 111] Connection refused

I cannot send mail.

Dang, wish I had seen this 5 days ago. ;-(

Couldn’t understand why only gmail was working.

🙁 Still, glad you found it eventually!

Hello pythonanywhere! Is there the possiblity to put in the whitelist smtp-relay.sendinblue.com for free account? My problem with smtp.gmail.com is about google block the request from pythonanywhere. Thanks in advance!

It won’t matter if it’s on the whitelist, since gmail is the only place that you can send SMTP to. If sendinblue have an http interface for mail sending, we can whitelist that. Just send us a link to the API documentation that shows the endpoint for the API.

Hello python anywhere i am having the following error

when trying to send an email Am an using a free account and the smtp connection is sendgrid kindly help as i need solution to this

For free accounts we only allow gmail smtp. You would have to upgrade to make smtp connections to other endpoints.

Am having this exception , am using lives plan

pls i need help

[edited by admin: formatting]

what was the command that you were trying to run? if you recently upgraded, have you killed and restarted your consoles?

Источник

@shexbeer

PS: Do you have Philips cloud enabled?

Yes, I have Philips cloud enabled

PPS: What happens if you send a command like —pw 0 or / —pw 1 ?

sudo ./airctrl.py  --ipaddr 192.168.1.37 --protocol coap -d --pw 0
2020-02-03 17:27:02,202 - MainThread - coapthon.layers.messagelayer - DEBUG - send_request - From None, To ('192.168.1.37', 5683), None-None, EMPTY-None, [] No payload
2020-02-03 17:27:02,203 - MainThread - coapthon.client.coap - DEBUG - send_datagram - From None, To ('192.168.1.37', 5683), CON-19242, EMPTY-None, [] No payload
2020-02-03 17:27:02,203 - Thread-1   - coapthon.client.coap - DEBUG - Start receiver Thread
2020-02-03 17:27:02,203 - MainThread - coapthon.layers.messagelayer - DEBUG - send_request - From None, To ('192.168.1.37', 5683), None-None, POST-NF, [Uri-Path: sys, Uri-Path: dev, Uri-Path: control, ] {"state": {"desired"...36 bytes
2020-02-03 17:27:02,204 - MainThread - coapthon.client.coap - DEBUG - send_datagram - From None, To ('192.168.1.37', 5683), CON-19243, POST-NF, [Uri-Path: sys, Uri-Path: dev, Uri-Path: control, ] {"state": {"desired"...36 bytes
2020-02-03 17:27:02,204 - MainThread-Retry-19242 - coapthon.client.coap - DEBUG - retransmit loop ... enter
2020-02-03 17:27:02,204 - MainThread-Retry-19243 - coapthon.client.coap - DEBUG - retransmit loop ... enter
2020-02-03 17:27:02,210 - Thread-1   - coapthon.layers.messagelayer - DEBUG - receive_empty - From ('192.168.1.37', 5683), To None, RST-19242, EMPTY-None, [] No payload
2020-02-03 17:27:02,211 - MainThread-Retry-19242 - coapthon.client.coap - DEBUG - retransmit loop ... exit
2020-02-03 17:27:02,212 - Thread-1   - coapthon.client.coap - DEBUG - receive_datagram - From ('192.168.1.37', 5683), To None, NON-19243, CONTENT-NF, [Content-Type: 50, ] {"status":"failed"}...19 bytes
2020-02-03 17:27:02,212 - Thread-1   - coapthon.layers.messagelayer - DEBUG - receive_response - From ('192.168.1.37', 5683), To None, NON-19243, CONTENT-NF, [Content-Type: 50, ] {"status":"failed"}...19 bytes
2020-02-03 17:27:02,212 - Thread-1   - coapthon.client.coap - DEBUG - Waiting for retransmit thread to finish ...
2020-02-03 17:27:02,212 - MainThread-Retry-19243 - coapthon.client.coap - DEBUG - retransmit loop ... exit
2020-02-03 17:27:02,323 - Thread-1   - coapthon.client.coap - DEBUG - Exiting receiver Thread due to request

sudo ./airctrl.py  --ipaddr 192.168.1.37 --protocol coap -d --pw 1
2020-02-03 17:27:09,106 - MainThread - coapthon.layers.messagelayer - DEBUG - send_request - From None, To ('192.168.1.37', 5683), None-None, EMPTY-None, [] No payload
2020-02-03 17:27:09,106 - MainThread - coapthon.client.coap - DEBUG - send_datagram - From None, To ('192.168.1.37', 5683), CON-52185, EMPTY-None, [] No payload
2020-02-03 17:27:09,107 - Thread-1   - coapthon.client.coap - DEBUG - Start receiver Thread
2020-02-03 17:27:09,107 - MainThread - coapthon.layers.messagelayer - DEBUG - send_request - From None, To ('192.168.1.37', 5683), None-None, POST-CQ, [Uri-Path: sys, Uri-Path: dev, Uri-Path: control, ] {"state": {"desired"...36 bytes
2020-02-03 17:27:09,107 - MainThread-Retry-52185 - coapthon.client.coap - DEBUG - retransmit loop ... enter
2020-02-03 17:27:09,107 - MainThread - coapthon.client.coap - DEBUG - send_datagram - From None, To ('192.168.1.37', 5683), CON-52186, POST-CQ, [Uri-Path: sys, Uri-Path: dev, Uri-Path: control, ] {"state": {"desired"...36 bytes
2020-02-03 17:27:09,108 - MainThread-Retry-52186 - coapthon.client.coap - DEBUG - retransmit loop ... enter
2020-02-03 17:27:09,109 - Thread-1   - coapthon.layers.messagelayer - DEBUG - receive_empty - From ('192.168.1.37', 5683), To None, RST-52185, EMPTY-None, [] No payload
2020-02-03 17:27:09,109 - MainThread-Retry-52185 - coapthon.client.coap - DEBUG - retransmit loop ... exit
2020-02-03 17:27:09,111 - Thread-1   - coapthon.client.coap - DEBUG - receive_datagram - From ('192.168.1.37', 5683), To None, NON-52186, CONTENT-CQ, [Content-Type: 50, ] {"status":"failed"}...19 bytes
2020-02-03 17:27:09,111 - Thread-1   - coapthon.layers.messagelayer - DEBUG - receive_response - From ('192.168.1.37', 5683), To None, NON-52186, CONTENT-CQ, [Content-Type: 50, ] {"status":"failed"}...19 bytes
2020-02-03 17:27:09,112 - Thread-1   - coapthon.client.coap - DEBUG - Waiting for retransmit thread to finish ...
2020-02-03 17:27:09,112 - MainThread-Retry-52186 - coapthon.client.coap - DEBUG - retransmit loop ... exit
2020-02-03 17:27:09,222 - Thread-1   - coapthon.client.coap - DEBUG - Exiting receiver Thread due to request

PPS: After having second look onto your pcap file, it looks like your app/device sends different coap messages than mine does. Also i saw in your pcap that your device is using firmware 1.4 and mine use 0.2.1. When did you buy your device? Did you connect it to Cloud, did any OTA? (for comparison: I bought my device on Monday from Amazon, never connected to Cloud, never did OTA)

I bought my AC3829/10 on Amazon in November and connected to it using the Air Matters app from my Android phone. I’ve never confirmed any updates, but it’s possible that it’s running in the background.

PPPS: After taking a look into your responses from GET /sys/dev/status, it looks like the json response may be encrypted. Mine is plain

Yes, it looks like CoAP over TLS. I signed out of the Phillips account on Air Matters and tried to capture the communication again according to the recommended procedure:

1. Start capturing from mobile device
2. Open App
3. Click on Device
4. Set ChildLock On/Off + Power On/Off
5. Stop Capturing from mobile device

purifier-coap_tls.pcap.zip

I couldn’t reproduce your issue, thus not sure what’s the problem. But, some remarks.

I added a simple ping-pong exchange to your code:

# t2.py

from multiprocessing.connection import Listener

listener = Listener(('127.0.5.1', 16001), authkey=b'password')
print ("listener ready", listener)
running = True
while running :
    print ("ready to connect")
    conn = listener.accept()
    print('connection accepted from', listener.last_accepted)
    msg = conn.recv()
    print(f"received: {msg}")
    conn.send(b"PONG")

# t1.py

from multiprocessing.connection import Client
address = ('127.0.5.1', 16001)            
conn = Client(address, authkey = b'password')        
conn.send(b"PING")
print(conn.recv())

and also changed the listening address to one from the link-local subnet 127.0.0.0/8.

Then simply using 2 terminal tabs/windows, run t2.py then t1.py 3 times:

$ python t2.py
listener ready <multiprocessing.connection.Listener object at 0x7fb115c18a00>
ready to connect
connection accepted from ('127.0.0.1', 36702)
received: b'PING'
ready to connect
connection accepted from ('127.0.0.1', 36704)
received: b'PING'
ready to connect
connection accepted from ('127.0.0.1', 36706)
received: b'PING'
ready to connect

The server process continues to run, as expected. The client tab:

$ python t1.py
b'PONG'
$ python t1.py
b'PONG'
$ python t1.py
b'PONG'

Please pay attention… You may think these things you named are the same — but they are significantly different:

multiprocessing.connection, socket, zeromq.

The python-builtin import socket module is direct translation of the classic BSD sockets API. The «sockets API» is what defines such things as: port, listening on a port, connecting to a port, accepting a connection, send, recv, close and a few more functions. A book on network programming may help (e.g. this one as a random example — I don’t endorse it). The sockets API is almost 40 years old, so you’ll also easily find free learning materials online.

Next, import multiprocessing module. It’s a completely different story. It provides helpers for multi-process Python programs. Those create multiple PIDs and can run on multiple processor cores. Almost certainly you’ll want these processes to talk to each other to do useful work. This is where sockets come handy: since processes are isolated by OS from each other, network provides a way to build that communication (even if it’s localhost-only). The sub-module multiprocessing.connection provides ergonomic helpers exactly for that.

Next, ØMQ is altogether a separate project (it’s not python-builtin; neither it’s python-specific). It does something interesting; it redefines another «socket API». ØMQ socket ≠ BSD socket. Zeromq sockets can do things which BSD sockets can’t (pub/sub, fanout, app-level routing). Zeromq sockets are built «on top of» BSD sockets; if you have troubles with the lower-level API, I would recommend to approach ZMQ only after you get comfortable with bare basic sockets.

Nothing works although symptoms vary.

Again, you should get comfortable with interpreting network failure modes. The raised error codes have precisely defined meanings. For example, the classic Connection refused errno 111 means that the initial SYN packet to the host you connect() to was responded with an RST packet instead of the normal SYN+ACK — which usually happens when there’s no program listening to the given port on the remote computer you connect() to.

One more remark with regards to your security concerns. You should always assume that the network is adversarial (hostile), regardless if it’s indeed true at that point in space & time — even the localhost network. This is why the higher-level multiprocessing API has the authkey parameter; it’s practically always needed. The password bytestring is one of the worst values for authkey imaginable, try something better. An active network adversary could, theoretically, explain your issue; there’s something called «RST injection attack». You might’ve simply exhausted the listen backlog/SOMAXCONN, too.

Lastly, Wireshark is a wonderful tool.