Apache will start just fine. This implies that the connection is blocked somewhere between you and Github. Now log in to your GitLab account, go to User Settings and look for SSH keys in the left sidebar. But as you can see, between the first request for runner-1 and second request for runner-1 there are two sleeps taking 5s, so finally it’s ~10s between subsequent requests for runner-1 . GitLab Setting up Gitlab Pages Double click the Pageant icon in your system tray to open the Pagent Key List dialog. Create a new repo and put a .gitlab-ci.yml inside with: test_backend_job: image: debian:latest script: - apt-get update && apt-get --assume-yes install netcat - nohup nc -l localhost 5000 & - sleep 5 - nc … Improve this answer. On the source server, the old keys are stored in the file ~/.ssh/known_hosts. GitLab ; GitLab - How to fix gitlab.com: permission denied (publickey) fatal: Could not read from remote repository; BitBucket - Permission denied (public key), can’t … Show activity on this post. fatal: could not read Username for 'https://github.com': No such device or address Nginx -Gitlab: could not clone over https GitLab: The project you were looking for could not be found. Steps to reproduce. NUC is connected via OpenVPN to the server on AWS. Apache forwards incoming requests to GitLab on Docker. GitLab on a DiskStation I've tried changing the .gitlab-ci.yml to include override to the situation Warning: Using a password on the command line interface can be insecure. docker-compose exec gitlab-runner bash gitlab-runner run --user=root. docker下gitlab安装配置使用 If not defined, the project’s job timeout setting is used. GitLab Runner checks for configuration modifications every 3 seconds and reloads if necessary. Now log in to your GitLab account, go to User Settings and look for SSH keys in the left sidebar.