can you access .well-known/acme-challenge/test.txt ?
maz
peppy
Edited
I got the HTTP version working so I could test the files. At the moment, I can access a file such as:
http://ex.mysite.com/.well-known/acme-challenge/test.txt
saved in linux filesystem at:
/home/username/app/assets/static/.well-known/acme-challenge/test.txt
However, that is a static file. certbot is trying to create and access a randomly generated file that it creates:
/.well-known/acme-challenge/SA9wcsbj4wLBl1OfSsb75bQQl9hTuHwzRlk7rEgp3bE
and I end up with this error:
[debug] ** (Phoenix.Router.NoRouteError) no route found for GET /.well-known/acme-challenge/osotlOoymnQdsQfpEnsTNrHTUwmHycKJT6v0Q6lXRms (ExchatWeb.Router)
How do we get certbot / LetsEncrypt to create the file and do the tests so I can get an SSL certificate?
0
maz
Can you access .well-known/test.txt On prod? If you don’t get a Route error here then it’s not a router issue.
Another idea might be to add acme-challenge to the plug(only: ~w) strings.
Another thing that could be an issue is the permissions of .well-known and acme-challenge
0
peppy
maz
No problem. Can you share your fix so when someone discovers this thread they can get up-and-running quickly?
0
peppy
Sure, no problem. Basically, I came across a good solution here: https://stackoverflow.com/questions/37216626/elixir-phoenix-production-server-has-issue-with-letsencrypt-renewal
In the router.ex file, I set up a snipet for the .well-known directory:
scope "/.well-known", MyAppWeb do
pipe_through :browser
get "/acme-challenge/:challenge", AcmeChallengeController, :show
end
and then a new controller letsencrypt.ex:
defmodule MyAppWeb.AcmeChallengeController do
use MyAppWeb, :controller
def show(conn, %{"challenge" => "the_random_file_name"}) do
send_resp(conn, 200, "TheHashInTheFile")
end
def show(conn, _) do
send_resp(conn, 200, "Not valid")
end
end
Lastly, you’ll need to do the certbot call using the /assets/static (or /priv/static) directory as the web root:
sudo certbot --authenticator webroot --webroot-path /home/username/myapp/assets/static --installer apache -n -d ex.mysite.com
Once that is done, everything was made fun for the long haul.
1