License: Apache License 2.0

Nginx 15.17% Shell 84.83%

docker-nginx-ssl-proxy's People

Contributors

Stargazers

Watchers

Forkers

dsys remac spunkedy farmisen appallicious kenblair1226 nejcsm torchlightsoftware djaed globegitter danyanya cinello shokunin lookstar kayman-mk john-hix epasham

docker-nginx-ssl-proxy's Issues

Can't map two secrets to /etc/secrets

Kubernetes doesn't support mapping two secrets to the same directory... They're mounted as volumes and you can't put one volume inside another or merge the keys in any way.

In the meantime, is there something we can do with this container to make it easier to work with? Possible solutions:

Make the auth secret location configurable, e.g. AUTH_LOCATION.
Put the auth secret in a different place, e.g. /etc/auth/htpasswd.

1 would be more backward compatible, but is anyone successfully utilizing the current configuration? 2 avoids adding an additional config parameter, and feels a little bit more aware of the present kubernetes limitations.

Bronken json on deployment

Can you post or send a service and replicationController example of your nginx and letsencrypt?

I'm having got this error message :

unable to decode "./nginx-ssl-proxy-deployment.yml": [pos 128]: json: expect char '"' but got char '{'

That is my RC and SVC .yml of my nginx and letsencrypt:

kind: Service
apiVersion: v1
metadata:
  name: letsencrypt-service
spec:
  ports:
  - port: 80
    targetPort: 80
    protocol: TCP
  selector:
    name: letsencrypt
    role: cert-app

---

kind: ReplicationController
apiVersion: v1
metadata:
  name: letsencrypt-rc
  labels:
    name: letsencrypt
    role: cert-app
spec:
  replicas: 1
  selector:
    name: letsencrypt
    role: cert-app
  template:
    metadata:
      name: letsencrypt-rc
      labels:
        name: letsencrypt
        role: cert-app
    spec:
      containers:
      - name: letsencrypt
        image: ployst/letsencrypt:0.0.3
        env:
        - name: EMAIL
          value: [email protected]
        - name: DOMAINS
          value: [MY DOMAIN, FOR NOW, IT'S MY EXTERNAL IP. WORKS?]
        - name: RC_NAMES
          value: nginx-ssl-proxy-api
        ports:
        - name: ssl-proxy-http
          containerPort: 80

kind: Service
apiVersion: v1
metadata:
  name: nginx-ssl-proxy-service
spec:
  ports:
  - name: https
    port: 443
    targetPort: ssl-proxy-https
    protocol: TCP
  - name: http
    port: 80
    targetPort: ssl-proxy-http
    protocol: TCP
  selector:
    name: nginx-ssl-proxy-api
    role: ssl-proxy
  type: LoadBalancer
  externalIPs: [xxx.xxx.xxx.xxx]

----

kind: ReplicationController
apiVersion: v1
metadata:
  name: nginx-ssl-proxy-api
  labels:
    name: nginx-ssl-proxy-api
    role: ssl-proxy
    spec:
      containers:
      - name: nginx-ssl-proxy-api
        image: ployst/nginx-ssl-proxy:0.0.3
        env:
        - name: CERT_SERVICE_HOST_ENV_NAME
          value: LETSENCRYPT_SERVICE_SERVICE_HOST
        - name: CERT_SERVICE_PORT_ENV_NAME
          value: LETSENCRYPT_SERVICE_SERVICE_PORT

deployment-files.zip

cert.crt read failed

Hi, sorry to bother but I really can't solve this problem.
When I run the command below,

docker run \
-e ENABLE_SSL=true \
-e TARGET_SERVICE=localhost \
-e SERVER_NAME=truemagic.cn \
-v cert.crt:/etc/secrets/proxycert \
-v key.pem:/etc/secrets/proxykey \
-v dhparam.pem:/etc/secrets/dhparam \
ployst/nginx-ssl-proxy

I got output like this

Enabling SSL...
Starting nginx...
2018/08/14 10:01:37 [emerg] 9#9: PEM_read_bio_X509_AUX("/etc/secrets/proxycert") failed (SSL: error:0906D06C:PEM routines:PEM_read_bio:no start line:Expecting: TRUSTED CERTIFICATE)
nginx: [emerg] PEM_read_bio_X509_AUX("/etc/secrets/proxycert") failed (SSL: error:0906D06C:PEM routines:PEM_read_bio:no start line:Expecting: TRUSTED CERTIFICATE)

And here's my cert.crt:

Could you tell me where I am wrong? Is this some kind of format problem or what?
Thanks!

Question about using with letsencrypt

Hi , i am trying to implement this (that was written by you) and i need your help to clarify some things:

About the letsencrypt replication controller and service - do i need to expose the letsencrypt service the the internet or only as internal service in my cluster? If the service will exposed internal i assume that it will be used by the nginx-ssl-proxy service right?
In my domain settings (currently managed by goDaddy) i need to point my domain to a different IP address (according to letsencrypt docs) so i wanted to know what will be the IP address that my domain should points to.. the IP address of the nginx-ssl-proxy service or the IP address of the letsencrypt service?
Do i need to generate some *.pem files ahead (for cert and key) or everything will be done automatically when i will deploy both containers to kubernetes
Do you have a source where i can downloaded the yaml files for both (the letsecnrypt and the proxy pods) ?

Thanks in advanced!

Recommend Projects

React

A declarative, efficient, and flexible JavaScript library for building user interfaces.
Vue.js

🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript

TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
TensorFlow

An Open Source Machine Learning Framework for Everyone
Django

The Web framework for perfectionists with deadlines.
Laravel

A PHP framework for web artisans
D3

Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

javascript

JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
web

Some thing interesting about web. New door for the world.
server

A server is a program made to process requests and deliver data to clients.
Machine learning

Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Visualization

Some thing interesting about visualization, use data art
Game

Some thing interesting about game, make everyone happy.

Recommend Org

Facebook

We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft

Open source projects and samples from Microsoft.
Google

Google ❤️ Open Source for everyone.
Alibaba

Alibaba Open Source for everyone
D3

Data-Driven Documents codes.
Tencent

China tencent open source team.

ployst / docker-nginx-ssl-proxy Goto Github PK