Learn how to fix the “Mount.nfs4 connection timed out “ error. Our NFS Support team is here to help you with your questions and concerns.

Mount.nfs4 connection timed out Error | Fixed

If you have been running into the following error, you have come to the right place.

mount.nfs4: Connection timed out

This error pops up when we try to mount an Amazon Elastic File System on the EC2 instance.

Fortunately, our experts have your back. With the right troubleshooting steps, we can get EFS mounted and the workflow back on track.

Today, we will take a look at the common causes of this error and solutions.

In fact, the error usually occurs when there is a problem establishing a connection between the EC2 instance and the EFS file system. This may be due to misconfigurations in security groups, subnets, or network interfaces.

Solution: Configuring Security Groups

1. To begin with, create a new security group for the EC2 instance. Make sure to allow inbound access for ports like SSH (22), HTTP (80), and HTTPS (443). Optionally, restrict the source address.
2. Then, create another security group for the EFS mount. Add an inbound rule for NFS, allowing TCP traffic on port 2049 from the EC2 security group we created in Step 1.
3. Now, in the EC2 console, add the EFS Mount security group to the EC2 instance. This ensures that the instance can receive inbound connections from the EFS Mount security group.
4. Next, in the EFS console, manage file system access by adding the EFS Mount security group to each mount target and removing the default security group. This allows communication between the EC2 instance and the EFS file system.

Additional Troubleshooting Steps

If you are still having trouble after configuring security groups, consider the following:

• Make sure the subnets associated with the EFS file system allow traffic to the target systems. Add rules to allow all traffic or specific traffic based on the needs.
• Then, double-check the mount command syntax and path. Sometimes, using “/” as the path instead of a specific directory can resolve connectivity issues.
• Next, confirm that the network interfaces associated with the EFS mount targets have the correct security group rules, particularly for TCP port 2049.

Let us know in the comments if you need further help with the error.

[Need assistance with a different issue? Our team is available 24/7.]

Conclusion

In brief, our Support Experts demonstrated how to fix the “ Mount.nfs4 connection timed out” error.