This may seem like a fairly convoluted matter, but I would really appreciate some help because this is a very important matter for me. I'm not a system administrator, but I am trying to help a client deploy his Laravel site and I'm running into issues.
I am using Forge, connected to digital ocean via his API token. First, I created a droplet and deployed Laravel to it. Everything works great. He has pointed the domain to the droplet and I can access the site through the domain and IP address. Then, when I go to setup the SSL certificate, it tells me I need to enter something other than default in the domain name field. I put in the domain the website is hosted on (although it's not in the root directory of that host, not sure if this matters). All of a sudden, all of the pages on the site now start pointing to a 404 error. I change the site name back to default (which deletes the SSL certificate), so everything should be back to normal, and still getting 404 errors. Tried deploying again to no success.
If I need to start over I can, but how should I go about fixing this? I'm totally lost.
@tylerw Well, this is a trap that is well documented. You must delete the default site and create a new site. I usually create the site with a name that reflects your website like what-ever-your-site-is-called.com and then setup deployment all over again. You will have to enter the .env values once again because it is a new site and perform migrations etc. After all of that is done (you don't have to change the DNS again), then you can issue an SSL certificate. You can not use default site because the certificate authority cannot verify the site using the default.
