Showing posts from March, 2017

Can't resolve DNS Aws

I recently registered a domain for a joke website  I figured I could whip up the page in a couple of minutes and throw it up on AWS using S3 static site hosting.  All done in an hour or so. What I thought would take an hour ended up in a multi-day ordeal while I tried to get the DNS to resolve.  I went through what seem to be the typical problems.
The bucket wasn't configured to be accessible as a website.My bucket wasn't named the same as the website; the bucket needed to be to match the domain I got these fixed up and found that it still wasn't working.
 I added extra routes in to see if I could Alias or CNAME to a known working site, but they didn't work either. So it seemed it was a problem with something to do with the DNS configuration.

After searching around I found a mention in a thread that the name server records in the hosted zone needed to match those in the domain name registration.  In attempting …

Solving `Empty reply from server` in DotNet Core

tldr; If you’re getting curl: (52) Empty reply from server check that you’ve configured Kestrel correctly. Long version I’ve started playing with Dotnet Core and Docker and have had a few issues getting started. I’ve had a little bit of experience with Docker, though only a little. I’ve worked with DotNet previously but never with Core. Environment The setup I’m using is a Windows laptop running Vagrant. Via Vagrant I’m running an Ubuntu Virtual Machine with the Docker run time installed. Feels a litle like inception. Key Problem The key problem that I’ve had getting started was having my Docker container not responding correctly to my curl commands. I get this:
curl: (56) Recv failure: Connection reset by peer
curl: (52) Empty reply from server Given that I’m not all that familliar with Docker or Dotnet Core I decided to remove one of the variables and set up a simple Express app in a different docker container. This validated that the commmand I was using to run the container (docker ru…