Development site admin portal not working

Darren Hagen asked on May 29, 2019 15:43

So I have done the following. I added the CustomAdminUrl and associated value that is the URL of my development site along with /Admin to the web.config. I added the appropriate RouteConfig mapRoute for the AdminRedirect. I then added the AdminRedirectContoller with CustomAdminUrl settings. Finally, in the local version of the admin I added an alias for the development URL we are using. The front end of the site works great. I just can't get to the admin on the development server.

When I attempt to go to the 'root url'/Admin I get "...redirected you too many times." I have cleared the cookies for that browser and get the same result. Is there somewhere in the database that I need to update or something else that I am missing? Please let me know if there is something obvious after migration that I should be attending to. Thanks

Correct Answer

Dmitry Bastron answered on May 29, 2019 18:09

Forgot to mention, in this case your admin application should be configured as an application in IIS Right click on your website in IIS and add admin application with "kentico" alias.

Image Text

Hope it will help.

Also, I usually create admin link for MVC sites like admin.yourdomain.com instead as it's easier to configure but may require extra SSL certificate for production (if you don't have wildcard certificate).

2 votesVote for this answer Unmark Correct answer

Recent Answers


Dmitry Bastron answered on May 29, 2019 16:07

Hi Darren,

I would rather try anything else apart from /Admin. For example, if you configure yourdomain.com/kentico as your Admin URL - Kentico admin area should be accessible via yourdomain.com/kentico/Admin URL. Please try this one.

0 votesVote for this answer Mark as a Correct answer

Darren Hagen answered on May 29, 2019 17:48

Dmitry - Thanks for the response. I did add the /kentico and then tried going to the /kentico/admin. I getting a new server error.

"Server Error in '/' Application. The resource cannot be found" DESCRIPTION: HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable. Please review the following URL and make sure that it is spelled correctly.

I have all the same files on the server that I did locally.

0 votesVote for this answer Mark as a Correct answer

Darren Hagen answered on May 29, 2019 18:30

It was the IIS Application that did it. Thank you so much Dmitry, and the subdomain idea. I will keep that in mind.

0 votesVote for this answer Mark as a Correct answer

Dmitry Bastron answered on May 29, 2019 19:48

Glad to hear this and good luck with your projects! Could you mark my answer as correct please?

0 votesVote for this answer Mark as a Correct answer

   Please, sign in to be able to submit a new answer.