title: Gitlab-runner shell executor suddenly error on ssl
body: <p>Yesterday my shell executor worked fine with default test yml:</p>
  
  <pre><code>stages:
    - test
    - build
    - deploy
  
  test:
    stage: test
    script: echo "Running tests"
  
  build:
    stage: build
    script: echo "Building the app"
  
  deploy_staging:
    stage: deploy
    script:
      - echo "Deploy to staging server"
      - export
    environment:
      name: staging
      url: https://staging.example.com
    only:
    - master
  </code></pre>
  
  <p>But now i get the follow error:  </p>
  
  <pre><code>Running with gitlab-runner 10.3.0 (5cf5e19a)
    on gitlab01ShellSQLRunner (9ec36953)
  Using Shell executor...
  Running on debian...
  Cloning repository...
  Cloning into '/home/gitlab-runner/builds/9ec36953/0/dev/SQL'...
  fatal: unable to access 'https://gitlab-ci-token:xxxxxxxxxxxxxxxxxxxx@10.45.18.14/dev/SQL.git/': SSL: certificate subject name (Gitlab01) does not match target host name '10.45.18.14'
  ERROR: Job failed: exit status 1
  </code></pre>
  
  <p>This is I fail to understand because of three things:<br>
  1. The runners url is <a href="https://gitlab01" rel="nofollow noreferrer">https://gitlab01</a> (why does it use ip suddenly?)<br>
  2. The ip matches the url <a href="https://gitlab01.YXNET.local" rel="nofollow noreferrer">https://gitlab01.YXNET.local</a> ~ aliased <a href="https://gitlab01" rel="nofollow noreferrer">https://gitlab01</a><br>
  3. It worked yesterday:  </p>
  
  <pre><code>Running with gitlab-runner 10.3.0 (5cf5e19a)
    on gitlabShellRunner (d36a5267)
  Using Shell executor...
  Running on debian...
  Fetching changes...
  HEAD is now at 6e9a125 added CI/CD file
  From https://gitlab01/dev/SQL
     6e9a125..84de9fd  master     -&gt; origin/master
  Checking out 84de9fd7 as master...
  Skipping Git submodules setup
  $ echo "Running tests"
  Running tests
  Job succeeded
  </code></pre>