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

"unable to resolve host address" running wget as chroot user

jerrac

New Pleskian
Server info: Plesk 11.5 on a Ubuntu 12.04 64bit server.

When I try to run a curl or wget command as my chooted user, it responds with an error saying it cannot resolve the host.

Ip addresses work.

I tried the steps mentioned in this post: http://talk.plesk.com/threads/scheduled-tasks-always-fail.331821/#post-775191

But it didn't help.

I also set the users shell to normal /bin/bash, and it worked. After setting it back to /bin/bash (chrooted) it stopped working.

This issue is preventing my user from setting up a needed cron job.

Any suggestions?
 
This seems like something a LOT of people would need. I certainly found plenty of posts on the subject of resolving dns entries from a chroot environment when I did a Google search. So, I would there would be workaround.

To me, I'd think that adding the correct files to the chroot environment would do it. But when I followed the instructions for that in the post I linked, it didn't work. So, did I miss some files? Or what?
 
Back
Top