I was having issues with the custom domain generator to create subdomains with my existing base domain. I don't know if it's a wizard bug but wondering if anyone else experienced the same issue?
5 replies
tomspark wrote:
Could be — and if it is, I want to fix it, so thanks for flagging. You haven't broken anything either way. To tell whether it's the wizard or something on the domain side, I need to see what it actually said when it failed. Can you paste the exact message that came up when you tried to create the subdomain (screenshot works too)? Also helpful: which subdomain you were making (like watch.yourdomain.com) and whether it failed instantly or after a minute or so. With that I can point you at exactly what's going on.
knguyn02 wrote:
This is what I see when I try generating the custom domains
tomspark wrote:
Thanks for the screenshot—we can see exactly what's happening. We're looking into this and will follow up as soon as we have answers. You haven't broken anything on your end, so no worries there. Appreciate you flagging this!
tomspark wrote:
Good news first: your domain is fine. That error message is our bug — it blames the domain name when the real problem is something else. Since every single one failed with the exact same wording, it looks like SparkBox couldn't talk to the part that sets up domains, and then reported it badly. I've filed that on our side already. To find the real cause on your box, run this and paste whatever comes back: sudo docker logs sb-dashboard 2&1 | grep -i "failed to set up domain" | tail -5 You should get a line or two with the real error hiding in it — paste them here and I'll give you the exact fix.
Chris wrote:
Coming back to this properly, and sorry it sat — Tom's instinct was right, and I can now name the cause. SparkBox has no domain-format check at all. That wording is a fallback in our error handling: when the dashboard's request to Nginx Proxy Manager fails, any error containing the word "invalid" — an NPM login failure, for example — gets reported as a bad domain name. So your names were never the problem. All 22 failed identically because one thing failed underneath, not twenty-two. The real error is in the dashboard's log: sudo docker logs sb-dashboard 2&1 | grep -i 'failed to set up domain' | tail -5 Paste whatever that prints and I'll take it from there. The misleading message is written up for Tom. — Chris