How to Connect a Socket in Python

What a socket does and why you need one

A socket in Python is an object that lets your program send and receive data over a network — either to another program on your computer or to a server across the internet. Think of it like a telephone jack: you plug it in, establish a connection, and then you can talk back and forth. Python's socket module handles all the technical details of finding the other computer, negotiating the connection, and keeping the line open while you exchange information.

Most network programs you use every day — your web browser, email client, messaging app — rely on sockets behind the scenes. When you write Python code that needs to talk to a server or listen for incoming connections, you build that communication using sockets. The socket module is built into Python, so you do not need to install anything extra to get your free guide.

Key Takeaways

Import the socket module at the top of your Python file with import socket, then create a socket object using socket.socket().
Connect to a remote server using the connect() method with a tuple containing the hostname and port number, like my_socket.connect(("example.com", 80)).
Always close your socket when you are done with close() to free up system resources and prevent connection leaks.
Use try/except blocks to catch connection errors like timeouts or refused connections, which happen frequently in network programming.
Test your socket code with a known server first — like connecting to Google's DNS server on port 53 — before building more complex programs.

Import the socket module and create a socket object

Start by adding import socket at the very top of your Python file. This gives you access to all the socket functions and classes you need. Next, create a socket object by calling socket.socket(). The most common form looks like this:

my_socket = socket.socket(socket.AF_INET, socket.SOCK_STREAM)

This line does three things. socket.AF_INET tells Python you want to use the standard internet protocol (IPv4). socket.SOCK_STREAM tells Python you want a reliable, ordered connection — the kind used for web browsing and email. Together, these settings create a socket ready to connect to a remote server. You can name the variable anything you want; my_socket is just an example.

Connect to a server using the connect() method

Once you have a socket object, use the connect() method to reach another computer. The method takes one argument: a tuple with two pieces of information. The first is the hostname or IP address of the server you want to reach. The second is the port number — a number between 0 and 65535 that tells the server which service you want to talk to.

Here is a real example that connects to Google's public DNS server:

my_socket.connect(("8.8.8.8", 53))

Port 53 is the standard port for DNS queries. If you were connecting to a web server, you would use port 80 for unencrypted traffic or port 443 for encrypted (HTTPS) traffic. The hostname can be a domain name like "example.com" or an IP address like "93.184.216.34" — Python will look up the IP address for you if you use a domain name.

The connect() method blocks — meaning your program pauses and waits — until the connection succeeds or fails. This can take anywhere from a few milliseconds to several seconds depending on network speed and distance.

Handle connection errors with try and except

Network connections fail all the time. The server might be down, the hostname might not exist, the port might be closed, or your internet connection might drop. If you call connect() without protecting it, your program will crash when any of these things happen. Wrap your socket code in a try/except block to catch these errors gracefully:

try: my_socket = socket.socket(socket.AF_INET, socket.SOCK_STREAM) my_socket.connect(("example.com", 80)) print("Connected successfully") except socket.error as error: print(f"Connection failed: {error}")

The except socket.error line catches any socket-related error — connection refused, timeout, hostname not found, and many others. The as error part lets you store the error message in a variable so you can print it or log it. This tells you what actually went wrong, which is invaluable for debugging.

Common errors you will see include ConnectionRefusedError (the server is not listening on that port), TimeoutError (the connection took too long), and socket.gaierror (the hostname could not be resolved to an IP address).

Send and receive data through the socket

After connect() succeeds, you can send data to the server using the send() method and receive data using the recv() method. Both methods work with bytes, not strings, so you need to encode your text first:

my_socket.send(b"Hello, server")

The b prefix tells Python this is a byte string. If you have a regular string variable, encode it like this: my_socket.send(message.encode()). The recv() method takes one argument — the maximum number of bytes to read at once — and returns the data as bytes:

response = my_socket.recv(1024) print(response.decode())

This reads up to 1024 bytes from the server and then decodes them back into a readable string. If the server sends more than 1024 bytes, you need to call recv() multiple times in a loop to get all the data. If the server closes the connection, recv() returns an empty byte string.

Close the socket when you are finished

Always call close() on your socket when you are done with it. This tells the operating system to release the connection and free up the resources it was using:

my_socket.close()

If you do not close your sockets, your program will eventually run out of available connections and new sockets will fail to connect. This is called a connection leak. The best practice is to close the socket in a finally block so it closes even if an error occurs:

try: my_socket = socket.socket(socket.AF_INET, socket.SOCK_STREAM) my_socket.connect(("example.com", 80)) my_socket.send(b"GET / HTTP/1.1\r\nHost: example.com\r\n\r\n") response = my_socket.recv(1024) print(response.decode()) except socket.error as error: print(f"Error: {error}") finally: my_socket.close()

The finally block runs no matter what — whether the connection succeeded, failed, or raised an exception. This guarantees your socket gets closed.

Test your socket with a simple connection

Before you build a complex program, test your socket setup with a server you know works. Google's public DNS server at 8.8.8.8 on port 53 is a reliable target. Here is a complete working example:

import socket try: test_socket = socket.socket(socket.AF_INET, socket.SOCK_STREAM) test_socket.connect(("8.8.8.8", 53)) print("Connection successful") except socket.error as error: print(f"Connection failed: {error}") finally: test_socket.close()

Run this code. If you see "Connection successful", your socket setup is working. If you see an error, check that your internet connection is active and that your firewall is not blocking outbound connections. Once this simple test works, you can modify it to connect to the servers your actual program needs.

Frequently Asked Questions

What is the difference between AF_INET and AF_INET6?

AF_INET uses the older IPv4 protocol, which is still the most common. AF_INET6 uses the newer IPv6 protocol, which supports many more addresses but is not yet universal. For most programs, AF_INET is the right choice. Use AF_INET6 only if you know the server you are connecting to uses IPv6.

Why does my program hang when I call connect()?

The connect() method blocks until the connection succeeds or fails, which can take several seconds if the network is slow or the server is far away. If it seems to hang forever, the server is probably not responding. You can set a timeout with my_socket.settimeout(5) to make it fail after 5 seconds instead of waiting indefinitely.

Can I reuse a socket after calling close()?

No. Once you close a socket, it is done. If you need to connect again, create a new socket object with socket.socket(). Trying to use a closed socket will raise an error.

What does "Address already in use" mean?

This error usually appears when you are building a server (listening on a port) rather than a client (connecting to a port). It means another program is already using that port. Wait a minute or two for the operating system to release the port, or choose a different port number for testing.

How do I know what port to use when connecting?

The port depends on what service you are connecting to. Web servers use port 80 (HTTP) or 443 (HTTPS). Email servers use port 25, 587, or 993 depending on the type. DNS uses port 53. Check the documentation for the service you want to connect to — it will tell you the correct port.

This guide is for general information only and is not medical, financial, legal, or other professional advice. For decisions specific to your situation, consult a qualified professional. See our Editorial Policy.