nginx-proxy | Automated nginx proxy for Docker containers using docker-gen | Proxy library

by nginx-proxy Python Version: 1.3.1 License: MIT

X-Ray Key Features Code Snippets(1)Community Discussions(10)Vulnerabilities Install Support

kandi X-RAY | nginx-proxy Summary

nginx-proxy is a Python library typically used in Networking, Proxy, Nginx, Docker applications. nginx-proxy has no bugs, it has no vulnerabilities, it has a Permissive License and it has medium support. However nginx-proxy build file is not available. You can download it from GitHub.

nginx-proxy sets up a container running nginx and docker-gen. docker-gen generates reverse proxy configs for nginx and reloads nginx when containers are started and stopped. See Automated Nginx Reverse Proxy for Docker for why you might want to use this.

Support

Quality

Security

License

Reuse

Support

nginx-proxy has a medium active ecosystem.

It has 17122 star(s) with 2909 fork(s). There are 275 watchers for this library.

It had no major release in the last 12 months.

There are 369 open issues and 934 have been closed. On average issues are closed in 1675 days. There are 56 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of nginx-proxy is 1.3.1

Quality

nginx-proxy has 0 bugs and 0 code smells.

Security

nginx-proxy has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

nginx-proxy code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

nginx-proxy is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

nginx-proxy releases are available to install and integrate.

nginx-proxy has no build file. You will be need to create the build yourself to build the component from source.

Installation instructions are not available. Examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of nginx-proxy

Get all kandi verified functions for this library.

nginx-proxy Key Features

No Key Features are available at this moment for nginx-proxy.

nginx-proxy Examples and Code Snippets

Running Datasette behind a proxy-Nginx proxy configuration

Python

Lines of Code : 0

License : Permissive (Apache-2.0)

Copy

events {
  worker_connections  1024;
}
http {
  server {
    listen 80;
    location /my-datasette {
      proxy_pass http://127.0.0.1:8009/my-datasette;
      proxy_set_header Host $host;
    }
  }
}

Community Discussions

Trending Discussions on nginx-proxy

Does docker's Dockerfile "From" download image?

How to redirect to index.html when using proxy_pass

Nginx Reverse Proxy docker container gives 504 Gateway Time-out

Different domain with different phpmyadmin service and the "same port" problem (nginx reverse proxy, docker)

Docker compose with Dockerfile creates multiple images instead of one

How to serve multiple container using bitnami nginx container

Rails 6 ActionCable Unable to Upgrade WebSocket Request

ingress-nginx not working when using ingressClassName instead of kubernetes.io/ingress.class in annotations

Docker jrcs/letsencrypt-nginx-proxy-companion doesn't generate a proper certificate

storage class in aks can't chown a directory

QUESTION

Does docker's Dockerfile "From" download image?

Asked 2022-Apr-09 at 22:43

I followed this article to build multi domain websites
https://carlosvin.github.io/langs/en/posts/reverse-proxy-multidomain-docker/
This is a basic test, very simple. Only three files.

Edit
C:\Windows\System32\drivers\etc\hosts

...

ANSWER

Answered 2022-Apr-09 at 22:43

The Dockerfile defines how your new image is created. You aren't running the httpd image, you are running two different images that extended the httpd image:

Source https://stackoverflow.com/questions/71808484

QUESTION

How to redirect to index.html when using proxy_pass

Asked 2022-Apr-01 at 20:59

I'm trying to setup a Angular/NestJS project that uses docker. It's all working except if I reload the Angular frontend (admin) on any url other than / it gives me a 404. I believe I need the try_files $uri $uri/ /index.html =404; in location / part of the default.config file, but I can't figure out how to get it to work with proxy_pass. Anyone get this to work or know the secret?

Folder Structure

...

ANSWER

Answered 2022-Apr-01 at 20:59

The try_files directive needs to be set in the Angular apps Nginx Docker component. The first Nginx instance does not have access to the Angular containers' filesystem, which it needs to check whether a file exists or not.

Create a Nginx configuration file, admin/nginx-config.conf:

Source https://stackoverflow.com/questions/71712547

QUESTION

Nginx Reverse Proxy docker container gives 504 Gateway Time-out

Asked 2022-Mar-21 at 14:16

I have two docker container running, one is the jwilder nginx reverse proxy. The other one is portainer. I can access the portainer backend by adding the :9443 port to the url. But the virtual host and virtual port configured for nginx reverse proxy don't seem to work. I get a 504 Gateway Time-out. I use the following docker-compose.yml's each with their Dockerfile in the same folder:

For nginx reverse proxy (compose)

...

ANSWER

Answered 2022-Mar-21 at 14:16

I was able to find out what went wrong. Maybe it helps someone who runs into the same problem. It was a iptables that didn't allow the traffic. So remember to test without any extra iptables rules to rule that out.

Source https://stackoverflow.com/questions/71556801

QUESTION

Different domain with different phpmyadmin service and the "same port" problem (nginx reverse proxy, docker)

Asked 2022-Mar-20 at 12:09

I have a VPS with nginx-proxy container, and I create some wordpress website with phpmyadmin service. If I want to create another site with this definition I got "same port" problem. Ok, I can change the port to 2998 and it works fine but I need to add a new open port to my VPS. I don't want to add or change the port for each site.

Now:

example-a.com:2999 -> example-a phpmyadmin login page
examlpe-b.com:2998 -> example-b phpymadmin login page

Is there a way to direct me to the appropriate container by domain address?

example-a.com:2999 -> example-a phpmyadmin login page
examlpe-b.com:2999 -> example-b phpymadmin login page

My nginx proxy definition

...

ANSWER

Answered 2022-Mar-07 at 12:49

What you want is not possible, but you probably don't actually want it. It becomes clear once you think through what you want to configure, and what would happen if a user would go to either URL:

you have configured example-a.com to point to your IP
you have configured example-b.com to point to your IP
you have configured your nginx-proxy container to listen on ports 80 and 443
you want to configure your WordPress containers to both listen on port 2999
you, or rather the acme-companion, have configured your nginx container to forward HTTP requests that ask for host example-a.com to go to the container for example A with port 2999, and requests that ask for example-b.com to go to container B with port 2999

Now, you can see right away that you have two things attempting to listen on the same network interface with port 2999 - that doesn't work, and it can't, because who would handle picking up incoming requests before the request is parsed to find out which host it wanted ? Container A can't accept the request and, if it's meant for B, hand the request over - A doesn't know about B.

So if you think about a user sending a request to example-a.com:2999, what really happens is that a request goes to :2999, just like if a user goes to example-b.com:2999, it will end up going to :2999.

How can that problem be solved ? By having a third container C that accepts user requests, looks into the request, and based on whether they wanted container A or B, hands the request over to A or B.

Here is the great thing: you already have that! Container C is really your nginx container, which is listening on port 80/443. So if your users go to example-a.com without providing a port, it will go to 80 or 443 (depending on whether they used http or https). Then, nginx will analyze the request, and send it to the correct container. For this, it doesn't really matter what port A and B listen on, because to the outside world, it looks like they are listening on 80/443.

So the real answer is that while you can't combine custom ports with virtual hosts and use the same port for multiple containers (other than 80/443), you don't actually NEED custom ports in the first place! If you just configure your containers with the default ports, users can use both https://example-a.com and https://example-b.com and it will 'just work'™

Source https://stackoverflow.com/questions/70625820

QUESTION

Docker compose with Dockerfile creates multiple images instead of one

Asked 2022-Mar-18 at 14:08

I have a docker-compose.yml and Dockerfile in the same folder. When running docker compose build this should result in one image and one container, but somehow I'm left with two images and two containers. The same docker-compose.yml and Dockerfile on my desktop however results in one image. What is happening here?

docker-compose.yml

...

ANSWER

Answered 2022-Mar-18 at 14:08

You're looking at two different build tools. The classic docker build performs each step using a container that gets committed into an dangling image. For some of those changes, the container isn't even run, it's just created. These are visible in the container and image listings. Deleting them may delete your build cache which will force a rebuild of the entire image, and while they report the size of all their layers, those layers are shared with the final created image, so deleting the dangling images often won't save much space (maybe a few kb for some json metadata). Because of that, people would leave them around.

The other build is using buildkit, which runs directly on containerd and runc, so you don't see the build artifacts in the docker container and image list. This is the preferred builder and enabled by default on newer versions of docker.

Source https://stackoverflow.com/questions/71525657

QUESTION

How to serve multiple container using bitnami nginx container

Asked 2022-Mar-08 at 14:33

I have containers in one server:

web-zamrud, api-zamrud and db-zamrud, all of them using docker bridge named zamrud-network
web-berlian, api-berlian and db-berlian, all of them using docker bridge named berlian-network
nginx container to serve web-zamrud and web-berlian.

Below is zamrud containers docker-compose

...

ANSWER

Answered 2022-Mar-08 at 14:33

In case anyone face same problem, what I did is make the bitnami nginx container down

Source https://stackoverflow.com/questions/71382402

QUESTION

Rails 6 ActionCable Unable to Upgrade WebSocket Request

Asked 2022-Feb-26 at 02:09

I have been struggling to get my Rails app deployed correctly for a while now, and have decided it is finally time to consult the community for some help. I have read just about every stackoverflow post on this issues, including the following, with no luck:

Rails 5 ActionCable fails to upgrade to WebSocket on Elastic Beanstalk -> From this post I ensured I was using an Application Load Balancer
ActionCable on AWS: Error during WebSocket handshake: Unexpected response code: 404 -> Configured an nginx proxy, with no change

Problem Description

I am using the following setup:

Ruby 2.7.5
Rails 6.1.0
GraphQL
React Frontend (separate repo)
Elastic Beanstalk
- Ruby 2.7 running on 64bit Amazon Linux 2/3.4.1
Application Load Balancer
Postgres ActionCable adapter

My application is deployed to AWS Elasticbeanstalk and all requests to /graphql are successful. However, when attempting to connect to /cable I get this error in my browser console:

...

ANSWER

Answered 2022-Feb-26 at 02:09

After posting on reddit, I was able to fix my issue by:

Removing my .ebextensions/nginx_proxy.config file.
Creating a new file, .platform/nginx/conf.d/elasticbeanstalk/websocket.conf with the contents:

Source https://stackoverflow.com/questions/71198267

QUESTION

ingress-nginx not working when using ingressClassName instead of kubernetes.io/ingress.class in annotations

Asked 2021-Nov-16 at 13:42

I have a baremetal cluster deployed using Kubespray with kubernetes 1.22.2, MetalLB, and ingress-nginx enabled. I am getting 404 Not found when trying to access any service deployed via helm when setting ingressClassName: nginx. However, everything works fine if I don't use ingressClassName: nginx but kubernetes.io/ingress.class: nginx instead in the helm chart values.yaml. How can I get it to work using ingressClassName?

These are my kubespray settings for inventory/mycluster/group_vars/k8s_cluster/addons.yml

...

ANSWER

Answered 2021-Nov-16 at 13:42

Running kubectl get ingressclass returned 'No resources found'.

That's the main reason of your issue.

Why?

When you are specifying ingressClassName: nginx in your Grafana values.yaml file you are setting your Ingress resource to use nginx Ingress class which does not exist.

I replicated your issue using minikube, MetalLB and NGINX Ingress installed via modified deploy.yaml file with commented IngressClass resource + set NGINX Ingress controller name to nginx as in your example. The result was exactly the same - ingressClassName: nginx didn't work (no address), but annotation kubernetes.io/ingress.class: nginx worked.

(For the below solution I'm using controller pod name ingress-nginx-controller-86c865f5c4-qwl2b, but in your case it will be different - check it using kubectl get pods -n ingress-nginx command. Also keep in mind it's kind of a workaround - usually ingressClass resource should be installed automatically with a whole installation of NGINX Ingress. I'm presenting this solution to understand why it's not worked for you before, and why it works with NGINX Ingress installed using helm)

In the logs of the Ingress NGINX controller I found (kubectl logs ingress-nginx-controller-86c865f5c4-qwl2b -n ingress-nginx):

Source https://stackoverflow.com/questions/69878685

QUESTION

Docker jrcs/letsencrypt-nginx-proxy-companion doesn't generate a proper certificate

Asked 2021-Nov-12 at 16:25

I'm following a tutorial to deploy Wordpress using Docker on a Ubuntu server. The tutorial is in this website.

It's important to mention that I already have two subdomains at this point, one for the Wordpress site and another for the phpMyAdmin site.

However the letsencrypt certificates seem to not be generated properly. I can access the website via http, but not https, and when I look at the certificate it doesn't look correct. In fact it doesn't seem to have one for my website.

To make everything easier I created a script to run all the steps fast:

...

ANSWER

Answered 2021-Nov-10 at 18:43

The issue seemed to be the number of times I had requested a certificate for those specific domains. I tried the deploy multiple times to figure out how to do it properly for the deployment server and also to write a proper version of the script, that I requested many times a certificate for two specific domains.

The issue was resolved after I tried a different domain and subdomain.

Source https://stackoverflow.com/questions/69869094

QUESTION

storage class in aks can't chown a directory

Asked 2021-Oct-28 at 11:49

i hope you're doing okay

im trying to build a cdap image that i havein gitlab in aks using argocd

the build works in my local kubernetes cluster with rook-ceph storage class but with managed premium storage class in aks it seems that something is wrong in permissions

here is my storage class :

...

ANSWER

Answered 2021-Oct-24 at 11:44

I make a bit of research, and it led me to this github issue: https://github.com/Azure/aks-engine/issues/1494

SMB mount options(including dir permission) could not be changed, it's by SMB proto design, while for disk(ext4, xfs) dir permission could be changed after mount close this issue, let me know if you have any question.

From what I see, there are no options chown after mounting it.

BUT

I also find a workaround that might apply to your issue: https://docs.openshift.com/container-platform/3.11/install_config/persistent_storage/persistent_storage_azure_file.html

It's Workaround for using MySQL with Azure File for Openshift, but I think it could work with your case.

Source https://stackoverflow.com/questions/69678103

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install nginx-proxy

You can download it from GitHub.
You can use nginx-proxy like any standard Python library. You will need to make sure that you have a development environment consisting of a Python distribution including header files, a compiler, pip, and git installed. Make sure that your pip, setuptools, and wheel are up to date. When using pip it is generally recommended to install packages in a virtual environment to avoid changes to the system.

Support

You can activate the IPv6 support for the nginx-proxy container by passing the value true to the ENABLE_IPV6 environment variable:. NginX does not support scoped IPv6 resolvers. In docker-entrypoint.sh the resolvers are parsed from resolv.conf, but any scoped IPv6 addreses will be removed. By default, docker uses IPv6-to-IPv4 NAT. This means all client connections from IPv6 addresses will show docker's internal IPv4 host address. To see true IPv6 client IP addresses, you must enable IPv6 and use ipv6nat. You must also disable the userland proxy by adding "userland-proxy": false to /etc/docker/daemon.json and restarting the daemon.

Find more information at: