I was trying to setup letsencrypt on my server but I am not able to verify my domain because elgg's .htaccess file is forbidding me to access a folder within the elgg directory and generating a 403 forbidden error.
Letsencrypt is asking to create ".well-known/acme-challenge/" folder and put a file inside that folder. When I am accessing that file via my browser it's showing me 403 forbidden error.
Is there any way to allow/open only the ".well-known/acme-challenge/" folder so that the folders/files in that directory is visible via my browser.
info@elgg.org
Security issues should be reported to security@elgg.org!
©2014 the Elgg Foundation
Elgg is a registered trademark of Thematic Networks.
Cover image by Raül Utrera is used under Creative Commons license.
Icons by Flaticon and FontAwesome.
- Rohit Gupta@Rohit_1990_3676

Rohit Gupta - 0 likes
- Rohit Gupta@Rohit_1990_3676

Rohit Gupta - 0 likes
- redirect all http://domain.com to https://www.domain.com
- redirect all http://www.domain.com to https://www.domain.com
- redirect all https://domain.com to https://www.domain.com
- Rohit Gupta@Rohit_1990_3676

Rohit Gupta - 0 likes
- Nikolai Shcherbin@rivervanrain

Nikolai Shcherbin - 1 like

- Rohit Gupta@Rohit_1990_3676

Rohit Gupta - 0 likes
- Steve Clay@steve_clay

Steve Clay - 0 likes
- Steve Clay@steve_clay

Steve Clay - 0 likes
You must log in to post replies.if I comment out "RewriteRule (^\.|/\.) - [F]" then i am able to access the .well-known/acme-challenge folder but I think this will leave other folder like .git open for exploits.
Any permanent solution?
I think this should also be included in core as letsencrypt is gaining popularity day by day and I am sure soon all of us will be using it.
2nd Question:
How to achieve the following:
So basically, all my traffic be it non-www or www will be redirected to SSL www domain.
Additionally, I have 2 subdomain that works on http, so I want to achieve the above and also keep the 2 subdomain free from the above redirect rule.
This is a silly requirement for LetsEncrypt. It's unwise to serve files/dirs starting with "."
Looks like it's a standard location. Made a ticket to make it easier.