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
CentOS-WebPanel Bugs / Problem installing PostgreSQL and phpPgAdmin
« on: March 18, 2024, 06:35:05 PM »
Hi!
Im using CWPPro and having some trouble with PostgreSQL and phpPgAdmin.
The installation of PostgreSQL database server was fine using root panel. I can create databases and users.
When I install phpPgAdmin using command /script/install_phpPgAdmin the command runs fine, no errors, but when I click in phpPgAdmin a PHP error occured telling me that I does'n have PHP module enabled.
I tried to enable module but with no success.
I found a site with another installing method that worked:
https://www.alphagnu.com/topic/321-how-to-enable-pgadmin/
But when I try to login in database, does not work. Always show "Login Failed" and this database log:
2024-03-18 17:54:23.515 GMT [523] LOG: provided user name (XXXXX) and authenticated user name (cwpsvc) do not match
2024-03-18 17:54:23.515 GMT [523] FATAL: Peer authentication failed for user "XXXXX"
2024-03-18 17:54:23.515 GMT [523] DETAIL: Connection matched pg_hba.conf line 84: "local all all peer"
Is this a bug?
I have to change some configuration file?
Thanks!
Im using CWPPro and having some trouble with PostgreSQL and phpPgAdmin.
The installation of PostgreSQL database server was fine using root panel. I can create databases and users.
When I install phpPgAdmin using command /script/install_phpPgAdmin the command runs fine, no errors, but when I click in phpPgAdmin a PHP error occured telling me that I does'n have PHP module enabled.
I tried to enable module but with no success.
I found a site with another installing method that worked:
https://www.alphagnu.com/topic/321-how-to-enable-pgadmin/
But when I try to login in database, does not work. Always show "Login Failed" and this database log:
2024-03-18 17:54:23.515 GMT [523] LOG: provided user name (XXXXX) and authenticated user name (cwpsvc) do not match
2024-03-18 17:54:23.515 GMT [523] FATAL: Peer authentication failed for user "XXXXX"
2024-03-18 17:54:23.515 GMT [523] DETAIL: Connection matched pg_hba.conf line 84: "local all all peer"
Is this a bug?
I have to change some configuration file?
Thanks!
2
CentOS-WebPanel Bugs / SCP files upload in wrong permission
« on: June 01, 2018, 06:01:40 PM »
Hi!
I was using SCP to send files through ssh and I noticed that files upload are created in different permission than original permission of owner.
The FTP works well, but SCP dont.
Att,
I was using SCP to send files through ssh and I noticed that files upload are created in different permission than original permission of owner.
The FTP works well, but SCP dont.
Att,
3
CentOS 7 Problems / Problems and suggestions for Wildcard certificate installation and CSR generatio
« on: March 15, 2018, 08:30:15 PM »
Hi!
First, congrats for this panel. Its the best panel available at low cost.
Now, some suggestions.
I always have problem when installing Wildcard certificate, beacuse Wildcard works a little bit different from normal domain certificate. This is not so easy for non-technical people and I think with some not so hard changes, this will become easier.
First, when creating CSR for domain, we must use *.domain.com for Wildcard SSL. This will create the file with "*." in name, like "*.domain.com", for example. The panel shows error when it reads this file.
I suggest, if the domain starts with "*." chars, this is always a Wildcard domain, just ignore them. Create the file with domain name only, follow by ".cert", ".key" or ".csr".
Second, the Wildcard certificate is the same file for all subdomains that needs to be certificated. The panel creates a file for each domain, because it uses the domain name given in field "Domain:" on "SSL Cert Manager". This cause the user to copy and paste the certificate every time when he needs to use the cert. If this cert will be renewed, the user needs to update all these files.
I suggest use the same name when created the CSR file, without final part ".csr" of file. The domain is only used to apache configuration files. When need to renew this certificate, we just update one file with certificate and all subdomains is ok.
If there was a checkbox that tells to panel if this is a wildcard certificate, or if the panel identifies from domain having *. in the beggining, would help.
Sorry about the long post.
That's all, i think!
Thanks!
First, congrats for this panel. Its the best panel available at low cost.
Now, some suggestions.
I always have problem when installing Wildcard certificate, beacuse Wildcard works a little bit different from normal domain certificate. This is not so easy for non-technical people and I think with some not so hard changes, this will become easier.
First, when creating CSR for domain, we must use *.domain.com for Wildcard SSL. This will create the file with "*." in name, like "*.domain.com", for example. The panel shows error when it reads this file.
I suggest, if the domain starts with "*." chars, this is always a Wildcard domain, just ignore them. Create the file with domain name only, follow by ".cert", ".key" or ".csr".
Second, the Wildcard certificate is the same file for all subdomains that needs to be certificated. The panel creates a file for each domain, because it uses the domain name given in field "Domain:" on "SSL Cert Manager". This cause the user to copy and paste the certificate every time when he needs to use the cert. If this cert will be renewed, the user needs to update all these files.
I suggest use the same name when created the CSR file, without final part ".csr" of file. The domain is only used to apache configuration files. When need to renew this certificate, we just update one file with certificate and all subdomains is ok.
If there was a checkbox that tells to panel if this is a wildcard certificate, or if the panel identifies from domain having *. in the beggining, would help.
Sorry about the long post.
That's all, i think!
Thanks!
4
SSL / Re: Want to install Wildcard SSL in CWP
« on: March 15, 2018, 08:11:12 PM »
This is very hard. I whink they should take this easy to us. I will post the problems I have facing with this in another thread.
To install a Wildcard SSL, first, you generate a CSR. You need to use *.domain.com in CN. The file will be generated with "*." in name, this is your first problem, because it is not recognized by panel.
Login in SSH and rename file "*.domain.com.csr" to just "domain.com.csr". Do the same with key file.
These files are located in "/etc/pki/tls/certs" and "/etc/pki/tls/private".
After this, get your CSR and order your certificate.
After you receive your certificate, you must paste the certificate in file "domain.com.cert" inside "/etc/pki/tls/certs". I don't remember if this file is created empty. If not, create yourself using panel file manager.
When you go to install your cert for your domain, the panel suggest the "*.domain.com" as domain, you need use only "domain.com" as domain, otherwise, will not work. This is the second problem, because the panel use the domain name you specify as file name.
When you go to install the certificate for other subdomains of your domain, the panel use a diferent file for each subdomain, but this certificate is a Wildcard, there is no sense to use diferent filenames for this, just specify other domain and your are ok.
In this case, you will need to copy the content of certificate file to this new created subdomain file, and for the bundle file too.
The bundle file must contain the certificate for your domain (the one you bought) and below the root certificate from your certificate provider.
This is a bit confusing.
To install a Wildcard SSL, first, you generate a CSR. You need to use *.domain.com in CN. The file will be generated with "*." in name, this is your first problem, because it is not recognized by panel.
Login in SSH and rename file "*.domain.com.csr" to just "domain.com.csr". Do the same with key file.
These files are located in "/etc/pki/tls/certs" and "/etc/pki/tls/private".
After this, get your CSR and order your certificate.
After you receive your certificate, you must paste the certificate in file "domain.com.cert" inside "/etc/pki/tls/certs". I don't remember if this file is created empty. If not, create yourself using panel file manager.
When you go to install your cert for your domain, the panel suggest the "*.domain.com" as domain, you need use only "domain.com" as domain, otherwise, will not work. This is the second problem, because the panel use the domain name you specify as file name.
When you go to install the certificate for other subdomains of your domain, the panel use a diferent file for each subdomain, but this certificate is a Wildcard, there is no sense to use diferent filenames for this, just specify other domain and your are ok.
In this case, you will need to copy the content of certificate file to this new created subdomain file, and for the bundle file too.
The bundle file must contain the certificate for your domain (the one you bought) and below the root certificate from your certificate provider.
This is a bit confusing.
5
Information / Re: PHP or Apache disabled functions
« on: August 29, 2017, 12:31:11 PM »
I understand.
But the other panels also run with cgi and works. Do you know if this function is disabled in some config file?
I think just enabling this function will not affect security, or am I wrong?
Thanks!
But the other panels also run with cgi and works. Do you know if this function is disabled in some config file?
I think just enabling this function will not affect security, or am I wrong?
Thanks!
6
Information / Re: PHP or Apache disabled functions
« on: August 29, 2017, 01:46:54 AM »
Wordpress with W3 Total Cache isn't able to check some modules in Compatibility Check tool.
The code that do this checks use "apache_get_modules" function, that is disabled.
I know the modules is installed, but customers want see the "ok" on Compatibility Check tool.
There is no how "whitelist" some functions?
Thanks!
The code that do this checks use "apache_get_modules" function, that is disabled.
I know the modules is installed, but customers want see the "ok" on Compatibility Check tool.
There is no how "whitelist" some functions?
Thanks!
7
Information / PHP or Apache disabled functions
« on: August 28, 2017, 04:47:14 PM »
Hi everyone!
Does PHP or apache have disabled some functions by default in CWP?
I need to run "apache_get_modules" and nothing gets returned.
I found this issue running a Wordpress W3 Total Cache compatibility test, wich tell modules not installed in Apache, but they are installed.
I have done a search for "disabled_functions" in PHP ini files compiled through PHP Selector and nothing was found. There is other files with this option?
Thanks!
Does PHP or apache have disabled some functions by default in CWP?
I need to run "apache_get_modules" and nothing gets returned.
I found this issue running a Wordpress W3 Total Cache compatibility test, wich tell modules not installed in Apache, but they are installed.
I have done a search for "disabled_functions" in PHP ini files compiled through PHP Selector and nothing was found. There is other files with this option?
Thanks!
8
SSL / Re: SSL with subdomains, wildcard problem
« on: August 28, 2017, 04:40:15 PM »
Yes, sure it works!
But is interesting that pannel do it automatically. How we can tell to developers about this issue?
But is interesting that pannel do it automatically. How we can tell to developers about this issue?
9
SSL / Re: SSL with subdomains, wildcard problem
« on: August 25, 2017, 03:40:35 AM »
I think if you not use * in domain, when you generate a CSR, the ssl seller won't understand as Wildcard certificate, because there is no *. in domain.
In filesystem, some links was created wrong, I think.
Why dont replace the *. part of file by *-, fo example? This should work.
Another hint is to create a option to upload certificate, like cPanel do.
In filesystem, some links was created wrong, I think.
Why dont replace the *. part of file by *-, fo example? This should work.
Another hint is to create a option to upload certificate, like cPanel do.
10
SSL / Re: SSL with subdomains, wildcard problem
« on: August 25, 2017, 03:23:16 AM »
Hi!
Im facing this problem too. It creates a file started with *.yourdomain.com.crt, but this *. have problems with linux filesystem.
Does anyone has installed a Wildcard on CWP before?
Im facing this problem too. It creates a file started with *.yourdomain.com.crt, but this *. have problems with linux filesystem.
Does anyone has installed a Wildcard on CWP before?
11
CentOS 7 Problems / Problem installing Wildcard SSL valid certificate
« on: August 22, 2017, 10:06:43 PM »
Im facing problem installating a valid Wildcard SSL.
When I generate the CSR using *.domain.com (*. because it is wildcard), the file generated contains *. in the name, causing problems with linux filesystem.
I think the . must be replaced in file names.
When I generate the CSR using *.domain.com (*. because it is wildcard), the file generated contains *. in the name, causing problems with linux filesystem.
I think the . must be replaced in file names.
Pages: [1]
