question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Docker error after adding proxy

See original GitHub issue

I was using mup in combination with force-ssl. Now that forcing SSL is implemented in the mup proxy, I wanted to switch my configuration.

Unfortunately, after the switch, I got the following error:

	-----------------------------------STDERR-----------------------------------
	tsencrypt not found
	Error response from daemon: No such container: travel-nginx-proxy
	Error response from daemon: endpoint travel-nginx-proxy not found
	Finished removing docker containers
	--2017-11-09 09:36:45--  https://raw.githubusercontent.com/jwilder/nginx-proxy/master/nginx.tmpl
	Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 151.101.60.133
	Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|151.101.60.133|:443... connected.
	HTTP request sent, awaiting response... 200 OK
	Length: 11540 (11K) [text/plain]
	Saving to: ‘/opt/travel/config/nginx.tmpl’
	
	     0K .......... .                                          100% 13.6M=0.001s
	
	2017-11-09 09:36:45 (13.6 MB/s) - ‘/opt/travel/config/nginx.tmpl’ saved [11540/11540]
	
	docker: Error response from daemon: driver failed programming external connectivity on endpoint travel-nginx-proxy (cbebf49add91adbac64520e07574dceba34082007a9e81f7635396f6a8f7d041): Bind for 0.0.0.0:443 failed: port is already allocated.
	-----------------------------------STDOUT-----------------------------------
	using image
	removing last
	Image mup-travel:latest
	Volume
	94dd93d111fd38e3027aefafcc146edf8a3de53071b92631fe766aa2390bd5be
	Ran abernix/meteord:base
	Running autogenerate
	latest: Pulling from jrcs/letsencrypt-nginx-proxy-companion
	Digest: sha256:5bb2e91c0503baf9357c3b5eee659a8b259cf65c49cbf86717fb1a4f2307c0ba
	Status: Image is up to date for jrcs/letsencrypt-nginx-proxy-companion:latest
	latest: Pulling from jwilder/nginx-proxy
	Digest: sha256:ca447abb6b8ce7bdf5783b8be11867e1f065b8c06ac837f0024feb1151cee71b
	Status: Image is up to date for jwilder/nginx-proxy:latest
	Pulled autogenerate images
	af42ab57f851ec08755a7864ffb11871344ab915d065da8d42628e60e25770fc
	----------------------------------------------------------------------------

This is despite the fact I can see the container if I run docker ps -a on the machine. I tried mup setup and mup reconfig and also mup deploy, but nothing helped.

To me, it is also not clear if the meteor.ssl config is still needed if you have proxy.ssl in place. I kept both, just to be sure.

Here’s the excerpt of my config:



  proxy: {
    domains: 'my.domain.com',
    ssl: {
      letsEncryptEmail: 'my@mailaddress.com',
      forceSSL: true
    }
  },

meteor: {
    ...
    ssl: {
      autogenerate: {
        email: 'my@mailaddress.com',
        domains: 'my.domain.com'
      }
    },
    ...
}

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Comments:13

github_iconTop GitHub Comments

1reaction
bevinhexcommented, Dec 18, 2017

Yeah similar problem here, it is because if you want to use proxy for some reason (like http->https redirects), you need to setup ssl for proxy, between proxy and meteor , ssl is not needed, besides if you enable it mup reports error while trying to setup two proxy, and also need to change ROOT_URL to http or else meteor websocket will try to connect to https address, and somehow keep failing Mine is working fine now, this is part of my config, just tested.

  env: {
      ROOT_URL: 'http://test.de',
      MONGO_URL: 'mongodb://localhost/meteor',
    },

    // ssl: {
      // Enables let's encrypt (optional)
      // autogenerate: {
        // email: 'admin@test.de',
        // comma separated list of domains
        // domains: 'test.de,www.test.de'
      // },
    // },
    docker: {
      // change to 'abernix/meteord:base' if your app is using Meteor 1.4 - 1.5
      image: 'abernix/meteord:node-8.4.0-base',
    },

    // Show progress bar while uploading bundle to server
    // You might need to disable it on CI servers
    enableUploadProgressBar: true
  },

  mongo: {
    version: '3.4.1',
    servers: {
      linode: {}
    }
  },

	proxy:{
		domains: 'test.de,www.test.de',
		ssl:{
			letsEncryptEmail: 'admin@test.de',
			forceSSL:true
		}
	},
Read more comments on GitHub >

github_iconTop Results From Across the Web

Configure Docker to use a proxy server
On the Docker client, create or edit the file ~/.docker/config.json in the home directory of the user that starts containers. Add JSON similar...
Read more >
Cannot download Docker images behind a proxy
To configure Docker to work with a proxy you need to add the HTTPS_PROXY / HTTP_PROXY environment variable to the Docker sysconfig ...
Read more >
Docker run works behind proxy, and Docker build does not
Steps to reproduce the issue: docker run -it ruby bash; Configure http_proxy and https_proxy env variables; execute apt-get update (it should run fine)....
Read more >
Troubleshoot a Docker Container when it is Unable to ...
Step 5. Add the proxy server info in the ENV section of the Dockerfile. ENV JAVA_VERSION 1.7.0. ENV http_proxy http://proxy.
Read more >
Docker proxy error - Nexus Repository Manager
docker error info"error pulling image configuration: download failed after attempts=1: unknown blob". Personally, I understand that docker ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found