Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 302 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Cannot open 365 BC web client installed on docker
Blackdiamond
Member Posts: 29
Hi everyone,
I have updated my windows to window version 1903, windows 10 Enterprise. Docker is version 2.1.0.0 (36874).
I have just created new container and new image using this script using Powershell in Admin mode:
New-NavContainer -accept_eula -containerName "bcsandbox" -auth NavUserPassword -imageName "mcr.microsoft.com/businesscentral/sandbox:dk" -useBestContainerOS -updatehost
I get a status yesterday with container bcsandbox succesfully created. I was also able to use link created on desktop to open 365 BC on Cloud, which means I could log to 365 BC using username and password.
I am not able to use same created link on my desktop today. After a while it time out. "ERR_CONNECTION_TIMED_OUT"
I have tried to use several hours to search on Google but I am not able to find an answer.
Please help or advice which information do you need to assist me.
Thanks
I have updated my windows to window version 1903, windows 10 Enterprise. Docker is version 2.1.0.0 (36874).
I have just created new container and new image using this script using Powershell in Admin mode:
New-NavContainer -accept_eula -containerName "bcsandbox" -auth NavUserPassword -imageName "mcr.microsoft.com/businesscentral/sandbox:dk" -useBestContainerOS -updatehost
I get a status yesterday with container bcsandbox succesfully created. I was also able to use link created on desktop to open 365 BC on Cloud, which means I could log to 365 BC using username and password.
I am not able to use same created link on my desktop today. After a while it time out. "ERR_CONNECTION_TIMED_OUT"
I have tried to use several hours to search on Google but I am not able to find an answer.
Please help or advice which information do you need to assist me.
Thanks
0
Answers
Use the -updateHosts flag when creating your container with New-NavContainer, or you will not be able to access it by name. You should be able to access your container via IP though.
Freddy should really place the flag more prominently in the documentation, took me way too long to realize it even exists.
/Wisa
Hi Phogue,
How do I create New-NavContainer script again. I installed this container yesterday?
Hi Wisa,
Can you please elaborate in examples in more detail. What do you mean by "-updateHosts flag".
Hi @Blackdiamond
I am pretty sure that Wisa meant to add "-updateHosts" to your launching command, i.e. replacing
with:
as there seems to be a typo.
This command updates your hosts file (located in windows->system32->drivers->etc) and adds the ip of your container, allowing you to connect using the name of your container in your browser, instead of having to use the container's ip to connect.
Descriptions of all the parameters can be found in the source code for the New-Navcontainer script
Thanks I will do that next time. Good point :-)
Please read this:
https://freddysblog.com/2019/08/07/zombie-containers-skip-this-build/