I’ve been following the instructions provided in https://webtask.io/docs/custom-domain but I cannot seem to get the custom domain to work. Also, seems like there are other steps missing in the documentation to be able to fully customize the URL including the container name, for which Webtask CLI is needed.
Mainly the issue I’m facing is related to DNS configuration, and the requirement I have is to be able to have a friendly name for my default container similar to api.mydomain.com/container/endpoint.
Good morning Leo, I apologize for the delay but I haven’t heard anything back yet. As soon as I do I will be sure to share. I’m requesting feedback from a separate team today in hopes of finding out something
If by named webtasks you mean using the CLI, no I’m not. Had to use the web editor, otherwise changing the container name and the domain through the CLI would break its access. DNS settings are not clear to make it work.
I wanted to follow up on this @leo and confirm this has been successfully been accomplished in the past. You should be able to setup any reverse proxy in front of your webtask.io container using any reverse proxy tool like cloudfront. The reverse proxy basically acts like a legit MITM attack.
Touching base on this @leo, after talking with the team in charge of Webtask.io I was able to confirm that we no longer supporting the Custom Domain aspect Web task. Moving forward we will clean up the docs related to it as well. I apologize for any confusion
