• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue Bad code format by adding IPv4 over Plesk Panel

Dukemaster

Regular Pleskian
Hi Plesk developers,
Now I reproduced this error for several times during the last weeks. By adding new IPv4 over IP Pool of Plesk Panel the new code is pasted directly behind the last letter of existing code of /etc/network/interfaces ...Please look.
The result is failure by:
systemctl status networking.service
and / or
/etc/init.d/networking restart
Note: After I corrected the configuration of all 3 additional IPv4 the last two weeks, they immediately ran successful without failure.

This is the real code of my interfaces file after adding the last IPv4 yesterday.
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eth0
iface eth0 inet static
address 217.160.92.49
netmask 255.255.255.255
gateway 10.255.255.1
pointopoint 10.255.255.1

auto eth0:1
iface eth0:1 inet static
address 217.160.167.167
netmask 255.255.255.255

auto eth0:2
iface eth0:2 inet static
address 217.160.130.142
netmask 255.255.255.255iface eth0:3 inet static
address 212.227.254.115
netmask 255.255.255.255
auto eth0:3

I wonder why the standard IPv6 is in the extra file "ipv6" of /interfaces.d/ directory. But that's unimportant.

Lots of greets
 
Last edited:
Hi Dukemaster,

such issues appear, if you manually edited the file "/etc/network/interfaces", without adding a space/tab and a new line AFTER your manual edits... so it's a user mistake. :(

I wonder why the standard IPv6 is in the extra file "ipv6" of /interfaces.d/ directory. But that's unimportant.
Pls. add more informations to this statement, as it is unclear, WHAT you mean with it and what your ( possible ) issues/errors/problems you experience. In addition, pls. note, that this might be unrelated to your thread title, which could irritate other forum users. :(
 
Back
Top