Access old production system by IP address

You need to do a few things for this to happen:

1. Make sure your IP is publically available to access that way.
2. Make sure your IP is properly mapped on your internal network to the server with the old website.
3. Make sure you have a Kentico license key for the IP address.
4. Make sure you have an alias for that IP added to the site in Kentico.

Database? Is it accessible? Can you get it from there?

Hi Brenden,

I work w/Bob and what is the best way of doing that ? We can get at IIS and I'm assuming that the prod licn needs to change to dev since the migrated site's domain (same as old) already has a prod licn.

Thanks

Steve/Bob,

To change the DNS records, you'd need access to your DNS management tool/website. Typically your network admin has this. Secondly, you need to specify a bit more what your environment(s) look like. Do you have prod and dev on one server? If so (not ideal), then simply add the license key for dev into dev and change the domain of that site in the Sites app to dev. You'll also want to make sure you bind IIS to use your dev URL as well.

Did you mean "... license key for dev into prod and change ..."

No. Provide more info on your setup. Are dev and prod on the same server? Do you have separate dev and prod database servers? Do you have the subdomain setup for dev.yourdomain.com? Do you have the subdomain pointing to the server in which dev is on?

Am I safe in assuming your new system you migrated to is NOT Kentico or are both your old and your new sites Kentico instances? Provide as much detail as you can.

Our kentico landscape (dev, authoring, production, separate instances, separate databases) was migrated to Azure. On the old landscape, on prem, the instances were also on separate servers as well as the databases. The domain was also switched from pointing at on prem to pointing at azure. The production instance's licn went to azure when it was migrated.

In Azure you should have 3 separate web apps. Production is most likely yourdomain.com while the others are named with an alias based on the web app's name. Something like dev-webapp.azurewebapps.net.

You should be able to access the site at that Azure alias URL and receive a Kentico related message stating you don't have a key for this domain. You can then log in and enter a new license key and update the sites domain.

If you're getting a 404 or Azure blue page, they you don't have your web app configured properly. If you FTP'd your website contents to the web app, then you need to go into the configuration of the web app and set the path mapping to the site\wwwroot\CMS directory. If you're using a repository to deploy your project, then it should do this for you automatically.

I'd suggest FTPing into your instance and looking at the file structure. Then going to the web app and

I'm sorry for the confusion, but we are looking to get at the old production instance which is on prem. Thank you very much for the time you spent with this.

Ok then I go back to what I initially said, you need to make sure your dev.domain.com is pointing to your on-prem public facing IP address. Next you need to make sure your on-prem server has the proper IIS binding for that dev domain. At this point you should at least be able to get to the Kentico error page like this stating you don't have the proper license key.

Lastly log in to that dev instance and enter the proper dev license key and update the website's domain to your new dev domain.