0

I have created a provider hosted app, my MVC web application is hosted on IIS, I am able to access my web application with both lan ip and public ip from my PC, our office network uses Cyberroam and my network administrator has provided me external IP of the host machine which is accessible publicly.

I have registered my app on AppRegexNew.aspx, and configured it to use the local IP of host machine, for example: 192.165.5.25

After deploying it to my Sharepoint Developer's site it is installing and working perfectly and is accessible inside our LAN network. But when I registered a new app configured with public ip of host machine for example: 120.***.***.***

(I also updated app manifest and web.config of MVC site properly with new client id and made sure to remove previous versions of the app from developer site ), the app takes too long for installation and then fails with error message "Sorry, something went wrong with adding the app". I tried doing it multiple times, the app with local ip installs and runs smoothly but the app with public ip doesn't. What can be the possible solution to this?

Improve this question
5
  • What does the uls log say about the error?
    – Sascha
    Commented Dec 20, 2014 at 13:06
  • sry I forgot to mention that I am deploying my app on sharepoint online, i cant see uls log.
    – Frustrated Engineer
    Commented Dec 22, 2014 at 5:16
  • Ok sounds like you deploye some assemblies or lists that already exists or s.th. I had a similar problem and ended up that I found out that my app wanted to install some lists that already exists.
    – Sascha
    Commented Dec 22, 2014 at 12:26
  • I tried it yesterday, completely deleted app, and it worked, not sure what exactly was the problem, thanks for your time though, really appreciate it :)
    – Frustrated Engineer
    Commented Dec 23, 2014 at 5:08
  • So write it down as an answer :)
    – Sascha
    Commented Dec 23, 2014 at 12:40

1 Answer 1

Reset to default
0

I am not exactly sure what was wrong, but I tried again after completely deleting the app and deployed again, and it worked.

Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.