Question

APP Platform Laravel Wildcard Subdomain

Posted March 22, 2021 637 views
LaravelDigitalOcean App Platform

How do I achieve wildcard subdomain with my laravel application using DO app platform. It works fine using droplet and * A record.

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
Submit an Answer
2 answers

Hello @raynirola

If your domain nameserver is pointing to DigitalOcean then you can have to set add the domain and wildcard domain “*.example.com” in your app settings and required DNS records will be auto-generated. After DNS propagation time, the wildcard domain should start working.

In case your domain nameserver is not pointing to DigitalOcean then you have to follow one more step including adding the domain in the app settings. That is to point the domain CNAME record to app default subdomain provided by App Platform.

How to manage domain in App Platform

If the issue persists then please contact support with your domain name and APP ID for further help.

Regards,
Dikshith

Hi,

Actually I had the same problem, and it may take more then transferring your DNS name server to Digital Ocean and add the domain, then wildcard domain and expect just to work.

Let me explain what I’ve found out so far.

Digital Ocean APP platform uses CloudFlare and proxies the request throughout them, which is great as it adds extra security layer and DDOS protection, but when it comes to wildcard domain setting CNAME record is simply not enough. ColudFlare can fail proxy your wildcard domains, and you may end up with Error 1016 Origin DNS Error, even though your wildcard SSL certificate is valid.

It requires you to make additional changes in your DNS records. CloudFlare can only pass your wildcard subdomain if you are using “CNAME Flattening” (sometimes called an alias record, or ANAME). If you have the above error, please learn about CNAME Flattening.

I am happy that it was resolved on your side, but if someone else have the same problem, this might help.