Messages

1

CentOS-WebPanel Bugs / Re: After update or script update, my conf files of vhosts al revert to default

« on: January 27, 2022, 12:39:32 PM »

Since this "feature" was released, I have been migrating, one by one, all the domains and subdomains in my server to the recommended "template configuration". It seemed to work. Until today  . I found all the sites suspended again. No matter which template the site has, all of them suspended. Every site has a template matching its configuration. The template is correct. CWP shows the domain with its associated template. Nevertheless, all domains and subdomains are "suspended", no matter what. It looks as what drajvat is reporting.

The real solution is to stop this "feature". It is not reliable. As a software development concept, as a system behavior, it is horrible. This is pure speculation, but it looks like a hack that hides other issues. Maybe design problems too deep for the CWP team to solve without big efforts and time. I only see this kind of solutions as a "give me time to fix it" strategy. However, it is taking too long.

If there is no way for CWP to stop the "vhosts rebuild" process, I can only do some scripting to save new domains and restore periodically. I don't want to do this. It is a workaround to handle a not working hack. The best solution is to remove or disable the hack.

What can I do? What other users of CWP did?

Thank you for your help.

2

CentOS-WebPanel Bugs / Re: After update or script update, my conf files of vhosts al revert to default

« on: January 07, 2022, 12:36:22 PM »

I have extra information that forgot to add.

In the CWP installation that we use, when a new domain is added, it uses a default configuration for webserver in vhosts. That default configuration leaves the new domain working without issues. At night, that same configuration is overriden by the "rebuild vhosts" script, using the "suspended" template. I'm not sure, but it looks like there is a bug somewhere. If a website is added through CWP, and this website is running when finished, it shouldn't be disabled when this "vhosts rebuild" takes place at night.

Thanks for your help.

3

CentOS-WebPanel Bugs / Re: After update or script update, my conf files of vhosts al revert to default

« on: January 07, 2022, 10:23:46 AM »

The CWP dashboard now rebuilds all sites daily.
This means that if you have any previous customizations, you cannot do them directly in the Apache server configuration files.
You must create the customizations only in cloned template files for this purpose.
You did it?
What types of customization have you done?

Hello Netino,

Sorry the delay. I'm not the one who add domains to CWP, and I don't know exactly whats the procedure that my partners follow. I tried yesterday to edit a domain using the "select template" method, and it seems that the nightly rebuild keep the changes and the site is still working.

To summarize (please, correct me if I misunderstand): I have to create a template for every site that has a configuration detail. For example, if I don't want to have webmail support for a site, I have to create a template for that. If a site should not have "AllowOverride All", it is necessary to create a template for that. And so on. Like seati pointed before, it is necessary to have a template for every difference that a site has with another site in the same server. Right? So when CWP does the automatic vhosts rebuild, the sites keep up and running.

I have hundreds of domains in the server. It will be a lot of work and testing to create a template for each one. Is there any workaround? Can this rebuild process be stopped or masked somehow? Is it possible to protect the configurations until we move to the "template" method?

Thank you for your help.

4

CentOS-WebPanel Bugs / Re: After update or script update, my conf files of vhosts al revert to default

« on: January 05, 2022, 10:36:01 AM »

Hello everyone,

I'm following all the threads reporting this issue (vhosts overwritten with default values, page suspended) since Dec 30. For my server, the overwritting happens at 3:00 am, so fifteen minutes later, a cron job restore vhosts/ from backup and reload apache to recover the websites.
However, I was specting a better/more formal solution, maybe a patch, coming from the CWP team. All the solutions proposed in the forum are hacks, not real solutions. If I'm missing something, the proper solution, can anyone please point me what's the correct fix for this problem?

Thanks in advance :-)