Hi,
We are trying to deploy Web Server to NAV2017 environment.
Web Client runs fine if the Web Server is bound with HTTP (port 80), but when I change this to HTTPS (port 443) I'm getting the following error message. The funny thing is that when I change the HTTPS port to something like 7046, the Web Client launches without any issues.
Service Unavailable
HTTP Error 503. The service is unavailable
Is there any specific configuration that I'm missing in my installation/configuration?
Kenji
*This post is locked for comments
Hello see the bellow screenshot, i used for RND and its working fine,
for reference you can visit: https://saurav-nav.blogspot.in/2015/11/microsoft-dynamics-nav-2016-how-to.html
Look, for better response as per #Saurav create a new instance, follow him article, definitely you will get.
even i'm also followed them and i got.
Note: even if you type: https://nuc07.challanger.local:443/phone/
it automatic bind with
With your explanation, I don't think that explains the behavior where only port 443 is the only port that is not accessible.
Hello KenjiM,
once you installed self-signed or SSL certificate then you have to put the url something like
https://binu.challanger.local/phone
Here binu.challanger.local is a full qualified system name, and phone is a webinstance that i created.
Note: no need to give port number and all, because already certificate pulled all details.
this is might be happen while you installing web server component :
you might delete some URL data (by accident)
your general url will be : 443/DynamicsNAV100/WebClient/
you might be delete : "DynamicsNAV100/WebClient/" on the parameters
Port 443 might be forwarded to a different server (e.g. in your router) ?
Thank you for your feedback.
Yes, I have the self-signed SSL certificate installed, and when I access https://<hostname>:443/ I can access the default website, but when I try to access https://<hostname>:443/DynamicsNAV100/WebClient/ Then I get the error. And like mentioned in original post, if I change the port binding to something other than 443 then I am able to reach the web server.
I'm not sure what's causing this issue.
KenjiM ,
go to management console and check whether what is your client services port is : use that port
You need to create a self-signed SSL certificate and add an https binding to Web Client URL.
Please refer below links for more information.
https://msdn.microsoft.com/en-us/library/hh167264(v=nav.90).aspx
https://blogs.msdn.microsoft.com/suvidha/2014/09/10/securing-the-nav-web-client-connection-with-ssl/
-Yogesh Kulkarni
Please verify, if you find answer helpful.
Sohail Ahmed
2
mmv
2
Amol Salvi
2