You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, first of all thanks for this plugin.
We have some issue, when we try to issue e certrificate we receive a 404.
The /.well-known folder not exists in the file system and is temporary created when we call a create method right?
If i manually create the folder and visit the url i can see the content correctly, there is something that we are missing.
Thanks for help
MM
The text was updated successfully, but these errors were encountered:
You somehow have to return a stored challenge whenever it it retrieved from the /.well-known/acme-challenge endpoint. You could do this by configuring NGINX/Apache appropriately or by registering a route:
Route::get('/.well-known/acme-challenge/{token}', function (string $token) {
return \Illuminate\Support\Facades\Storage::get('public/.well-known/acme-challenge/' . $token);
})
Sometimes the /.well-known/ prefix is disabled by default in the NGINX/Apache config (see #4). Make sure it is forwarded to your Laravel application if you want Laravel to return the challenge.
So you are responsible of returning the challenge yourself. Either by configuring Laravel to return it as shown above, or by letting NGINX/Apache return it as a static file.
Of course i read the docs and readme, an we set the route in laravel to return the challenge but we receive a 404 when we try to issue e certificate.
If we do a dd inside the route and we visit it from the browser is working.
Hello, first of all thanks for this plugin.
We have some issue, when we try to issue e certrificate we receive a 404.
The /.well-known folder not exists in the file system and is temporary created when we call a create method right?
If i manually create the folder and visit the url i can see the content correctly, there is something that we are missing.
Thanks for help
MM
The text was updated successfully, but these errors were encountered: