Getting CHALLENGE FAILED

Help
41

I always try to do the reload

1 Like
42

graceful is the friendly reload :grin:

1 Like
43

what if I did a wildcard for covenantjourney.org

1 Like
44

Let's try this again. I expect no difference yet:

sudo certbot certonly --webroot -w /var/www/html/webroot -d "dashboard.covenantjourney.org" --dry-run

1 Like
45

i did that ... same difference :frowning:

1 Like
46

You could use a wildcard, but that would require DNS validation, which can be very annoying to automate.

1 Like
47

So who's hijacking the request? :thinking: Can you upload a copy of the main apache conf with a txt extension?

48

apache.txt (7.4 KB)
it's pretty generic

1 Like
49

Thanks. Taking a look. I've also made many more eyes aware of this topic.

1 Like
50

oh dear ... I am also texting the people involved with the software that is on the other end of apache to see if they are redirecting.

1 Like
51

You're positive there's no .htaccess file in either /var/www/html or /var/www/html/webroot?

1 Like
52

Has this file been shown?
[long thread]

1 Like
53

there is no .htaccess in /var/www/html
but there is one in webroot:

RewriteEngine on RewriteRule ^wpad.dat$ http://127.0.0.1/ [R=301,L,E=nolog:1] RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ index.php [QSA,L]
1 Like
54

Yep.

1 Like
55

Has apache been fully stopped and restarted?
[you must check for running processes after stopping it - if any remain, kill them]

1 Like
56

Can you upload that htaccess with a .txt extension and no period at the beginning?

1 Like
57

Yep. A graceful reload was performed.

That's not a full kill though, but it's a very busy server with many websites.

1 Like
58

htaccess.txt (269 Bytes)

1 Like
59

Yeah everyone says that.
No one is too busy to stop and fix what's broken!

1 Like
60

The htaccess file looks straightforward. Just a single file redirect and a directory to index redirect, both only when using https.

1 Like