Level 61
I'm not sure I understand what changed there compared to successful previous deployments? Is it on the same server?
May 11, 2020
6
Level 7
Laravel Forge failing on wildcard ssl generation
I'm trying to setup a project that uses wildcard ssl for subdomains but the Let's encrypt is failing with the following message:
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
Failed to enable unit: Unit file docker.service does not exist.
I've deployed 2 more projects like this and never happened this before, so i'm guessing it may have something to do with the changes to the provisioning script. Maybe something is not being installed like the in old one.
My dns configuration is the same as always.
Any ideas for debugging this? Don't know where to start.
Level 7
Its a new server.
Last time was 1 year ago or so. That's why i'm thinking about something in the Forge's provisioning script.
Step 1: Set up Digital Ocean dns
Step 2: Create api token
Step 3: Forge SSL -> *.domain.com,domain.com ->DO token
Step 4: Error
Level 61
So it is a brand new server configured by Laravel Forge and it is failing?
Level 7
Yep. Brand new php 7.4, mysql 8 created from Forge.
Normal domain ssl is working fine. Wildcard ssl (with Digital Ocean) is crashing, tested it with multiple domains.
Level 61
Not sure what can change there. Write to customer support (Forge), you are a paying customer. They will reply what you are doing wrong.
Or create them manually.
Level 7
Still no idea. Support told me i should check my dns because the challenge was failing.
I decided to create a new server and it worked flawlessly. I always used the same config, so it should have worked. Anyways, don't know what happened to that server.
Please or to participate in this conversation.