I have already tired with the following arguments.
0 13 */28 * ? *
and getting the following output
Wed, 01 Jun 2022 13:00:00 GMT
Wed, 29 Jun 2022 13:00:00 GMT
Fri, 01 Jul 2022 13:00:00 GMT
Fri, 29 Jul 2022 13:00:00 GMT
Mon, 01 Aug 2022 13:00:00 GMT
Mon, 29 Aug 2022 13:00:00 GMT
Thu, 01 Sep 2022 13:00:00 GMT
Thu, 29 Sep 2022 13:00:00 GMT
Sat, 01 Oct 2022 13:00:00 GMT
Sat, 29 Oct 2022 13:00:00 GMT
Expected output is to avoid Saturday and Sunday
I have tried that I can able to create one day of month.
enter image description here
Related
I have a docker-compose file with 4 containers, one of which is Redis. The image builds up properly and runs properly initially but after some time (sometimes it happens within 10 minutes or sometimes after a few hours) the Redis start throwing errors and my container 'worker' fails.
docker-compose.yml
version: '3.7'
services:
web:
build:
context: .
command: gunicorn EmotAPI.wsgi:application --bind 0.0.0.0:8000
ports:
- "8000:8000"
container_name: emot_web
depends_on:
- redis
worker:
build:
context: .
command: python manage.py rqworker default
depends_on:
- web
- redis
nginx:
build: ./nginx
ports:
- "80:80"
depends_on:
- web
redis:
image: "redis:latest"
ports:
- "6379:6379"
redis error log (after which functions start to fail)
1:S 06 Jul 2022 08:03:53.556 # Failed to read response from the server: Connection reset by peer
1:S 06 Jul 2022 08:03:53.556 # Master did not respond to command during SYNC handshake
1:S 06 Jul 2022 08:03:54.567 # Failed to read response from the server: Connection reset by peer
1:S 06 Jul 2022 08:03:54.567 # Master did not respond to command during SYNC handshake
1:S 06 Jul 2022 08:03:56.509 # Wrong signature trying to load DB from file
1:S 06 Jul 2022 08:03:56.509 # Failed trying to load the MASTER synchronization DB from disk: Invalid argument
1:S 06 Jul 2022 08:03:56.870 # Failed to read response from the server: Connection reset by peer
1:S 06 Jul 2022 08:03:56.870 # Master did not respond to command during SYNC handshake
1:S 06 Jul 2022 08:03:57.588 # Failed to read response from the server: Operation in progress
1:S 06 Jul 2022 08:03:57.588 # Master did not respond to command during SYNC handshake
1:S 06 Jul 2022 08:03:58.581 # Failed to read response from the server: Connection reset by peer
1:S 06 Jul 2022 08:03:58.581 # Master did not respond to command during SYNC handshake
1:S 06 Jul 2022 08:03:59.596 # Failed to read response from the server: Connection reset by peer
1:S 06 Jul 2022 08:03:59.596 # Master did not respond to command during SYNC handshake
1:S 06 Jul 2022 08:04:00.612 # Failed to read response from the server: Connection reset by peer
1:S 06 Jul 2022 08:04:00.612 # Master did not respond to command during SYNC handshake
1:S 06 Jul 2022 08:04:01.609 # Failed to read response from the server: Connection reset by peer
1:S 06 Jul 2022 08:04:01.609 # Master did not respond to command during SYNC handshake
1:S 06 Jul 2022 08:04:02.613 # Failed to read response from the server: Operation in progress
1:S 06 Jul 2022 08:04:02.613 # Master did not respond to command during SYNC handshake
1:S 06 Jul 2022 08:04:03.613 # Failed to read response from the server: Connection reset by peer
1:S 06 Jul 2022 08:04:03.613 # Master did not respond to command during SYNC handshake
1:S 06 Jul 2022 08:04:04.631 # Failed to read response from the server: Operation in progress
1:S 06 Jul 2022 08:04:04.631 # Master did not respond to command during SYNC handshake
1:S 06 Jul 2022 08:04:05.624 # Failed to read response from the server: Connection reset by peer
1:S 06 Jul 2022 08:04:05.624 # Master did not respond to command during SYNC handshake
1:S 06 Jul 2022 08:04:06.625 # Failed to read response from the server: Connection reset by peer
1:S 06 Jul 2022 08:04:06.625 # Master did not respond to command during SYNC handshake
1:S 06 Jul 2022 08:04:07.653 # Failed to read response from the server: Connection reset by peer
1:S 06 Jul 2022 08:04:07.653 # Master did not respond to command during SYNC handshake
1:S 06 Jul 2022 08:04:08.658 # Failed to read response from the server: Connection reset by peer
1:S 06 Jul 2022 08:04:08.658 # Master did not respond to command during SYNC handshake
1:S 06 Jul 2022 08:04:09.648 # Failed to read response from the server: Connection reset by peer
1:S 06 Jul 2022 08:04:09.648 # Master did not respond to command during SYNC handshake
1:S 06 Jul 2022 08:04:10.659 # Failed to read response from the server: Operation in progress
1:S 06 Jul 2022 08:04:10.659 # Master did not respond to command during SYNC handshake
1:S 06 Jul 2022 08:04:11.674 # Failed to read response from the server: Connection reset by peer
1:S 06 Jul 2022 08:04:11.674 # Master did not respond to command during SYNC handshake
1:S 06 Jul 2022 08:04:12.670 # Failed to read response from the server: Operation in progress
1:S 06 Jul 2022 08:04:12.670 # Master did not respond to command during SYNC handshake
1:S 06 Jul 2022 08:04:13.665 # Failed to read response from the server: Operation in progress
1:S 06 Jul 2022 08:04:13.665 # Master did not respond to command during SYNC handshake
1:S 06 Jul 2022 08:04:14.686 # Failed to read response from the server: Operation in progress
1:S 06 Jul 2022 08:04:14.686 # Master did not respond to command during SYNC handshake
1:S 06 Jul 2022 08:04:16.669 # Wrong signature trying to load DB from file
1:S 06 Jul 2022 08:04:16.669 # Failed trying to load the MASTER synchronization DB from disk: Invalid argument
1:S 06 Jul 2022 08:04:17.056 # Failed to read response from the server: Connection reset by peer
1:S 06 Jul 2022 08:04:17.057 # Master did not respond to command during SYNC handshake
1:S 06 Jul 2022 08:04:17.692 # Failed to read response from the server: Connection reset by peer
1:S 06 Jul 2022 08:04:17.692 # Master did not respond to command during SYNC handshake
1:S 06 Jul 2022 08:04:18.709 # Failed to read response from the server: Connection reset by peer
1:S 06 Jul 2022 08:04:18.709 # Master did not respond to command during SYNC handshake
1:S 06 Jul 2022 08:04:19.716 # Failed to read response from the server: Connection reset by peer
1:S 06 Jul 2022 08:04:19.716 # Master did not respond to command during SYNC handshake
1:S 06 Jul 2022 08:04:20.712 # Failed to read response from the server: Operation in progress
1:S 06 Jul 2022 08:04:20.712 # Master did not respond to command during SYNC handshake
1:S 06 Jul 2022 08:04:21.717 # Failed to read response from the server: Connection reset by peer
1:S 06 Jul 2022 08:04:21.717 # Master did not respond to command during SYNC handshake
1:S 06 Jul 2022 08:04:22.731 # Failed to read response from the server: Connection reset by peer
1:S 06 Jul 2022 08:04:22.731 # Master did not respond to command during SYNC handshake
1:S 06 Jul 2022 08:04:23.732 # Failed to read response from the server: Operation in progress
1:S 06 Jul 2022 08:04:23.732 # Master did not respond to command during SYNC handshake
1:S 06 Jul 2022 08:04:24.743 # Failed to read response from the server: Operation in progress
1:S 06 Jul 2022 08:04:24.743 # Master did not respond to command during SYNC handshake
1:S 06 Jul 2022 08:04:25.739 # Failed to read response from the server: Connection reset by peer
1:S 06 Jul 2022 08:04:25.739 # Master did not respond to command during SYNC handshake
1:S 06 Jul 2022 08:04:26.740 # Failed to read response from the server: Connection reset by peer
1:S 06 Jul 2022 08:04:26.740 # Master did not respond to command during SYNC handshake
1:S 06 Jul 2022 08:04:27.751 # Failed to read response from the server: Connection reset by peer
1:S 06 Jul 2022 08:04:27.751 # Master did not respond to command during SYNC handshake
1:S 06 Jul 2022 08:04:28.752 # Failed to read response from the server: Connection reset by peer
1:S 06 Jul 2022 08:04:28.752 # Master did not respond to command during SYNC handshake
1:S 06 Jul 2022 08:04:29.768 # Failed to read response from the server: Connection reset by peer
1:S 06 Jul 2022 08:04:29.768 # Master did not respond to command during SYNC handshake
1:S 06 Jul 2022 08:04:30.775 # Failed to read response from the server: Connection reset by peer
1:S 06 Jul 2022 08:04:30.775 # Master did not respond to command during SYNC handshake
1:S 06 Jul 2022 08:04:31.772 # Failed to read response from the server: Connection reset by peer
1:S 06 Jul 2022 08:04:31.772 # Master did not respond to command during SYNC handshake
1:S 06 Jul 2022 08:04:32.761 # Failed to read response from the server: Connection reset by peer
1:S 06 Jul 2022 08:04:32.761 # Master did not respond to command during SYNC handshake
1:S 06 Jul 2022 08:04:33.796 # Failed to read response from the server: Connection reset by peer
1:S 06 Jul 2022 08:04:33.796 # Master did not respond to command during SYNC handshake
1:S 06 Jul 2022 08:04:34.794 # Failed to read response from the server: Operation in progress
1:S 06 Jul 2022 08:04:34.794 # Master did not respond to command during SYNC handshake
1:S 06 Jul 2022 08:04:36.756 # Wrong signature trying to load DB from file
1:S 06 Jul 2022 08:04:36.756 # Failed trying to load the MASTER synchronization DB from disk: Invalid argument
1:S 06 Jul 2022 08:04:37.126 # Failed to read response from the server: Connection reset by peer
1:S 06 Jul 2022 08:04:37.126 # Master did not respond to command during SYNC handshake
1:S 06 Jul 2022 08:04:37.811 # Failed to read response from the server: Connection reset by peer
1:S 06 Jul 2022 08:04:37.811 # Master did not respond to command during SYNC handshake
1:S 06 Jul 2022 08:04:38.813 # Failed to read response from the server: Connection reset by peer
1:S 06 Jul 2022 08:04:38.813 # Master did not respond to command during SYNC handshake
1:S 06 Jul 2022 08:04:39.821 # Failed to read response from the server: Connection reset by peer
1:S 06 Jul 2022 08:04:39.821 # Master did not respond to command during SYNC handshake
1:S 06 Jul 2022 08:04:40.818 # Failed to read response from the server: Connection reset by peer
1:S 06 Jul 2022 08:04:40.818 # Master did not respond to command during SYNC handshake
1:S 06 Jul 2022 08:04:41.832 # Failed to read response from the server: Connection reset by peer
1:S 06 Jul 2022 08:04:41.832 # Master did not respond to command during SYNC handshake
1:S 06 Jul 2022 08:04:42.830 # Failed to read response from the server: Operation in progress
1:S 06 Jul 2022 08:04:42.830 # Master did not respond to command during SYNC handshake
I am unable to find a solution for it. Also, I am quite new to Redis so sorry if it's just a silly question, but there were no resources available so I had to resort to asking a question.
Okay, so the issue was not with Redis actually but a security issue. You shouldn't really open the ports to the public. Cryptojackers were taking control of the redis server and causing it to malfunction. To fix it, I just had to remove the line 'ports: - "6379:6379"' and the issue was resolved.
I have a kerberised CDH v5.14 cluster with 3 nodes.I trying to call the HDFS API using python as below
baseurl = "http://<host_name>:50070/webhdfs/v1/prod/?op=LISTSTATUS"
__, krb_context = kerberos.authGSSClientInit("HTTP/<host_name>")
#kerberos.authGSSClientStep(krb_context, "")
negotiate_details = kerberos.authGSSClientResponse(krb_context)
headers = {"Authorization": "Negotiate " + str(negotiate_details)}
r = requests.get(baseurl, headers=headers)
print r.status_code
The below error is returned
GSSException: Defective
token detected (Mechanism level: GSSHeader did not find the right tag)
HTTP ERROR 403
But the same works fine when I run it using curl
curl -i --negotiate -u: http://<host_name>:50070/webhdfs/v1/prod/?op=LISTSTATUS
HTTP/1.1 401 Authentication required Cache-Control:
must-revalidate,no-cache,no-store Date: Wed, 30 May 2018 02:50:04 GMT
Pragma: no-cache Date: Wed, 30 May 2018 02:50:04 GMT Pragma: no-cache
Content-Type: text/html; charset=iso-8859-1 X-FRAME-OPTIONS:
SAMEORIGIN WWW-Authenticate: Negotiate Set-Cookie: hadoop.auth=;
Path=/; HttpOnly Content-Length: 1409
HTTP/1.1 200 OK Cache-Control: no-cache Expires: Wed, 30 May 2018
02:50:04 GMT Date: Wed, 30 May 2018 02:50:04 GMT Pragma: no-cache
Expires: Wed, 30 May 2018 02:50:04 GMT Date: Wed, 30 May 2018 02:50:04
GMT Pragma: no-cache Content-Type: application/json X-FRAME-OPTIONS:
SAMEORIGIN WWW-Authenticate: Negotiate
YGYGCSqGSIb3EgECAgIAb1cwVaADAgEFoQMCAQ+iSTBHoAMCAReiQAQ+6Seu0SSYGmoqN4hdykSQ55ZcP+juBO/jk8/BGjoK5NCmdlBRFPMSbCZXvVjNHLg9iPACGvM8V0jqXTM5UfQ=
Set-Cookie:
hadoop.auth="u=XXXX&p=XXXX#HOSTNAME&t=kerberos&e=1527684604664&s=tVsrEsDMBGV0To8hOPp8mLxyiSo=";
Path=/; HttpOnly Transfer-Encoding: chunked
and it gives the correct response, what am I missing here? Any help is appreciated.
I have been trying to get an SSL certificate for a site using LetsEncrypt, "a free, automated, and open certificate authority (CA), run for the public’s benefit". There is an ACME shell script that is meant to make the process of using LetsEncrypts API easier to receive an SSL certificate. One of their methods requires you to enter in your domain name, and the webroot of your application.
acme.sh --issue -d example.com -w /home/wwwroot/example.com
However, when I try to enter this command, it says that it was unable to verify the domain. I added a --debug flag to the script command, and received this, but am not sure where the problem lies.
[Mon Sep 11 05:05:01 UTC 2017] Using config home:/home/doc4design/.acme.sh
[Mon Sep 11 05:05:01 UTC 2017] DOMAIN_PATH='/home/doc4design/.acme.sh/doc4design.com'
[Mon Sep 11 05:05:01 UTC 2017] Using ACME_DIRECTORY: https://acme-v01.api.letsencrypt.org/directory
[Mon Sep 11 05:05:01 UTC 2017] _init api for server: https://acme-v01.api.letsencrypt.org/directory
[Mon Sep 11 05:05:01 UTC 2017] ACME_KEY_CHANGE='https://acme-v01.api.letsencrypt.org/acme/key-change'
[Mon Sep 11 05:05:01 UTC 2017] ACME_NEW_AUTHZ='https://acme-v01.api.letsencrypt.org/acme/new-authz'
[Mon Sep 11 05:05:01 UTC 2017] ACME_NEW_ORDER='https://acme-v01.api.letsencrypt.org/acme/new-cert'
[Mon Sep 11 05:05:01 UTC 2017] ACME_NEW_ACCOUNT='https://acme-v01.api.letsencrypt.org/acme/new-reg'
[Mon Sep 11 05:05:01 UTC 2017] ACME_REVOKE_CERT='https://acme-v01.api.letsencrypt.org/acme/revoke-cert'
[Mon Sep 11 05:05:01 UTC 2017] Le_NextRenewTime
[Mon Sep 11 05:05:01 UTC 2017] _on_before_issue
[Mon Sep 11 05:05:01 UTC 2017] Le_LocalAddress
[Mon Sep 11 05:05:01 UTC 2017] Check for domain='doc4design.com'
[Mon Sep 11 05:05:02 UTC 2017] _currentRoot='/home/doc4design/webapps/django_2016/doc4_2016'
[Mon Sep 11 05:05:02 UTC 2017] _saved_account_key_hash is not changed, skip register account.
[Mon Sep 11 05:05:02 UTC 2017] Read key length:
[Mon Sep 11 05:05:02 UTC 2017] _createcsr
[Mon Sep 11 05:05:02 UTC 2017] Single domain='doc4design.com'
[Mon Sep 11 05:05:02 UTC 2017] Getting domain auth token for each domain
[Mon Sep 11 05:05:02 UTC 2017] Getting webroot for domain='doc4design.com'
[Mon Sep 11 05:05:02 UTC 2017] _w='/home/doc4design/webapps/django_2016/doc4_2016'
[Mon Sep 11 05:05:02 UTC 2017] _currentRoot='/home/doc4design/webapps/django_2016/doc4_2016'
[Mon Sep 11 05:05:02 UTC 2017] Getting new-authz for domain='doc4design.com'
[Mon Sep 11 05:05:02 UTC 2017] _init api for server: https://acme-v01.api.letsencrypt.org/directory
[Mon Sep 11 05:05:02 UTC 2017] ACME_KEY_CHANGE='https://acme-v01.api.letsencrypt.org/acme/key-change'
[Mon Sep 11 05:05:02 UTC 2017] ACME_NEW_AUTHZ='https://acme-v01.api.letsencrypt.org/acme/new-authz'
[Mon Sep 11 05:05:02 UTC 2017] ACME_NEW_ORDER='https://acme-v01.api.letsencrypt.org/acme/new-cert'
[Mon Sep 11 05:05:02 UTC 2017] ACME_NEW_ACCOUNT='https://acme-v01.api.letsencrypt.org/acme/new-reg'
[Mon Sep 11 05:05:02 UTC 2017] ACME_REVOKE_CERT='https://acme-v01.api.letsencrypt.org/acme/revoke-cert'
[Mon Sep 11 05:05:02 UTC 2017] Try new-authz for the 0 time.
[Mon Sep 11 05:05:02 UTC 2017] url='https://acme-v01.api.letsencrypt.org/acme/new-authz'
[Mon Sep 11 05:05:02 UTC 2017] payload='{"resource": "new-authz", "identifier": {"type": "dns", "value": "doc4design.com"}}'
[Mon Sep 11 05:05:02 UTC 2017] RSA key
[Mon Sep 11 05:05:02 UTC 2017] GET
[Mon Sep 11 05:05:02 UTC 2017] url='https://acme-v01.api.letsencrypt.org/directory'
[Mon Sep 11 05:05:02 UTC 2017] timeout
[Mon Sep 11 05:05:02 UTC 2017] _CURL='curl -L --silent --dump-header /home/doc4design/.acme.sh/http.header '
[Mon Sep 11 05:05:02 UTC 2017] ret='0'
[Mon Sep 11 05:05:02 UTC 2017] POST
[Mon Sep 11 05:05:02 UTC 2017] url='https://acme-v01.api.letsencrypt.org/acme/new-authz'
[Mon Sep 11 05:05:02 UTC 2017] _CURL='curl -L --silent --dump-header /home/doc4design/.acme.sh/http.header '
[Mon Sep 11 05:05:03 UTC 2017] _ret='0'
[Mon Sep 11 05:05:03 UTC 2017] code='201'
[Mon Sep 11 05:05:03 UTC 2017] The new-authz request is ok.
[Mon Sep 11 05:05:03 UTC 2017] entry='"type":"http-01","status":"pending","uri":"https://acme-v01.api.letsencrypt.org/acme/challenge/7hHtQgJ6i3H5IplHkU8zq-2n6TVLuUuhN5K9M71nZ8I/1959333012","token":"jSwY3$
[Mon Sep 11 05:05:03 UTC 2017] token='jSwY3zdodjpOfh1m6iz1SWNZFFSKnfqdkzj8Cc6Dl2c'
[Mon Sep 11 05:05:03 UTC 2017] uri='https://acme-v01.api.letsencrypt.org/acme/challenge/7hHtQgJ6i3H5IplHkU8zq-2n6TVLuUuhN5K9M71nZ8I/1959333012'
[Mon Sep 11 05:05:03 UTC 2017] keyauthorization='jSwY3zdodjpOfh1m6iz1SWNZFFSKnfqdkzj8Cc6Dl2c.KZ04ehApOrSMwkeVbG2UT-klFpwOPf_pDEdqVcHf4XM'
[Mon Sep 11 05:05:03 UTC 2017] dvlist='doc4design.com#jSwY3zdodjpOfh1m6iz1SWNZFFSKnfqdkzj8Cc6Dl2c.KZ04ehApOrSMwkeVbG2UT-klFpwOPf_pDEdqVcHf4XM#https://acme-v01.api.letsencrypt.org/acme/challenge/7hHtQgJ6i$
[Mon Sep 11 05:05:03 UTC 2017] vlist='doc4design.com#jSwY3zdodjpOfh1m6iz1SWNZFFSKnfqdkzj8Cc6Dl2c.KZ04ehApOrSMwkeVbG2UT-klFpwOPf_pDEdqVcHf4XM#https://acme-v01.api.letsencrypt.org/acme/challenge/7hHtQgJ6i3$
[Mon Sep 11 05:05:03 UTC 2017] ok, let's start to verify
[Mon Sep 11 05:05:03 UTC 2017] Verifying:doc4design.com
[Mon Sep 11 05:05:03 UTC 2017] d='doc4design.com'
[Mon Sep 11 05:05:03 UTC 2017] keyauthorization='jSwY3zdodjpOfh1m6iz1SWNZFFSKnfqdkzj8Cc6Dl2c.KZ04ehApOrSMwkeVbG2UT-klFpwOPf_pDEdqVcHf4XM'
[Mon Sep 11 05:05:03 UTC 2017] uri='https://acme-v01.api.letsencrypt.org/acme/challenge/7hHtQgJ6i3H5IplHkU8zq-2n6TVLuUuhN5K9M71nZ8I/1959333012'
[Mon Sep 11 05:05:03 UTC 2017] _currentRoot='/home/doc4design/webapps/django_2016/doc4_2016'
[Mon Sep 11 05:05:02 UTC 2017] ACME_REVOKE_CERT='https://acme-v01.api.letsencrypt.org/acme/revoke-cert'
[Mon Sep 11 05:05:02 UTC 2017] Try new-authz for the 0 time.
[Mon Sep 11 05:05:02 UTC 2017] url='https://acme-v01.api.letsencrypt.org/acme/new-authz'
[Mon Sep 11 05:05:02 UTC 2017] payload='{"resource": "new-authz", "identifier": {"type": "dns", "value": "doc4design.com"}}'
[Mon Sep 11 05:05:02 UTC 2017] RSA key
[Mon Sep 11 05:05:02 UTC 2017] GET
[Mon Sep 11 05:05:02 UTC 2017] url='https://acme-v01.api.letsencrypt.org/directory'
[Mon Sep 11 05:05:02 UTC 2017] timeout
[Mon Sep 11 05:05:02 UTC 2017] _CURL='curl -L --silent --dump-header /home/doc4design/.acme.sh/http.header '
[Mon Sep 11 05:05:02 UTC 2017] ret='0'
[Mon Sep 11 05:05:02 UTC 2017] POST
[Mon Sep 11 05:05:02 UTC 2017] url='https://acme-v01.api.letsencrypt.org/acme/new-authz'
[Mon Sep 11 05:05:02 UTC 2017] _CURL='curl -L --silent --dump-header /home/doc4design/.acme.sh/http.header '
[Mon Sep 11 05:05:03 UTC 2017] _ret='0'
[Mon Sep 11 05:05:03 UTC 2017] code='201'
[Mon Sep 11 05:05:03 UTC 2017] The new-authz request is ok.
[Mon Sep 11 05:05:03 UTC 2017] entry='"type":"http-01","status":"pending","uri":"https://acme-v01.api.letsencrypt.org/acme/challenge/7hHtQgJ6i3H5IplHkU8zq-2n6TVLuUuhN5K9M71nZ8I/1959333012","token":"jSwY3$
[Mon Sep 11 05:05:03 UTC 2017] token='jSwY3zdodjpOfh1m6iz1SWNZFFSKnfqdkzj8Cc6Dl2c'
[Mon Sep 11 05:05:03 UTC 2017] uri='https://acme-v01.api.letsencrypt.org/acme/challenge/7hHtQgJ6i3H5IplHkU8zq-2n6TVLuUuhN5K9M71nZ8I/1959333012'
[Mon Sep 11 05:05:03 UTC 2017] keyauthorization='jSwY3zdodjpOfh1m6iz1SWNZFFSKnfqdkzj8Cc6Dl2c.KZ04ehApOrSMwkeVbG2UT-klFpwOPf_pDEdqVcHf4XM'
[Mon Sep 11 05:05:03 UTC 2017] dvlist='doc4design.com#jSwY3zdodjpOfh1m6iz1SWNZFFSKnfqdkzj8Cc6Dl2c.KZ04ehApOrSMwkeVbG2UT-klFpwOPf_pDEdqVcHf4XM#https://acme-v01.api.letsencrypt.org/acme/challenge/7hHtQgJ6i$
[Mon Sep 11 05:05:03 UTC 2017] vlist='doc4design.com#jSwY3zdodjpOfh1m6iz1SWNZFFSKnfqdkzj8Cc6Dl2c.KZ04ehApOrSMwkeVbG2UT-klFpwOPf_pDEdqVcHf4XM#https://acme-v01.api.letsencrypt.org/acme/challenge/7hHtQgJ6i3$
[Mon Sep 11 05:05:03 UTC 2017] ok, let's start to verify
[Mon Sep 11 05:05:03 UTC 2017] Verifying:doc4design.com
[Mon Sep 11 05:05:03 UTC 2017] d='doc4design.com'
[Mon Sep 11 05:05:03 UTC 2017] keyauthorization='jSwY3zdodjpOfh1m6iz1SWNZFFSKnfqdkzj8Cc6Dl2c.KZ04ehApOrSMwkeVbG2UT-klFpwOPf_pDEdqVcHf4XM'
[Mon Sep 11 05:05:03 UTC 2017] uri='https://acme-v01.api.letsencrypt.org/acme/challenge/7hHtQgJ6i3H5IplHkU8zq-2n6TVLuUuhN5K9M71nZ8I/1959333012'
[Mon Sep 11 05:05:03 UTC 2017] _currentRoot='/home/doc4design/webapps/django_2016/doc4_2016'
[Mon Sep 11 05:05:03 UTC 2017] wellknown_path='/home/doc4design/webapps/django_2016/doc4_2016/.well-known/acme-challenge'
[Mon Sep 11 05:05:03 UTC 2017] writing token:jSwY3zdodjpOfh1m6iz1SWNZFFSKnfqdkzj8Cc6Dl2c to /home/doc4design/webapps/django_2016/doc4_2016/.well-known/acme-challenge/jSwY3zdodjpOfh1m6iz1SWNZFFSKnfqdkzj8C$
[Mon Sep 11 05:05:03 UTC 2017] Changing owner/group of .well-known to doc4design:doc4design
[Mon Sep 11 05:05:03 UTC 2017] url='https://acme-v01.api.letsencrypt.org/acme/challenge/7hHtQgJ6i3H5IplHkU8zq-2n6TVLuUuhN5K9M71nZ8I/1959333012'
[Mon Sep 11 05:05:03 UTC 2017] payload='{"resource": "challenge", "keyAuthorization": "jSwY3zdodjpOfh1m6iz1SWNZFFSKnfqdkzj8Cc6Dl2c.KZ04ehApOrSMwkeVbG2UT-klFpwOPf_pDEdqVcHf4XM"}'
[Mon Sep 11 05:05:03 UTC 2017] POST
[Mon Sep 11 05:05:03 UTC 2017] url='https://acme-v01.api.letsencrypt.org/acme/challenge/7hHtQgJ6i3H5IplHkU8zq-2n6TVLuUuhN5K9M71nZ8I/1959333012'
[Mon Sep 11 05:05:03 UTC 2017] _CURL='curl -L --silent --dump-header /home/doc4design/.acme.sh/http.header '
[Mon Sep 11 05:05:03 UTC 2017] _ret='0'
[Mon Sep 11 05:05:03 UTC 2017] code='202'
[Mon Sep 11 05:05:03 UTC 2017] sleep 2 secs to verify
[Mon Sep 11 05:05:05 UTC 2017] checking
[Mon Sep 11 05:05:05 UTC 2017] GET
[Mon Sep 11 05:05:05 UTC 2017] url='https://acme-v01.api.letsencrypt.org/acme/challenge/7hHtQgJ6i3H5IplHkU8zq-2n6TVLuUuhN5K9M71nZ8I/1959333012'
[Mon Sep 11 05:05:05 UTC 2017] timeout
[Mon Sep 11 05:05:05 UTC 2017] _CURL='curl -L --silent --dump-header /home/doc4design/.acme.sh/http.header '
[Mon Sep 11 05:05:06 UTC 2017] ret='0'
[Mon Sep 11 05:05:06 UTC 2017] doc4design.com:Verify error:Invalid response from http://doc4design.com/.well-known/acme-challenge/jSwY3zdodjpOfh1m6iz1SWNZFFSKnfqdkzj8Cc6Dl2c:
[Mon Sep 11 05:05:06 UTC 2017] pid
[Mon Sep 11 05:05:06 UTC 2017] No need to restore nginx, skip.
[Mon Sep 11 05:05:06 UTC 2017] _clearupdns
[Mon Sep 11 05:05:06 UTC 2017] skip dns.
[Mon Sep 11 05:05:06 UTC 2017] _on_issue_err
[Mon Sep 11 05:05:06 UTC 2017] Please check log file for more details: /home/doc4design/.acme.sh/acme.sh.log
[Mon Sep 11 05:05:06 UTC 2017] url='https://acme-v01.api.letsencrypt.org/acme/challenge/7hHtQgJ6i3H5IplHkU8zq-2n6TVLuUuhN5K9M71nZ8I/1959333012'
[Mon Sep 11 05:05:06 UTC 2017] payload='{"resource": "challenge", "keyAuthorization": "jSwY3zdodjpOfh1m6iz1SWNZFFSKnfqdkzj8Cc6Dl2c.KZ04ehApOrSMwkeVbG2UT-klFpwOPf_pDEdqVcHf4XM"}'
[Mon Sep 11 05:05:06 UTC 2017] POST
[Mon Sep 11 05:05:06 UTC 2017] url='https://acme-v01.api.letsencrypt.org/acme/challenge/7hHtQgJ6i3H5IplHkU8zq-2n6TVLuUuhN5K9M71nZ8I/1959333012'
[Mon Sep 11 05:05:06 UTC 2017] _CURL='curl -L --silent --dump-header /home/doc4design/.acme.sh/http.header '
[Mon Sep 11 05:05:06 UTC 2017] _ret='0'
[Mon Sep 11 05:05:03 UTC 2017] Changing owner/group of .well-known to doc4design:doc4design
[Mon Sep 11 05:05:03 UTC 2017] url='https://acme-v01.api.letsencrypt.org/acme/challenge/7hHtQgJ6i3H5IplHkU8zq-2n6TVLuUuhN5K9M71nZ8I/1959333012'
[Mon Sep 11 05:05:03 UTC 2017] payload='{"resource": "challenge", "keyAuthorization": "jSwY3zdodjpOfh1m6iz1SWNZFFSKnfqdkzj8Cc6Dl2c.KZ04ehApOrSMwkeVbG2UT-klFpwOPf_pDEdqVcHf4XM"}'
[Mon Sep 11 05:05:03 UTC 2017] POST
[Mon Sep 11 05:05:03 UTC 2017] url='https://acme-v01.api.letsencrypt.org/acme/challenge/7hHtQgJ6i3H5IplHkU8zq-2n6TVLuUuhN5K9M71nZ8I/1959333012'
[Mon Sep 11 05:05:03 UTC 2017] _CURL='curl -L --silent --dump-header /home/doc4design/.acme.sh/http.header '
[Mon Sep 11 05:05:03 UTC 2017] _ret='0'
[Mon Sep 11 05:05:03 UTC 2017] code='202'
[Mon Sep 11 05:05:03 UTC 2017] sleep 2 secs to verify
[Mon Sep 11 05:05:05 UTC 2017] checking
[Mon Sep 11 05:05:05 UTC 2017] GET
[Mon Sep 11 05:05:05 UTC 2017] url='https://acme-v01.api.letsencrypt.org/acme/challenge/7hHtQgJ6i3H5IplHkU8zq-2n6TVLuUuhN5K9M71nZ8I/1959333012'
[Mon Sep 11 05:05:05 UTC 2017] timeout
[Mon Sep 11 05:05:05 UTC 2017] _CURL='curl -L --silent --dump-header /home/doc4design/.acme.sh/http.header '
[Mon Sep 11 05:05:06 UTC 2017] ret='0'
[Mon Sep 11 05:05:06 UTC 2017] doc4design.com:Verify error:Invalid response from http://doc4design.com/.well-known/acme-challenge/jSwY3zdodjpOfh1m6iz1SWNZFFSKnfqdkzj8Cc6Dl2c:
[Mon Sep 11 05:05:06 UTC 2017] pid
[Mon Sep 11 05:05:06 UTC 2017] No need to restore nginx, skip.
[Mon Sep 11 05:05:06 UTC 2017] _clearupdns
[Mon Sep 11 05:05:06 UTC 2017] skip dns.
[Mon Sep 11 05:05:06 UTC 2017] _on_issue_err
[Mon Sep 11 05:05:06 UTC 2017] Please check log file for more details: /home/doc4design/.acme.sh/acme.sh.log
[Mon Sep 11 05:05:06 UTC 2017] url='https://acme-v01.api.letsencrypt.org/acme/challenge/7hHtQgJ6i3H5IplHkU8zq-2n6TVLuUuhN5K9M71nZ8I/1959333012'
[Mon Sep 11 05:05:06 UTC 2017] payload='{"resource": "challenge", "keyAuthorization": "jSwY3zdodjpOfh1m6iz1SWNZFFSKnfqdkzj8Cc6Dl2c.KZ04ehApOrSMwkeVbG2UT-klFpwOPf_pDEdqVcHf4XM"}'
[Mon Sep 11 05:05:06 UTC 2017] POST
[Mon Sep 11 05:05:06 UTC 2017] url='https://acme-v01.api.letsencrypt.org/acme/challenge/7hHtQgJ6i3H5IplHkU8zq-2n6TVLuUuhN5K9M71nZ8I/1959333012'
[Mon Sep 11 05:05:06 UTC 2017] _CURL='curl -L --silent --dump-header /home/doc4design/.acme.sh/http.header '
[Mon Sep 11 05:05:06 UTC 2017] _ret='0'
[Mon Sep 11 05:05:06 UTC 2017] code='400'
Could someone who is familiar with LetsEncrypt shed some light on why LetsEncrypt can't verify my site, and issue me an SSL certificate ?
The problem is stated on this line:
[Mon Sep 11 05:05:06 UTC 2017] doc4design.com:Verify error:Invalid response from http://doc4design.com/.well-known/acme-challenge/jSwY3zdodjpOfh1m6iz1SWNZFFSKnfqdkzj8Cc6Dl2c:
The issue is that for whatever reason, external traffic cannot access the file at http://doc4design.com/.well-known/acme-challenge/jSwY3zdodjpOfh1m6iz1SWNZFFSKnfqdkzj8Cc6Dl2c, which was presumably placed on the filesystem in /home/wwwroot/example.com/.well-known/acme-challenge/jSwY3zdodjpOfh1m6iz1SWNZFFSKnfqdkzj8Cc6Dl2c.
That file needs to be externally accessible at the given URL.
I had this on webfaction.
I see you also have a Django install.
Do you have a separate webapp to serve the static assets?
In my case, I had to place the LetyEncrypt generated file in the same directory where the STATIC assets are located.
I personally settled for this letsencrypt webfaction script last year.
LetsEncrypt utility client for WebFaction hosts
https://github.com/will-in-wi/letsencrypt-webfaction
I have it configured for 2 domains, and last time I checked the LetsEncrypt certificates were renewed automatically.
you can add --debug 2 to get a more detail debug info:
acme.sh --issue -d example.com -w /home/wwwroot/example.com --debug 2
from the log above, I guess it's related to ipv6. your domain has ipv6 AAAA record resolved. Is your website listening at ipv6 ?
just for test, I would like to block all traffic to my website not coming from Android browser using fail2ban.
This is the string in the log file:
GET http://www.aaaaa.com/video/09_12_2014_spot_app.mp4 - ORIGINAL_DST/171.171.171.171 video/mp4
[
User-Agent: stagefright/1.2 (Linux;Android 5.0)
Cookie: _gat=1; _ga=GA1.2.909922659.1455111791
Range: bytes=705201-
Connection: Keep-Alive
Accept-Encoding: gzip
Host: www.aaaaa.com
]
[
HTTP/1.1 206 Partial Content
Date: Thu, 26 May 2016 15:27:16 GMT
Server: Apache/2.2.15 (CentOS)
Last-Modified: Tue, 09 Dec 2014 19:55:17 GMT
ETag: "2b739f-ec2b1-509cdec1610e2"
Accept-Ranges: bytes
Content-Length: 262144
Content-Range: bytes 705201-967344/967345
Connection: close
Content-Type: video/mp4
]
Any help? Thank you in advance!
I'll try found question, but I couldn't.
I'll try to deploy my application to CloudBees platform.
In my application.conf file I set params:
###############################################################
# Production config ###########################################
###############################################################
%production.application.mode=prod
%production.jpa.ddl=create
%production.db.url="jdbc:mysql:"${MYSQL_URL_EASYBOOKDB}
%production.db.driver=com.mysql.jdbc.Driver
%production.db.user=${MYSQL_USERNAME_EASYBOOKDB}
%production.db.pass=${MYSQL_PASSWORD_EASYBOOKDB}
before that, i linked my app with db
bees app:bind -db easybook -a zolt/easybook -as easybookdb
I have installed cloudbees module for playframework.
I deploy my app, like that:
play bees:app:deploy --%production
have that answer:
upload complete, response=<?xml version="1.0" encoding="UTF-8"?>
<ApplicationDeployArchiveResponse>
<id>zolt/easybook</id>
<url>http://easybook.zolt.cloudbees.net</url>
</ApplicationDeployArchiveResponse>
Application zolt/easybook deployed: http://easybook.zolt.cloudbees.net
after that, i go to link http://easybook.zolt.cloudbees.net and see tomcat error page...
in log i see that stacktrace:
SEVERE: Exception sending context initialized event to listener instance of class play.server.ServletWrapper
Jan 07 02:56:58 easybook i-9cd9d7e1: play.exceptions.DatabaseException: Cannot connected to the database, Communications link failure
Jan 07 02:56:58 easybook i-9cd9d7e1: The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.
Jan 07 02:56:58 easybook i-9cd9d7e1: at play.db.DBPlugin.onApplicationStart(DBPlugin.java:161)
Jan 07 02:56:58 easybook i-9cd9d7e1: at play.plugins.PluginCollection.onApplicationStart(PluginCollection.java:525)
Jan 07 02:56:58 easybook i-9cd9d7e1: at play.Play.start(Play.java:533)
Jan 07 02:56:58 easybook i-9cd9d7e1: at play.Play.init(Play.java:305)
Jan 07 02:56:58 easybook i-9cd9d7e1: at play.server.ServletWrapper.contextInitialized(ServletWrapper.java:78)
Jan 07 02:56:58 easybook i-9cd9d7e1: at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4206)
Jan 07 02:56:58 easybook i-9cd9d7e1: at org.apache.catalina.core.StandardContext.start(StandardContext.java:4705)
Jan 07 02:56:58 easybook i-9cd9d7e1: at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1057)
Jan 07 02:56:58 easybook i-9cd9d7e1: at org.apache.catalina.core.StandardHost.start(StandardHost.java:840)
Jan 07 02:56:58 easybook i-9cd9d7e1: at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1057)
Jan 07 02:56:58 easybook i-9cd9d7e1: at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:463)
Jan 07 02:56:58 easybook i-9cd9d7e1: at org.apache.catalina.startup.Embedded.start(Embedded.java:825)
Jan 07 02:56:58 easybook i-9cd9d7e1: at com.staxnet.appserver.TomcatServerBase.startContainer(TomcatServerBase.java:120)
Jan 07 02:56:58 easybook i-9cd9d7e1: at com.staxnet.appserver.TomcatServerBase.start(TomcatServerBase.java:190)
Jan 07 02:56:58 easybook i-9cd9d7e1: at com.staxnet.appserver.StaxAppServer.main(StaxAppServer.java:89)
Jan 07 02:56:58 easybook i-9cd9d7e1: at com.staxnet.appserver.SnazAppServer.main(SnazAppServer.java:26)
Jan 07 02:56:58 easybook i-9cd9d7e1: at net.stax.appserver.bootstrap.Bootstrap.invokeAppServerMain(Bootstrap.java:41)
Jan 07 02:56:58 easybook i-9cd9d7e1: at net.stax.appserver.bootstrap.Bootstrap.main(Bootstrap.java:30)
Jan 07 02:56:58 easybook i-9cd9d7e1: Caused by: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure
Jan 07 02:56:58 easybook i-9cd9d7e1: The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.
Jan 07 02:56:58 easybook i-9cd9d7e1: at com.mysql.jdbc.Util.handleNewInstance(Util.java:411)
Jan 07 02:56:58 easybook i-9cd9d7e1: at com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:1116)
Jan 07 02:56:58 easybook i-9cd9d7e1: at com.mysql.jdbc.MysqlIO.<init>(MysqlIO.java:348)
Jan 07 02:56:58 easybook i-9cd9d7e1: at com.mysql.jdbc.ConnectionImpl.coreConnect(ConnectionImpl.java:2391)
Jan 07 02:56:58 easybook i-9cd9d7e1: at com.mysql.jdbc.ConnectionImpl.connectOneTryOnly(ConnectionImpl.java:2428)
Jan 07 02:56:58 easybook i-9cd9d7e1: at com.mysql.jdbc.ConnectionImpl.createNewIO(ConnectionImpl.java:2213)
Jan 07 02:56:58 easybook i-9cd9d7e1: at com.mysql.jdbc.ConnectionImpl.<init>(ConnectionImpl.java:797)
Jan 07 02:56:58 easybook i-9cd9d7e1: at com.mysql.jdbc.JDBC4Connection.<init>(JDBC4Connection.java:47)
Jan 07 02:56:58 easybook i-9cd9d7e1: at com.mysql.jdbc.Util.handleNewInstance(Util.java:411)
Jan 07 02:56:58 easybook i-9cd9d7e1: at com.mysql.jdbc.ConnectionImpl.getInstance(ConnectionImpl.java:389)
Jan 07 02:56:58 easybook i-9cd9d7e1: at com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:305)
Jan 07 02:56:58 easybook i-9cd9d7e1: at java.sql.DriverManager.getConnection(Unknown Source)
Jan 07 02:56:58 easybook i-9cd9d7e1: at java.sql.DriverManager.getConnection(Unknown Source)
Jan 07 02:56:58 easybook i-9cd9d7e1: at play.db.DBPlugin.onApplicationStart(DBPlugin.java:109)
Jan 07 02:56:58 easybook i-9cd9d7e1: ... 17 more
Jan 07 02:56:58 easybook i-9cd9d7e1: Caused by: java.net.ConnectException: Connection refused
Jan 07 02:56:58 easybook i-9cd9d7e1: at java.net.PlainSocketImpl.socketConnect(Native Method)
Jan 07 02:56:58 easybook i-9cd9d7e1: at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)
Jan 07 02:56:58 easybook i-9cd9d7e1: at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source)
Jan 07 02:56:58 easybook i-9cd9d7e1: at java.net.AbstractPlainSocketImpl.connect(Unknown Source)
Jan 07 02:56:58 easybook i-9cd9d7e1: at java.net.SocksSocketImpl.connect(Unknown Source)
Jan 07 02:56:58 easybook i-9cd9d7e1: at java.net.Socket.connect(Unknown Source)
Jan 07 02:56:58 easybook i-9cd9d7e1: at java.net.Socket.connect(Unknown Source)
Jan 07 02:56:58 easybook i-9cd9d7e1: at java.net.Socket.<init>(Unknown Source)
Jan 07 02:56:58 easybook i-9cd9d7e1: at java.net.Socket.<init>(Unknown Source)
Jan 07 02:56:58 easybook i-9cd9d7e1: at com.mysql.jdbc.StandardSocketFactory.connect(StandardSocketFactory.java:257)
Jan 07 02:56:58 easybook i-9cd9d7e1: at com.mysql.jdbc.MysqlIO.<init>(MysqlIO.java:298)
Jan 07 02:56:58 easybook i-9cd9d7e1: ... 28 more
Jan 07 02:56:58 easybook i-9cd9d7e1: Jan 07, 2014 10:56:57 AM org.apache.catalina.core.StandardContext start
Jan 07 02:56:58 easybook i-9cd9d7e1: SEVERE: Error listenerStart
if i try connect to DB over MysqWorkbench it's all fine...
what am I doing wrong?
I think you are not binding your database with your application in the right way.
According with Play1 ClickStart in which the database binding is working. These are the steps:
1.In application.conf you should have this:
db=java:comp/env/jdbc/mydb
jpa.dialect=org.hibernate.dialect.MySQL5Dialect
2.Bind the application to the database
$bees app:bind -a appName -db dbName -as mydb
3.Redeploy the application
bees app:deploy -a MY_APP -t tomcat7 myapp.war
Official documentation about Play1 is here.