@Joyce The links to specific documentation seem to be broken.
I set up www.foliodc.com for my site, but I would like to make it work without the “www” as well (foliodc.com). It is not clear how to do this with a godaddy domain. Any advice?
@foliodc you’ll need to setup a redirection for the Apex domain (@) to the www subdomain. It’s registrar-dependent, so you should check Goddady’s docs to do this
Apparently some people are already asking for this on their community: GoDaddy Community
Good catch! Just updated the first post with the link to the updated user doc.
Here’s the specific section for GoDaddy. It’s hard to keep all of these up to date but please don’t hesitate to let us know if you notice a big change in the GoDaddy interface.
Sorry, what i mean is can i have example.com and example1.com both point to the same app. the purpose would be that inside the app, i’d bind a value to the base URL to hit my DB to retrieve a specific record that should only show when the app is loaded from a specific URL VS using URL parameters.
basically want to whitelabel the app that we are creating for each of our customers by giving them their own domain name that hits our main app, that based on the domain name applies certain stylings for the customer
For example, the header on Each would be “Welcome to example.com” and “Welcome to example1.com” repsectively
just came across this tool today. Is CoAlias a plug-in or extension with WeWeb? I haven’t signed up yet, but I have some clients that are interested in having their own domain used for the WeWeb app I am building.
When will Weweb.io support naked domains? This is, unfortunately, a bit of a deal breaker for me and I missed this when I began development 6 months ago. Very disappointing to find this out when I went live today! Please add this ‘fine print’ , in bold, to your signup page.
Who still types in ‘www’ for URL’s these days? Nobody. Everyone just types in the domain, which at present will cause a ‘server error’ notice in the browser as it automatically appends ‘https’ in front of the domain.
My nameserver (Namecheap.com) does not support naked https redirects (e.g from naked domain to ‘www’ subdomain) as they can’t install an SSL certificate on their redirect server.
I’m at a bit of a loss here. Is there a known solution, workaround, or nameserver that will work with naked domains and weWeb.io? e.g even if I have to move my domain to another registrar, in order to implement a solution I would consider it.
Checking out this thread it is not at all clear if there is a known and supported solution.
I had this issue with mine originally, but it had nothing to do with WeWeb - I just had to tweak my DNS settings with my domain provider. Your own domain provider should have a guideline on how to do this, all the ones I had used in the past had info about it.
As I understand, all WeWeb does is “communicate” the published app to the domain provider, which is not in natural language - it’s something in the background, and your domain provider is the one that handles the non-natural language backend to either the domain, naked domain or sub-domain that you configured.
Re-reading your post I realise that you have an issue with “http” vs “https”? Not sure. Keeping my answer for other readers just in case it can be of help to someone in the future
First, go on the settings of the project you want to link a custom domain to.
WeWeb doesn’t support naked domain for the moment. Be sure to use a subdomain (the most common one is www)
If your registrar is not on this list, please contact us.
