Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: [1]
1
Backup / Re: New Backup [Beta] problems still not fixed
« on: August 02, 2020, 05:40:31 PM »
I have a similar problem. I added a new account the other day (normally I have just my own) and added some websites that took up about 1/2 gig of space. The next day I saw 25 gig of space get used, so I doubled the size of the drive. I then found today that the server had doubled in size again, and from being only 30 gig is now 80 gig.
The reason is the creation of the files in the backup directory under the
/ backup / weekly / user / backupcwp / directory.
My own sites are not being backuped like this, they only backup the code and are smaller.
What is the backupupcwp directory for? It has a tar file in it of 10 gig, and it is creating a new one in the daily backup, weekly backup and monthly backup. If I do not delete them they will take up 10gig x 7 in the daily backup alone, which is 3 times the size fo the rest of the server!
How do I stop it creating these backups, it never used to do this, and what are they for?
The reason is the creation of the files in the backup directory under the
/ backup / weekly / user / backupcwp / directory.
My own sites are not being backuped like this, they only backup the code and are smaller.
What is the backupupcwp directory for? It has a tar file in it of 10 gig, and it is creating a new one in the daily backup, weekly backup and monthly backup. If I do not delete them they will take up 10gig x 7 in the daily backup alone, which is 3 times the size fo the rest of the server!
How do I stop it creating these backups, it never used to do this, and what are they for?
2
Apache / Re: Default Page Displayed for all domains
« on: September 25, 2015, 06:09:09 AM »
I too faced this problem for hours and in my case it was so simple. In the CWP settings I had put in my public IP address. Put the one that it defaults to, probably 172.xxx.xxx.xxx and all was fixed. You will have to edit your user(s) too so they have this IP address, rebuild virtual hosts and for me anyway the web page was no longer the default one, but the one in the users public directory. I preferred to delete the user and add them again as the option for the 172...IP for users only appeared after I did
I have just looked back on all the posts in this thread and all the server IPs that are listed (many are not) are either public, or the one given to your PC by your routers (eg 192.xxx.xxx.xxx). Both of these will give the wretched default page for all your domains. There is a third IP to consider, the one that apache creates which is then shares, probably 172.....
So in my case
NS1: a.dxmx.com | IP:78.12.123.232 [Change] Public
NS2: b.dxmx.com | IP:78.12.123.232 [Change] Public
Server IP: 172.31.1.100 | CentOS-67-64-minimal apache IP
Shared IP: 172.31.1.100 [Change] apache IP
For those who have their machines on a router, and I am guessing here, you will need to forward the ports in the router to the 192.xxx of the machine hosting the webpanel, but that is a completely different issue.
In both cases all domains should point to single public IP address as set with your domain providor (the nameservers) and webpanel/apache will share an internal IP it made up all on its own.
BTW I took out all other suggestions in this thread on the basis that the I think the best config is the one the coders provided in the first place.
Hope this helps.
I have just looked back on all the posts in this thread and all the server IPs that are listed (many are not) are either public, or the one given to your PC by your routers (eg 192.xxx.xxx.xxx). Both of these will give the wretched default page for all your domains. There is a third IP to consider, the one that apache creates which is then shares, probably 172.....
So in my case
NS1: a.dxmx.com | IP:78.12.123.232 [Change] Public
NS2: b.dxmx.com | IP:78.12.123.232 [Change] Public
Server IP: 172.31.1.100 | CentOS-67-64-minimal apache IP
Shared IP: 172.31.1.100 [Change] apache IP
For those who have their machines on a router, and I am guessing here, you will need to forward the ports in the router to the 192.xxx of the machine hosting the webpanel, but that is a completely different issue.
In both cases all domains should point to single public IP address as set with your domain providor (the nameservers) and webpanel/apache will share an internal IP it made up all on its own.
BTW I took out all other suggestions in this thread on the basis that the I think the best config is the one the coders provided in the first place.
Hope this helps.
Pages: [1]
