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.


Messages - cvrle77

Pages: [1]
1
SSL / AutoSSL
« on: March 05, 2018, 02:46:35 AM »
Running Apache & Varnish Cache & Nginx Reverse Proxy with SSL.

After renewal of SSL today, everything effed up. One click on AutoSSL.
After that one click of death, nginx is off, and SSL is running on Apache
Can't start nginx if apache is working

Code: [Select]
Starting nginx: nginx: [emerg] bind() to 208.115.237.135:443 failed (98: Address already in use)
nginx: [emerg] bind() to 208.115.237.135:443 failed (98: Address already in use)
nginx: [emerg] bind() to 208.115.237.135:443 failed (98: Address already in use)
nginx: [emerg] bind() to 208.115.237.135:443 failed (98: Address already in use)
nginx: [emerg] bind() to 208.115.237.135:443 failed (98: Address already in use)
nginx: [emerg] still could not bind()
[FAILED]

Can't start apache if nginx is working

Code: [Select]
Starting httpd: AH00548: NameVirtualHost has no effect and will be removed in the next release /usr/local/apache/conf.d/ssl.conf:9
(98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:443
no listening sockets available, shutting down
AH00015: Unable to open logs
[FAILED]


I don't even know where to begin to fix something that was previously working as it should, before CWP update.
Now my wordpress site is running as if I am only running apache+SSL, without varnish and nginx as proxy.

Any fast help?
Using CWPpro version: 0.9.8.351

2
CentOS-WebPanel Bugs / CWP6Pro going crazy
« on: January 17, 2018, 12:47:45 PM »
So, the moment I got the pro version (12 days ago), after using free version for more than a year, I am experiencing some crazy issues, which can be seen in the images. After I've hit the UPDATE button on the varnish_conf2 page, varnish stopped working.
So I had to copy varnish from etc/sysconfig from my other server, which is free, to make varnish work again. And it works to some degree, when there is VERY low traffic. So I have to remove DAEMON_OPTS from the file, stop varnish, and run it that way, to keep my website alive.

I've purchased PRO version only so I can run varnish from RAM, and now I can't run varnish at all. Each time I send a notification from my blog about new post, few minutes later, I get error messages in CWP if varnish is turned on, website throws 500 and 503 error messages, and comes back online, and after this, everything messes up, until CWP crashes, website crashes, OS crashes, and I am unable to log in via ssh. Only option is to reboot my server.





3
Today I got this message

curl: (60) Peer certificate cannot be authenticated with known CA certificates
More details here: http://curl.haxx.se/docs/sslcerts.html

curl performs SSL certificate verification by default, using a "bundle"
 of Certificate Authority (CA) public keys (CA certs). If the default
 bundle file isn't adequate, you can specify an alternate file
 using the --cacert option.
If this HTTPS server uses a certificate signed by a CA represented in
 the bundle, the certificate verification probably failed due to a
 problem with the certificate (it might be expired, or the name might
 not match the domain name in the URL).
If you'd like to turn off curl's verification of the certificate, use
 the -k (or --insecure) option.

I have COMODO SSL cert installed, and everything was ok, until this morning.
How do I fix this, without turning off curl's verification.


Pages: [1]