{"id":15214,"date":"2025-07-11T18:35:42","date_gmt":"2025-07-11T13:05:42","guid":{"rendered":"https:\/\/www.skynats.com\/?p=15214"},"modified":"2025-07-11T18:35:44","modified_gmt":"2025-07-11T13:05:44","slug":"how-to-fix-ftp-service-failure-in-plesk-with-ipv6-disabled","status":"publish","type":"post","link":"https:\/\/www.skynats.com\/blog\/how-to-fix-ftp-service-failure-in-plesk-with-ipv6-disabled\/","title":{"rendered":"How to Fix FTP Service Failure in Plesk with IPv6 Disabled"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">If you&#8217;re running a Plesk server on <a href=\"https:\/\/www.linux.org\/\" target=\"_blank\" rel=\"noopener\"><mark style=\"background-color:rgba(0, 0, 0, 0)\" class=\"has-inline-color has-secondary-color\">Linux<\/mark><\/a> and have disabled IPv6, might encounter an issue where the FTP Service Failure in Plesk with IPv6 Disabled. This problem is triggered when the <strong>xinetd<\/strong> attempts to launch the FTP daemon using IPv6, despite the protocol being disabled system-wide.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">You might see the following error in your server logs (typically found in journalctl, \/var\/log\/messages, or systemctl status xinetd):<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>xinetd&#91;503]: socket creation failed (Address family not supported by protocol (errno = 97)). service = ftp\nxinetd&#91;503]: Service ftp failed to start and is deactivated.<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The FTP service remains inactive, rendering you unable to connect via FTP.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The issue is due to xinetd attempting to bind the FTP service using the IPv6 address family. If IPv6 is disabled at the kernel level, this fails with error 97, <strong>\u201cAddress family not supported by protocol\u201d<\/strong>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading has-small-font-size\"><strong>Resolution: Force xinetd to Use IPv4<\/strong><\/h2>\n\n\n\n<h3 class=\"wp-block-heading has-small-font-size\"><strong>Step 1: Connect to your server via SSH<\/strong><\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>ssh root@server-ip<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading has-small-font-size\"><strong>Step 2: Edit the FTP service configuration<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Open the \/etc\/xinetd.d\/ftp_psa file with your preferred text editor. Example using vim editor:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>vim \/etc\/xinetd.d\/ftp_psa<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Look for this line:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>flags = IPv6<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Replace it with:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>flags = IPv4<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Your updated configuration should look like this:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>service ftp\n{\n        flags           = IPv4\n        disable         = no\n        socket_type     = stream\n        protocol        = tcp\n        wait            = no\n        user            = root\n        instances       = UNLIMITED\n        server          = \/usr\/sbin\/in.proftpd\n        server_args     = -c \/etc\/proftpd.conf\n}<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">This file may be overwritten during a future Plesk update, so you might want to create a script or automation to reapply this fix if needed.<\/p>\n\n\n\n<h3 class=\"wp-block-heading has-small-font-size\"><strong>Step 3: Restart the xinetd service<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">After saving the changes, restart xinetd to apply them:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>systemctl start xinetd<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">To verify it&#8217;s running:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>systemctl status xinetd<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">If everything is configured correctly, the FTP service should now be active and accepting connections over IPv4.<\/p>\n\n\n\n<h2 class=\"wp-block-heading has-small-font-size\"><strong>Conclusion<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">While disabling IPv6 can improve security or simplify networking in certain environments, it can cause compatibility issues like FTP Service Failure in Plesk with IPv6 Disabled when services expect IPv6 support by default. By explicitly telling xinetd to use IPv4, you ensure your FTP service continues to work even with IPv6 turned off.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Need expert help fixing FTP service failures on your Plesk server with IPv6 disabled? Contact Skynats today for reliable <a href=\"https:\/\/www.skynats.com\/plesk-server-management\/ \">Plesk Server Management Services<\/a> and fast support!<\/p>\n","protected":false},"excerpt":{"rendered":"<p>If you&#8217;re running a Plesk server on Linux and have disabled IPv6, might encounter an issue where the FTP Service Failure in Plesk with IPv6 Disabled. This problem is triggered when the xinetd attempts to launch the FTP daemon using IPv6, despite the protocol being disabled system-wide. You might see the following error in your [&hellip;]<\/p>\n","protected":false},"author":14,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5],"tags":[1062,1004,1063],"class_list":["post-15214","post","type-post","status-publish","format-standard","hentry","category-blog","tag-ftp-service-failure-in-plesk-with-ipv6-disabled","tag-plesk-server-management-services","tag-xinetd"],"_links":{"self":[{"href":"https:\/\/www.skynats.com\/blog\/wp-json\/wp\/v2\/posts\/15214","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.skynats.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.skynats.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.skynats.com\/blog\/wp-json\/wp\/v2\/users\/14"}],"replies":[{"embeddable":true,"href":"https:\/\/www.skynats.com\/blog\/wp-json\/wp\/v2\/comments?post=15214"}],"version-history":[{"count":2,"href":"https:\/\/www.skynats.com\/blog\/wp-json\/wp\/v2\/posts\/15214\/revisions"}],"predecessor-version":[{"id":15216,"href":"https:\/\/www.skynats.com\/blog\/wp-json\/wp\/v2\/posts\/15214\/revisions\/15216"}],"wp:attachment":[{"href":"https:\/\/www.skynats.com\/blog\/wp-json\/wp\/v2\/media?parent=15214"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.skynats.com\/blog\/wp-json\/wp\/v2\/categories?post=15214"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.skynats.com\/blog\/wp-json\/wp\/v2\/tags?post=15214"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}