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

Question Curl problem

Alberto Almagioni

New Pleskian
I have a problem with curl.
I set up a server with Debian 9 and Plesk 17 and I moved there a website.
In this site I’m using curl to call a web service on the same domain: something like https://dev.domain.tld calling https://dev.domain.tld/functions/services.php
On my previous server (not managed with plesk) everything was working.
Here curl doesn’t work.
After a lot of googling I find a workaround putting the local ip associated with the host name in /etc/hosts
Now everything is working so I guess is a routing problem but I can’t find a way to solve it.
The server is on a /24 network. I can ping the public ip of the server from server itself but I can’t navigate (lynx) the site without the trick of hosts file...
as this is a workaround and not a solution I’d like to understand how to solve but as I’m very “newbie” on Plesk, probably I set something wrong on the server.
Thank you
Alberto
 
Under Tools > IP Addresses - associated the Public IP to local internal IP then configure Plesk DNS for the website. This will allow websites to resolve internally without having to use /etc/hosts file. Your Scheduled Task - Fetch as URL or curl www.domain.com to resolve and execute.

Note that you will need to install the Plesk DNS extension.

The one downside of this is that internally, the website will resolve to external IP which can become an issues in some circumstances.
 
Back
Top