RE: Reseller accounts using their own dedicated IP to setup name-based accounts etc..
1) NameVirtualHost &ip&:80 is not added to the Apache configuration, hence causing all name-based accounts setup on the reseller IP to point to the reseller's main account rather than the correct name-based account.
2) Other name-based accounts can not FTP to the server, because ftp.&namebasedaccount&.com is pointed to the reseller IP by default. However when you FTP to the reseller IP and use the credentials of a name-based accounts it doesnt authenticate. You have to FTP into the main server IP, which defeats the point of using a dedicated reseller IP.
When can we get a fix? (a real fix this time) - would like to lol but this aint funny. Why release a feature that doesnt work correctly?:p
1) NameVirtualHost &ip&:80 is not added to the Apache configuration, hence causing all name-based accounts setup on the reseller IP to point to the reseller's main account rather than the correct name-based account.
2) Other name-based accounts can not FTP to the server, because ftp.&namebasedaccount&.com is pointed to the reseller IP by default. However when you FTP to the reseller IP and use the credentials of a name-based accounts it doesnt authenticate. You have to FTP into the main server IP, which defeats the point of using a dedicated reseller IP.
When can we get a fix? (a real fix this time) - would like to lol but this aint funny. Why release a feature that doesnt work correctly?:p