Hey Lawrence,

Typically, you would point a new name at unbouncepages.com. For example, if you have your web site at 'www.mycompany.com’, you might create ‘news.mycompany.com’ or ‘info.mycompany.com’ and point that at unbouncepages.com.

It sounds like you’ve pointed ‘www.mycompany.com’ at our unbouncepages.com servers. These servers don’t know anything about your existing files, which is why they’re responding with a “not found”.

If I’m understanding your issue correctly, you should point your root domain back to the server for your main site, and create a new name for your Unbounce pages.

Does that make sense?

Cheers,

Carl

Carl,

all makes sense, but we’d really like the unbounce page to be on ‘www.mycompany.com’ for our launch AND to be able to continue to access the rest of our server…are there any workarounds?

Hey Lawrence, it really depends on specifics. If your Unbounce page is acting as a ‘coming soon’, then you should be able to have your existing server available at something other than www.mycompany.com (like, beta.mycompany.com, for example). At launch time, you can just point www to your beta server and voila, you’re live!

In terms of a workaround, there are various proxying methods that would let you access both servers from one name (using Apache for your main site and proxying a portion of your URL space to your Unbounce pages, or using Varnish as a front-end for everything), but assisting with such a configuration is really beyond what we can provide, sorry…