3 months ago
Hi.
I have an issue with the TLS cert. for the wildcard domain configuration. I use cloudflare dns for my Django-Tenant App.
digitdesk.net has status setup complete but .digitdesk.net has status Issuing TLS certificate. I wait for more than 12 hours then I delete all and configure it again as other similar threads suggested. One of the threads escalated the problem.
All starts when the certificate expires and it didn’t update automatically.
I took the recommendations of threads to delete all records and done them again and now cannot use the app. digitdesk.net is working but *.digitdesk.net is not and the use of the app is through the subdomains.
Thanks Loukas
19 Replies
3 months ago
Hey there! We've found the following might help you get unblocked faster:
If you find the answer from one of these, please let us know by solving the thread!
3 months ago
I have seen all possible solutions and do step by step all recommendations but *.digitdesk stays on incomplete status
Status changed to Awaiting User Response Railway • 3 months ago
3 months ago
Hi and thank you for the support.
I just re-configured the domain config in railway and the dns on clouflare.
The digitdesk.net is completed and must give time to *.digitdesk.net
I’ll inform you with the results.
Status changed to Awaiting Railway Response Railway • 3 months ago
3 months ago
Cool! When your wildcard cert is done let us know.
Status changed to Awaiting User Response Railway • 3 months ago
3 months ago
More than 10 hours and waiting. This is unnormal behavior. Normally 30 minutes max to complete this process.
Attachments
Status changed to Awaiting Railway Response Railway • 3 months ago
3 months ago
Hello!
We're acknowledging your issue and attaching a ticket to this thread.
We don't have an ETA for it, but, our engineering team will take a look and you will be updated as we update the ticket.
Please reply to this thread if you have any questions!
3 months ago
I agree, I have raised a request to the platform team to investigate what could be the cause.
Status changed to Awaiting User Response Railway • 3 months ago
3 months ago
Hope for a solution ASAP
Status changed to Awaiting Railway Response Railway • 3 months ago
Status changed to Awaiting User Response Railway • 3 months ago
2 months ago
Good morning team.
I cannot wait to hear from you guy's. See that something is going on.
Attachments
Status changed to Awaiting Railway Response Railway • 3 months ago
2 months ago
We've had to disable all deployments on the platform due to this incident - apologies, we don't have an ETA for when it'll be up, but we will publish a post-mortem about this incident once it is resolved.
Thank you for the patience 
Status changed to Awaiting User Response Railway • 3 months ago
2 months ago
Any update?
Is a plan problem? Is anybody else with the same issue?
Status changed to Awaiting Railway Response Railway • 3 months ago
2 months ago
Hey there!
We had an incident earlier that is now resolved.
Status changed to Awaiting User Response Railway • 3 months ago
Status changed to Solved echohack • 3 months ago
13 days ago
🛠️ The ticket Certificate Issuance Delays has been marked as triage.
13 days ago
🛠️ The ticket Certificate Issuance Delay has been marked as triage.
13 days ago
🛠️ The ticket Certificate Issuance Delay has been marked as todo.
13 days ago
✅ The ticket Certificate Issuance Delay has been marked as completed.