Messages

1

Information / Re: Can't login to client portal

« on: May 05, 2022, 02:23:41 PM »

solved.

2

Information / Can't login to client portal

« on: May 05, 2022, 11:52:34 AM »

Are there any other people who cannot login into client portal anymore?
https://support.centos-webpanel.com/clientarea.php

Please try and let me know

3

Migration from other control panels / Re: CWP -> CWP Connection not reached - RESOLVED

« on: February 17, 2022, 10:33:19 PM »

SOLVED! We found out that ssh needs to have "PermitRootLogin yes"

4

Migration from other control panels / CWP -> CWP Connection not reached

« on: February 17, 2022, 07:07:44 PM »

I looked in forum for an answer but could not find it. Our problem is the error: Connection not reached While connecting to migration. Firewalls are down so no limitation, ips are in whitelist, know hosts etc. We can migratie any server we want but except this one. Any ideas on how to debug why this "Connection not reached" error can be solved? We can SSH to the migration server just fine. So looks like the tool just does not start or connect. Please any advice?

5

SSL / Disable TLSv1.0 and v1.1 in openssl

« on: September 13, 2021, 02:57:55 PM »

Hello, how can we disable TLS v1.0 and v1.1 in openSSL? We tries all but then openSSL breaks all. We are able to disable tls on apache and NGIX but not on openSSL. Please any suggestions?

Thanks, Ron

6

Apache / ip to name how to do?

« on: September 06, 2021, 11:22:12 AM »

We have a CWP and all working fine. Now the base IP is http://1.2.3.4 (for example) and we want this IP not to serve any pages as we cannot set any SSL on IP. So is it possible to have the .htaccess in /usr/local/apache/htdocs have some redirect option? If we put a htaccess in there the redirection does not work at all. We added the correct user to the .htaccess and put this inside there:
(ip is fictive)
RewriteEngine On
RewriteBase /
RewriteCond %{HTTP_HOST} ^12\.34\.56\.789$
RewriteRule ^(.*)$ http://www.domainname.com/$1 [L,R=301]

Redirect is configured just fine but not running. Hope you guys can maybe have some help?

I also get this in the logs:
 client denied by server configuration: /usr/local/apache/htdocs/.htaccess
Nothing is changed on apache side it is default.

7

SSL / Re: acme.sh is now using zerossl, change it to letsencrypt CA server

« on: June 21, 2021, 08:49:58 PM »

you've malformed vhost probably you're using custom template. If yes recreate those template

Hi, we did not but is there a way to set default? So we can test?

8

SSL / Re: acme.sh is now using zerossl, change it to letsencrypt CA server

« on: June 18, 2021, 05:27:33 AM »

Try it for yourself and see. It is related to let’s encrypt

we've already tested and provided the solution, whats in nginx error log ?

-- Unit nginx.service has begun starting up.
Jun 18 07:24:55 wp04.refreshserver.nl nginx[301557]: nginx: [emerg] SSL_CTX_set_cipher_list("EECDH~~@@~~ECDSA~~@@~~AESGCM:EECDH~~@@~~aRSA~~@@~~AESGCM:EECDH~~@@~~ECDSA~~@@~~SHA384:EECDH~~@@~~ECDSA~~@@~~SHA256:EECDH~~@@~~aRSA~~@@~~SHA384:EECDH~~@@~~aRSA~~@@~~SHA256:EECDH~~@@~~aRSA!RC4:EECDH:!RC4:!aNULL:!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!SRP:!DSS") failed (SSL: error:140E6118:SSL routines:ssl_cipher_process_rulestr:invalid command error:140E6118:SSL routines:ssl_cipher_process_rulestr:invalid command error:140E6118:SSL routines:ssl_cipher_process_rulestr:invalid command error:140E6118:SSL routines:ssl_cipher_process_rulestr:invalid command error:140E6118:SSL routines:ssl_cipher_process_rulestr:invalid command error:140E6118:SSL routines:ssl_cipher_process_rulestr:invalid command error:140E6118:SSL routines:ssl_cipher_process_rulestr:invalid command)
Jun 18 07:24:55 wp04.refreshserver.nl nginx[301557]: nginx: configuration file /etc/nginx/nginx.conf test failed
Jun 18 07:24:55 wp04.refreshserver.nl systemd[1]: nginx.service: Control process exited, code=exited status=1
Jun 18 07:24:55 wp04.refreshserver.nl systemd[1]: nginx.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- The unit nginx.service has entered the 'failed' state with result 'exit-code'.
Jun 18 07:24:55 wp04.refreshserver.nl systemd[1]: Failed to start The nginx HTTP and reverse proxy server.
-- Subject: Unit nginx.service has failed
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- Unit nginx.service has failed.
--
-- The result is failed.

9

SSL / Re: acme.sh is now using zerossl, change it to letsencrypt CA server

« on: June 17, 2021, 11:47:53 AM »

Try it for yourself and see. It is related to let’s encrypt

we've already tested and provided the solution, whats in nginx error log ?

I uninstalled nginx as all sites where dead. So I dont have any log anymore. It just said nginx was not running and could not be restarted. So please provide us with the solution please?

10

SSL / Re: acme.sh is now using zerossl, change it to letsencrypt CA server

« on: June 17, 2021, 04:03:06 AM »

Try it for yourself and see. It is related to let’s encrypt

11

SSL / Re: AutoSSL not working on Centos7

« on: June 15, 2021, 10:59:53 AM »

Issue is being wroked on, there is a fix available... see this thread: https://forum.centos-webpanel.com/index.php?topic=10946.0

Look at when patch is applied all NginX sites will stop working. So be aware!

12

SSL / Re: acme.sh is now using zerossl, change it to letsencrypt CA server

« on: June 15, 2021, 10:48:22 AM »

Since today we've many ticket regarding autossl is failing, this is due to acme client changed the default CA to zerossl to change back to letsencrypt run the below command as root

Code: [Select]

/root/.acme.sh/acme.sh --set-default-ca  --server  letsencrypt
and then issue the certs

this is temporary until we fix it in core cwp and push the update

After this command NginX  wont startup again. Can you please help with a fix?

13

CentOS 7 Problems / TLSv1.3

« on: January 09, 2021, 12:39:46 PM »

Does anyone got the TLSv1.3 version on CWP7 with centos 7 working? We dont seem to get it working. I hope someone can help us out as we now only have TLSv1.2. Thanks so much.

Ron Cooper