Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
tried removing SElenux enforcement - no difference. I'm in a real bind now, I had the system going to the default page at least, now it's just locking me out completely.
quick update - it now goes to the Apache set up page, i.e a default holding page once again, not to the correct folder. grrr.
Since dns is working again, but you can't do the vhost migration, I suggest you to create those vhosts from scratch. It's not a big deal to create the configuration for 3-4 vhosts.
well, you say that but it should not have been a big deal to create one - I removed the site in question and recreated it from scratch, and got the errors as described. I really don't want to risk removing sites which are currently working perfectly well, to have them do the same thing.
No need to remove sites
You just recreate the vhosts in apache config and point their DocumentRoot to the DocumentRoot that was setup previously in plesk
You can run
yes, I understand that I just have to remove the sites config in Apache, but I already tried this for the existing site and created a new one, and it goes to the default page. I am pretty sure that if I do that with any of the (currently working) sites, I will end up with the same problem, meaning I have double trouble.
I'll look at the Apache error log and try that command.
ok I found some entries in these files and pointed the system to the httpd.conf file in the conf folder, and it now goes to the correct site - however, when I FTP to the site it goes to the wrong location! ah, what a tangled web. I think I can fix that particular issue though.
I repointed the user to the correct directory but now I just get a lot of time outs on the FTP connection. Makes no sense!
Please note that timeouts usually mean some network or firewall problem. So check your ftp server settings (about active or passive ftp), as well as your firewall rules.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.