Cannot make http requests to sails app running in a docker container

[colinmetcalf]

Node version: 8.12.0
Sails version (sails): 1.2.3
ORM hook version (sails-hook-orm): 2.1.1
Sockets hook version (sails-hook-sockets): 1.5.5
Grunt hook version (sails-hook-grunt): 1.0.8

---

Hello,
I recently updated sails from 0.12 to v1 on my application that uses sails to connect my backend to a mongo database. The update works great on my local machine, however during my jenkins build when pushing out the update to my servers, I am running into an error connecting to a docker container which runs my sails application.
I am currently receiving the error: Client network socket disconnected before secure TLS connection was established
and cannot seem to debug it. This error happened when I attempted to send a GET request to the server running the docker container after the app spun up. I have not been able to diagnose the root issue in my own debugging or in sails documentation

Here are the headers I am sending in the GET: Accept, 'X-JFrog-Art-Api, 'Content-Type', 'User-Agent': 'axios/0.18.1'

Thanks

[sailsbot]

@colinmetcalf Thanks for posting! We'll take a look as soon as possible.

In the mean time, there are a few ways you can help speed things along:

• look for a workaround. (Even if it's just temporary, sharing your solution can save someone else a lot of time and effort.)
• tell us why this issue is important to you and your team. What are you trying to accomplish? (Submissions with a little bit of human context tend to be easier to understand and faster to resolve.)
• make sure you've provided clear instructions on how to reproduce the bug from a clean install.
• double-check that you've provided all of the requested version and dependency information. (Some of this info might seem irrelevant at first, like which database adapter you're using, but we ask that you include it anyway. Oftentimes an issue is caused by a confluence of unexpected factors, and it can save everybody a ton of time to know all the details up front.)
• read the code of conduct.
• if appropriate, ask your business to sponsor your issue. (Open source is our passion, and our core maintainers volunteer many of their nights and weekends working on Sails. But you only get so many nights and weekends in life, and stuff gets done a lot faster when you can work on it during normal daylight hours.)
• let us know if you are using a 3rd party plugin; whether that's a database adapter, a non-standard view engine, or any other dependency maintained by someone other than our core team. (Besides the name of the 3rd party package, it helps to include the exact version you're using. If you're unsure, check out this list of all the core packages we maintain.)

---

Please remember: never post in a public forum if you believe you've found a genuine security vulnerability. Instead, disclose it responsibly.

For help with questions about Sails, click here.

[whichking]

Hey, @colinmetcalf—could you provide us with a simple repo that reproduces this error? Thanks!