• 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.

Resolved Bug: Plesk NAT - IP Reset via command line does not work because plesk things the ip does not exist.

Talistech

Basic Pleskian
Username:

TITLE

Bug: Plesk NAT - IP Reset via command line does not work because plesk things the ip does not exist.

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

Server operating system version Ubuntu 22.04.4 LTS
Plesk version and microupdate number Plesk Obsidian 18.0.62 Update #2

PROBLEM DESCRIPTION

Hi there,

I have found a bug while updating DNS records via the CLI.
You are able to update the dns records to the "internal" ip address while using NAT. But you cannot use the external/public address because Plesk thinks that that address does not exist.

Thanks,

Kind regards,
Talistech

STEPS TO REPRODUCE

Bash:
root@server:~# plesk bin subscription --update example.com -ip 99.99.99.99 # Example with public address
An error occurred during domain update: An error occurred during changing of hosting settings: Unable to set IP address for hosting: IP address '99.99.99.99' does not exist

exit status 1


root@server:~# plesk bin subscription --update example.com -ip 10.26.2.102 # Example with local address
SUCCESS: Update of domain 'example.com' completed.

ACTUAL RESULT

Bash:
root@server:~# plesk bin subscription --update example.com -ip 10.26.2.102 # Example with local address
SUCCESS: Update of domain 'example.com' completed.

EXPECTED RESULT

Bash:
root@server:~# plesk bin subscription --update example.com -ip 99.99.99.99 # Example with public address
An error occurred during domain update: An error occurred during changing of hosting settings: Unable to set IP address for hosting: IP address '99.99.99.99' does not exist

exit status 1

ANY ADDITIONAL INFORMATION

(DID NOT ANSWER QUESTION)

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug
 
Back
Top