Howdy,
Well, you seem to be going a bit against the grain in regards to how Virtualmin works.
I’d highly recommend not making any changes in Webmin – but instead, to find a way to work with Virtualmin’s workflow.
By default, Virtualmin places websites and user accounts in /home.
That’s because it configures suexec and related tools to run out of /home. Using suexec provides security advantages, since code isn’t running as the Apache user, but instead runs as the account owner.
So if you try to work around Virtualmin, and make Apache run the site out of /var/www – things won’t actually work properly for you.
My recommendation then is to migrate your site to work within /home/USERNAME.
I dont have permission to even look in the new folder virtualmin created for the new domain. Its made that folder owned by the new name of the domain I guess when I created it, and it wont let you navigate there unless I guess if you login via FTP as that new user
That’s correct – a new top-level Virtual Server would setup the files so that they’re only visible to users of that Virtual Server.
To most folks, that’s considered a feature
I would recommend using a user of that Virtual Server though in order to upload files.
Also, since suexec is being used, it would cause problems if you attempted to use a different user to modify files.
That said, if you really need to do some file management and copy files from their current location to this user’s directory – you could always use a tool like WinSCP to log in over SSH as root, and copy the files that way. But after doing so, be sure to change the ownership of the files to that of the Virtual Server owner.
-Eric