-
Notifications
You must be signed in to change notification settings - Fork 91
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to Open Nav Web Client on another machine within the Network #226
Comments
There are several things you should test
|
or maybe you didn't publish the ports from the container on the host. |
@NAVspecialist - Thanks for the reply. Yes i can ping the IP Address of the server. I have added the Port 443 in inbound rules of firewall using ("netsh advfirewall firewall add rule name="Docker443" dir=in action=allow protocol=TCP localport=443 enable=yes profile=domain,private,public") I am not using the IP address instead using the web client address which we get at the end after we use the New-Navcontainer command |
It would help a lot if you specify the command you use to start the container? |
@freddydk - Thanks for the reply. Don't really know what command i am supposed to use in this case. New-NavContainer After this i didn't perform any other command for Port Enable |
fine - this show me that your container indeed cannot be reached from outside the server unless you use transparent networking or other special things. |
@freddydk - Hi Freddy, used the following command, still i am not able to access from any other machine within the Network. Please let me know if i am missing out something in the command. I am using the URL - https://TestNav2018CU5/NAV/ to browse. $publicdnsName = 'TestNav2018CU5' $additionalParameters = @("--publish 8080:8080", New-NavContainer |
Did you try changing the https://TestNav2018CU5/NAV/ to the IP-address/NAV/ instead? Can you start a commandprompt and type ping Testnav2018cu5 ? |
Yeah, so what is the name of the Server on which the container is running? |
@NAVspecialist - Running it with IP address, it worked on other machines. Thanks. Still not able to Download Symbols using VS Code from another machine. I have installed the Certificate and added it in Trusted Root Certification Authorities, still getting the same error. |
Hi Guys, Kindly Assist. |
You are using a self-signed certificate. In the output of the container you will find the URL to this certificate (you can download it from the container). You need to trust this certificate on the computer on which you run VS Code. You do this by installing it on the trusted root certificatioins on that machine. |
@freddydk - Still not working. I have downloaded the certificate from the container and Installed it on the machine. Still when i browse, i am getting the same warning of invalid certificate and when i am using VS Code to download symbol getting SSL error. Attached are the screenshots. |
You cannot use the IP number for https - the name after https needs to be what the certificate is made for. |
@freddydk - Hi Freddy. Thanks for the Suggestion. created another container using following command, where i have removed usessl - Now the Problem is i am not able to browse my Web Client from another machine on the Network, however i was able to download symbols on the same machine via connection through the new web client URL (just the opposite of what was happening in the previous step). I am using "http://IP-address/NAV/" on the browser. |
modify your --publish 443:443 (https) to --publish 80:80 (http) - else you won't publish the right port. |
@freddydk - Worked, Thank you very much. 👍 🥇 |
I have a dedicated server with windows server 2016 where i have installed dockers. I have downloaded nav 2018 cu5 image and created container for the same. i have configured portainer to manage the containers within docker. Now the problem is i am able to browse to portainer and nav web client within the dedicated server, however when i am trying to browse the Nav web client outside the server but on a machine which is within the network i am unable to connect (through vs code) or even browse the page. Somehow portainer page has the configurations to be browsed from any machine within the network. Can anyone please help and let me know which step did i miss while creating container for nav web client?
The text was updated successfully, but these errors were encountered: