Plesk 12.x / Linux :: Each Website In Separate Directory
Dec 15, 2014
I just started using plesk for my blogs and websites, so testing and finding my way around i notice every site i add instead of having its own folder just like in cpanel(shared hosting) the sites are been added under the primary domain.
My family is getting into the blogging business and they want to be hosted together to share costs. What features should I look for in hosting 4 or 5 small but growing blogs?
Info that may help you give a recomendation:I plan to have a separate url for each blog's root directory.
I plan to use wordpress.
I want each site to have it's own email addresses.
I've got a situation in which I need to have a set of mail accounts that share a domain name with a domain that's already in use as a domain alias and because the domain is already in use, I'm unable to create a new account using that domain. I tried explicitly adding "www" to the domain alias so I could keep the www.domain.com address as an alias and reserve the "domain.com" name for use as a separate account, but Plesk won't allow for that.
How to address this? The idea I'm currently considering is to delete the domain alias and then create the new account and manually set the DOCUMENT ROOT of the new account to refer to the other domain's document root. I'm sure this could create some difficulty in Plesk so I'm looking for input before trying it. I'm actually not even sure exactly where I would be able to redefine the document root with Plesk allowing the change and not overwriting it later.
If all else fails, I can setup a new account on a different and unrelated Plesk server, but I'd prefer not to do that.
How to connect nginx to work with directory web_users for some virtual host?
This directory contains two accounts (user1, user2) with a large amount of static content (files .jpg), the downloaded web users themselves. At the moment they are processed by Apache, which causes an additional load on the server.
In hosting configuration for virtual host "domain.tld" set:
document root: httpdocs. (That is, the "httpdocs" and "web_users" directories are on the same level).
In the web server configuration settings (in additional nginx directives) i can't use the directive "server" (refuses to save), where you can specify the location of the additional "document root" for nginx.
Initially I was able to connect via FTP. Then all of a sudden I started getting 550 SSL/TLS required on the control channel. Why did it suddenly required SSL/TLS when I did not do anything extra?
Now when I'm trying to connect via FTPES using FileZilla (tried both active and passive) on Linux Mint Debian, I'm getting the error below. I'm really stumped. I have tried to Allow incoming from all on port 49152-65534/tcp via Plesk firewall, but still no go.
The worst thing now is, I can't even get FTP to work anymore. Of course I would prefer to have TLS working.
Status:Connection established, waiting for welcome message... Response:220 ProFTPD 1.3.5 Server (ProFTPD) [206.106.213.243] Command:AUTH TLS
I normally protect a given directory in the Plesk Contral Panel with a Username / Password. I would like to bypass the username and password for visitors from one IP.
would do the trick, but no go, nginx isnt passing it to apache by the looks of it. I tried all kinds of possible solutions but cant get it to work. It works with files though. The logfile says directory index of "/var/www/vhosts/testdomain.eu/httpdocs/wp-admin/" is forbidden. This makes sense, since its turned off.
My /var/www/vhosts/system directory was accidentally deleted. The actual vhost directories are unharmed, e.g. /var/www/vhosts/example.com. Is there a non-destructive script I can run to re-initialize the system directory? I am on Plesk 11.5.30.
There is a directory say, "Master" and inside, "Master" there is sub-directory, "Slave". A user who has access to, "Master" should be able to access, "Slave" automatically. However, a user who has access to, "Slave" should not have access to, "Master". Inside cPanel this type of protection is not possible.
I'm migrating sites from Plesk 9 to Plesk 12 using the migration manager. Since the migration manager doesn't migrate backups, are the backups compatible between Plesk 9 and Plesk 12? If so, is there an easy way to copy the backups in the correct directory structure since we are forced to use clients in plesk 12 and it changes the directory structure of the backups folders.
i'm running the latest version of Plesk 11 on a Ubuntu 12.04 system.
We have a customer with a domain and this customer added other domains to his account.
now, 2 domains are not working, he created the as usual, Plesk created the directories under /vhosts/domain.com/domain1.com and the vhosts.conf are also correct.
when i'm opening the domain in the browser, i get the following error message:
The requested URL /var/www/vhosts/domain.com/index.php was not found on this server.
Which protocol I should use for performing a backup of important server files and folders. I do make a snapshot but i found that's not enough.
My Centos 6.6 has ProFTPD configuration setup only for webhosts so no root access. I came across SCP, but don't know how to secure that like a Pro. I have also heard about SSHFS for linux.
Today I try to fit all FW rules to my need. After i blocked the traffic "allow other incoming traffic" in the Plesk FW i dont get folders listed via FTP. The FTP client connect to my server, but listing content times out. After allow other traffic the content get listed. The rule "Allow FTP connections" ist in all enabled all the time.
I enabled plesk firewall to my ip now I cant seem retrieve directory listing. I've done the same with ssh that works fine.
Response:230 User logged in Command:OPTS UTF8 ON Response:200 UTF8 set to on Status:Connected Status:Retrieving directory listing... Command:PWD Response:257 "/" is the current directory Command:TYPE I Response:200 Type set to I Command:PASV Response:227 Entering Passive Mode Command:MLSD Error:Connection timed out Error:Failed to retrieve directory listing
I'm setting up a SAAS service which is built on top of Laravel. To put it simply the service itself knows whether its being called from a sub.example.com or just example.com and serves a correct response accordingly. So going to sub.example.com will use the same index.php file as example.com but the routes and controllers within the application will provide a different response. sub.example.com will show a tenant login page where as example.com will show a new tenant subscription page or something else.
So when someone new subscribes I add a new entry to the database with a subdomain name for them and when a request comes from that subdomain and they are logged in it will show them their information. Easy right.
There is a problem though with setting it up with Plesk. When I add a wildcard subdomain, it will look for /subdomains/sub/ for the files which is a bit problematic since I want it to serve the files from the same place as the domain example.com.
Is there a way to configure that so that regardless of the subdomain it will try and serve the exact same content as my main domain?