Sponsor:

Server and Web Integrator
Link:
Kloxo-MR logo
6.5.0 or 7.0.0
Click for "How to install"
Donation/Sponsorship:
Kloxo-MR is open-source.
Donate and or Sponsorship always welcome.
Click to:
Click Here
Please login or register. 2024-03-29, 15:57:02

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 - LotsOfQ

Pages: 1 2 [3] 4 5 ... 31
31
Kloxo-MR Tips and Tricks / Re: Alternative to Kloxo-MR
« on: 2017-12-18, 08:55:20 »
hm.. VestaCP e.g.
It also has an open source code

How is it compare to Kloxo-MR? You're currently using it?

32
Solved.

Code: [Select]
Go to https://curl.haxx.se/docs/caextract.html and download cacert.pem
rename it to ca-bundle.crt
replace  /etc/pki/tls/certs/ca-bundle.crt

33
I've checked log and found this. It might be because I've upgraded Curl to the latest version (curl.x86_64 0:7.57.0-1.0.cf.rhel6).
Code: [Select]
7] Please refer to https://curl.haxx.se/libcurl/c/libcurl-errors.html for error code: 77
[Sun Dec 17 04:12:21 PST 2017] Can not connect to https://acme-v01.api.letsencrypt.org/directory to get nonce.
[Sun Dec 17 04:12:21 PST 2017] Can not get domain new authz.
[Sun Dec 17 04:12:21 PST 2017] Please add '--debug' or '--log' to check more details.
[Sun Dec 17 04:12:21 PST 2017] See: https://github.com/Neilpang/acme.sh/wiki/How-to-debug-acme.sh
Should I downgrade it and if so, how do I downgrade?

34
I can't add Let's Encrypt anymore. It was working fine before. All old ones are still working fine but can't add new ones.

Keeps getting this error. "Alert: Create Certificate failed"

Tried:
Code: [Select]
sh /script/fixssl; sh /script/fixweb; sh /script/restart-web -y
sh /script/fixdns;sh /script/restart-all;
sh /script/fixdnsaddstatsrecord

I'm out of idea. Anyone please help.

35
[Solved] I've found the solution and thought to share it if anyone runs into this. I updated curl and it solved. And updating I followed the step here:
https://forum.mratwork.com/kloxo-mr-technical-helps/how-to-upgrade-curl-to-latest-version/msg46811/#msg46811

36
Kloxo-MR Technical Helps / How to update NSS?
« on: 2017-12-16, 21:57:09 »
How do you update NSS?

37
Kloxo-MR Tips and Tricks / Alternative to Kloxo-MR
« on: 2017-12-16, 21:47:34 »
Without MRatWork, we're lost. Many threads are not answer. I still have the same issue for awhile now.

https://forum.mratwork.com/kloxo-mr-technical-helps/curl-error-60-peer-certificate-cannot-be-authenticated/

I am losing hope and starting to think it's the end.

Anyone know of an alternative to Kloxo-MR? Please if you do share it here.

38
What I was told before was Varnish doesn't work with https.

39
Yes, that's what I did. I used example.com as example but I did replaced it with my real domain and that's the errors I got.

Code: [Select]
curl -v https://mydomain.com
* About to connect() to mydomain.com port 443 (#0)
*   Trying 133.244.221.21... connected
* Connected to mydomin.com (133.244.221.21) port 443 (#0)
* Initializing NSS with certpath: sql:/etc/pki/nssdb
* NSS error -8018
* Closing connection #0
* Problem with the SSL CA cert (path? access rights?)
curl: (77) Problem with the SSL CA cert (path? access rights?)

40
Thank you so much for the help. I feel like I'm one step close to a solution. Again thank you.

I tried to follow the solution but got errors on this step. Any idea what to do?

Code: [Select]
curl -v https://example.com
* About to connect() to example.com port 443 (#0)
*   Trying 133.244.221.21... connected
* Connected to example.com (133.244.221.21) port 443 (#0)
* Initializing NSS with certpath: sql:/etc/pki/nssdb
* NSS error -8018
* Closing connection #0
* Problem with the SSL CA cert (path? access rights?)
curl: (77) Problem with the SSL CA cert (path? access rights?)

42
What I meant was this is my original.
Code: [Select]
listen 443 ssl http2;
listen [::]:433 ssl http2;

I noticed yours is httpd. So do I change it to httpd like yours?

About 433, I know it has to be 443 but unclear about httpd and http2.

Also in my listen_ssl_back.conf file:
Code: [Select]
listen 8433;
listen [::]:8433;

Do I just change it to this?
Code: [Select]
listen 8443;
listen [::]:8443;
or
Code: [Select]
listen 8443 ssl http2;
listen [::]:8443 ssl http2;

43
I've just realized that mine said:

Code: [Select]
listen 443 ssl http2;
listen [::]:433 ssl http2;

So it's not httpd but http2, change it to httpd?

44
My listen_ssl_back.conf file
Code: [Select]
listen 8433;
listen [::]:8433;

Should I change line 1 also?

Quote
listen 8443 ssl http2;

45
More info that I found people with similar issue asking for support.

Code: [Select]
pretty sure that error whould be a problem with your SSL Certificate itself.  So would need to have your we host check your SSL Certification.

Pretty sure this an issue that only your web host can take core of for you.  ie SSL Cert is not setup correctly, cURL/OpenSSL issue, etc.

Pages: 1 2 [3] 4 5 ... 31

MRatWork Affiliates:    BIGRAF(R) Inc.    House of LMAR    EFARgrafix

Page created in 0.036 seconds with 20 queries.

web stats analysis