Hey there, first of all, thanks for the amazing package.

Im trying to use it for creating ssl certs for clients of my saas app.

Basically after users register in the app, they get a custom subdomain, in the form: client1.myapp.com, client2.myapp.com.., etc. And they can use a CNAME to use a custom domain they bring, classic SAAS.

I configured a CNAME record which is reaching the app fine, but in this case when creating a certificate I am failing on the challenge step, not being able to validate the file in .well_known....

My routes file looks like this:

Route::group(['domain' => '{company:slug}.'.config('app.domain')], function () {
	Route::group(['middleware' => 'tenant'], function(){
		Route::get('', [HomeController::class, 'index']);

...
...

I'm using the config file as is, only updating the api_url to use the production one.

Checking in the server, i can't see any file created in public/.well_known.... Should I be able to see the file even if challenge fails? Maybe that's where i'm having the issue so the file is never uploaded...

Thanks in advance for any help!

root@files:/home/fs/public_html# php artisan lets-encrypt:create -d edulife.cmhlmc.com Generating certificates for 1 domains. edulife.cmhlmc.com: Failed to generate a certificate for edulife.cmhlmc.com Challenge failed (response: {"type":"http-01","status":"invalid","error":{"type":"urn:ietf:params:acme:error:unauthorized","detail":"66.45.249.26: Invalid response from http://edulife.cmhlmc.com/.well-known/acme-challenge/qCfxYAtN2NeQPm5WT1EIPTO5DBOX_u9YW3pp8VxChao: 404","status":403},"url":"https://acme-staging-v02.api.letsencrypt.org/acme/chall-v3/3123418344/UPLhFg","token":"qCfxYAtN2NeQPm5WT1EIPTO5DBOX_u9YW3pp8VxChao","validationRecord":[{"url":"http://edulife.cmhlmc.com/.well-known/acme-challenge/qCfxYAtN2NeQPm5WT1EIPTO5DBOX_u9YW3pp8VxChao","hostname":"edulife.cmhlmc.com","port":"80","addressesResolved":["66.45.249.26"],"addressUsed":"66.45.249.26"}],"validated":"2022-07-25T10:12:37Z"}).

Hello, I tried running the php artisan command but it returns the following error:

I saw the other thread with this error that was resolved by installing OpenSSL. I have got it enabled and php says it is enabled with a path to a openssl.cnf. The thing is that the path doesn't actually exist.

I don't know if that is why the command doesn't work? I am very new with certificates...

I am struggling to find a solution for a scope problem in the Laravel when you execute the command from the callback. From the Laravel command, I am trying to execute the job in a different context (multi-tenant platform, changing database and other settings). However, no matter what I tried, I all the time getting the error from the package. Reading through PHP manuals, StackOverflow and other articles, I tried bunch of different things such as:

• callable (https://www.php.net/manual/en/language.types.callable.php, How to call the callable function in PHP?)
• passing $this (Is there a workaround for $this within a closure in PHP 5.3?)
• passing $this by reference etc. However, none of these approaches worked in this case. What do you think that's causing this problem?

I must emphasize that I do not have a problem with scope in general - I have numerous commands which are executed in a dynamic context and everything runs without any problem. This error occurs only when I try to use this package in a callback

Expected result: Running job in correct Laravel context (changed by setup method in Instance model).

Actual result:

Using $this when not in object context at app/Models/Instance.php:80

Let me show you the problem:

Command:

class RenewExpiringCertificates extends Command {
  public function handle(): int {
      LetsEncryptCertificate::query()
          ->requiresRenewal()
          ->chunk(100, function (LetsEncryptCertificateCollection $certificates) {
              $certificates->renewNow();  // PROBLEMATIC CALL
          });

      return 0;
  }
  
  protected function execute(InputInterface $input, OutputInterface $output) {
      $method = method_exists($this, 'handle') ? 'handle' : '__invoke';

      $count = 0;
      Instance::inAllActiveSpaces(function () use ($method, &$count) {
          $count += $this->laravel->call([$this, $method]); // CALL TO HANDLE METHOD
      });

      return $count;
  }
}

Instance:

class Instance extends Model {
    protected $connection = 'mysql-master';

    public function setup() {
        Config::set('database.connections.mysql.database', $this->database);
        DB::reconnect('mysql');
        // ...
    }

    public static function inAllActiveSpaces($callback) {
        Instance::active()->each(function ($instance) use ($callback) {
            $instance->setup();
            $callback($instance);  // BREAKING POINT
        });
    }
}

From my research and looking into the source code, this looks to raise a problem:

// Daanra\LaravelLetsEncrypt\Models\LetsEncryptCertificate
public function renewNow(): self
{
    return LetsEncrypt::renewNow($this);
}

Kindly add support for laravel 9 & php 8

Your requirements could not be resolved to an installable set of packages.

Problem 1 - acmephp/core[dev-master, 1.3.0] require guzzlehttp/psr7 ^1.0 -> found guzzlehttp/psr7[1.0.0, ..., 1.x-dev] but the package is fixed to 2.2.1 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command. - acmephp/core 1.2.0 requires guzzlehttp/guzzle ^6.0 -> found guzzlehttp/guzzle[6.0.0, ..., 6.5.x-dev] but it conflicts with your root composer.json require (^7.0.1). - daanra/laravel-lets-encrypt v0.2.4 requires acmephp/core ^1.2|dev-master -> satisfiable by acmephp/core[dev-master, 1.2.0, 1.3.0]. - Root composer.json requires daanra/laravel-lets-encrypt ^0.2.4 -> satisfiable by daanra/laravel-lets-encrypt[v0.2.4].

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions. You can also try re-running composer require with an explicit version constraint, e.g. "composer require daanra/laravel-lets-encrypt:*" to figure out if any version is installable, or "composer require daanra/laravel-lets-encrypt:^2.1" if you know which you need.

As discussed in #22, this PR adds subjectAlternativeNames support.

The following is currently untested, but just wanted to check direction before I go any further.

Hi,

I'm wondering if this package supports sending SubjectAlternativeNames to LetsEncrypt / AcmePHP?

I can see that AcmePHP itself does have support for them, but I couldn't see any obvious references in this package.

EDIT: Our use case is for a multi-tenant Laravel application. we want one vhost per tenant rather than one per domain, so it makes sense to have a single SSL cert with all their active domains contained inside.

Please share correct nginx configuration. Default Laravel / nginx / apache install give 404 Not Found error when trying to access https://mydomain.com/.well-known/acme-challenge/any8Token8Typed8Here.

If I'm creating Laravel route with "dot" before "well-know" as it requires lets encrypt:

Route::get('/.well-known/acme-challenge/{token}', function (string $token) { <<<=== it doesn't work

Removing dot makes routes reachable but it is not something what lets encrypt expects:

Route::get('/well-known/acme-challenge/{token}', function (string $token) { <<<=== it works

For some reason /.well-known/acme-challenge/{token} is not served by laravel application, nginx doesn't allow this route. (But for example allows next: "/.well-known/acme-challenge")

Approach no. 2:

If nginx settings are not available, please help to understand how to put / return token from default "/public/.well-known/acme-challenge/....." folder

In documentation I clearly see: "You can customise this behavior by setting a custom PathGenerator class in your config under path_generator', but no further explanation how to create custom PathGenerator class.

I was wondering if it is possible o use this package to create SSL certificates for internally used domains that are not accessible from outside of our network. The domain is set using our own local DNS Server.

Right now when I try to create a certificate it returns the following:

Challenge failed (response: {"type":"http-01","status":"invalid","error":{"type":"urn:ietf:params:acme:error:unauthorized","detail":"91.184.0.100: Invalid response from http://labelsolutions..........nl/.well-known/acme-challenge/w9Js1qFOMkH9LH2Bp6jTJBZFNq79KM0ehuHuJ92MSd0: 404","status":403},"url":"https://acme-v02.api.letsencrypt.org/acme/chall-v3/174525676347/Y0Wtbw","token":"w9Js1qFOMkH9LH2Bp6jTJBZFNq79KM0ehuHuJ92MSd0","validationRecord":[{"url":"http://labelsolutions............nl/.well-known/acme-challenge/w9Js1qFOMkH9LH2Bp6jTJBZFNq79KM0ehuHuJ92MSd0","hostname":"labelsolutions..........nl","port":"80","addressesResolved":["91.184.0.100"],"addressUsed":"91.184.0.100"}],"validated":"2022-11-10T09:56:36Z"}).

I replaced the original domain name for dots, but the url for us internally is working.

Hello,

I don't understand how create jobs after successfully generate certificate. For example, I would like to create an apache virtualhost and add a row in database. I found this on website but I don't understand where is this job ?

[$certificate, $pendingDispatch] = \Daanra\LaravelLetsEncrypt\Facades\LetsEncrypt::create('mydomain.com', [ new CreateNewApacheVirtualHost('mydomain.com'), new ReloadApache(), new NotifyUserOfNewCertificate(request()->user()), ]);

Where is job CreateNewApacheVirtualHost ? How create this please ?

Hi, thank you fro the awesome package.

I have tried to install the package in laravel 5.5 project but not working. so i am wondering in which php version it was tested?

if you wondering what the errors: PHP Error: Call to undefined method Daanra/LaravelLetsEncrypt/Jobs/RegisterAccount::dispatchNow() second error BadMethodCallException with message 'Method ensureDirectoryExists does not exist.