Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K 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
- 264 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 385 SQL Performance
- 33 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
Options
NAV 2016 in Docker Container returns "Could not create SSL/TLS secure channel" on web request
rsaritzky
Member Posts: 469
Hi all,
We do our in-house development in local Docker containers. We have a shipping solution that communicates with Fedex web services.
Since the last update of the NAV2016 Docker image artifacts (approx Nov 1, 2021 - perhaps a week earlier), when running a Fedex web service request, we receive an error "Could not create SSL/TLS secure channel".
This error does NOT occur in our production database or any non-Docker test databases.
References to this error point to a problem with TLS1.2 not being in the default configuration.
The shipping solution formats the web request and then calls it through a DotNet component "System.Net.HttpWebRequest"
Any ideas?
Thanks
We do our in-house development in local Docker containers. We have a shipping solution that communicates with Fedex web services.
Since the last update of the NAV2016 Docker image artifacts (approx Nov 1, 2021 - perhaps a week earlier), when running a Fedex web service request, we receive an error "Could not create SSL/TLS secure channel".
This error does NOT occur in our production database or any non-Docker test databases.
References to this error point to a problem with TLS1.2 not being in the default configuration.
The shipping solution formats the web request and then calls it through a DotNet component "System.Net.HttpWebRequest"
Any ideas?
Thanks
Ron
0