rproxy | 简单的反向代理用于内网穿透,支持HTTP/HTTPS转发 | Proxy library
kandi X-RAY | rproxy Summary
kandi X-RAY | rproxy Summary
简单的反向代理用于内网穿透,支持HTTP/HTTPS转发
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
- create zip file
- readPacket reads a single packet from conn .
- pkgMacOSApp adds the package information to the system .
- SetConfig set the TRProxyConfig
- windowsPkg is a wrapper for windows package .
- darwin package .
- EncodeCmd encodes a command
- DecodeRequest decodes an HTTP request .
- linux package
- read data from conn
rproxy Key Features
rproxy Examples and Code Snippets
Community Discussions
Trending Discussions on rproxy
QUESTION
I've set up a simple Nginx reverse proxy using the "official image" Docker container. I've set it up to act as a front end for three containers, but only one is working correctly. The others load their index.html, but then try to pull ancillary files with URLs that make Nginx think they're local files.
The Docker host is called otto. I have Docker containers for Home Assistant listening on port 8123, Statping on port 8080, and Portainer on port 9000. Because I'm tired of remembering port numbers, my proxy_pass is set up so http://otto/homeassistant/ redirects to http://otto:8123/, http://otto/statping/ to http://otto:8080/ and http://otto/portainer/ to http://otto:9000
But, only Portainer works. The other two load their index.html just fine, but then start trying to pull javascript files from /js/somefilename.js. This of course fails, because there's no http://otto/homeassistant or http://otto/statping on the front of it. Nginx then tries to find the file locally in /etc/nginx/html, fails, and gives up.
My question is why does Portainer work so flawlessly when the other two can't even load a home page?
I've tried disabling local file serving, by commenting out location / { }, but it doesn't matter.
I've tried assigning HTTP headers that I've seen in other examples, like this:
...ANSWER
Answered 2021-Mar-18 at 15:29The problem was exactly as @zigarn had pointed out in the comments. The apps being reverse proxied were relying on URLs with a base of / and not something like /statping or /homeassistant. Portainer worked because it apparently does not have that same dependency.
The solution is to move away from reverse proxying based on URL and instead use reverse proxy based on hostname. So now, rather than http://otto.local/statping/, I have http://statping.otto.local/ All reverse proxied apps load their home pages with this arrangement, so I feel like it's a win.
There area still some minor troubles with homeassistant and node-red, and I suspect this may be due to a need to reverse proxy web sockets. Still researching that, but the main objective of getting them all to pull up a home page or login page has been accomplished.
Now for the gory details...
Because this is a home setup, with the standard, basic functionality internet router, I had to put some work into setting up a DNS server before names like statping.otto.local or homeassistant.otto.local would resolve.
To do this, I installed bind 9 on otto, the same host running the Docker containers. It's installed from a package on Raspberry Pi OS rather than as a container. The trick was to use a wildcard CNAME in addition to the DNS entry for otto.local.
With *.otto.local pointing to otto.local, I am able to get any combination of {appname}.otto.local to resolve to otto's IP address. Now, typing http://portainer.otto.local et al. gets me to otto and Nginx.
In the Nginx config, it's a matter of creating several entries that look like this one:
QUESTION
I'm working on a use case to create a Docker container for an apache server for a CMS application.
Below is the folder structure for the docket container.
...ANSWER
Answered 2018-Nov-19 at 22:00OK, I was able to reproduce your issue using the files you provided. It's weird that you're not getting more info in the logs. But here's how I debugged it:
The fact that the status is
restarting
is bad - it means your container isn't staying up. I removed therestart: always
line, but got the same result.Let's narrow down the problem some more. I built your Dockerfile and ran it by running the following commands in the
httpd
directory:docker build -t apache-rproxy:latest . && docker run --rm -p 80:80 apache-rproxy:latest
. Unfortunately, I got the same error with no additional logs.Let's debug some more. Try the same command with the official httpd image:
docker run --rm -p 80:80 httpd:2.4
. Notice that this time, httpd starts and begins logging, and the container remains alive.
Now, the only difference between the httpd:2.4
image and the apache-rproxy:latest
image is your config file. So you something in your httpd.conf
is preventing apache from starting (or even logging anything). Work out what the problem is there and I think you'll have a working setup.
QUESTION
I am trying to use selenium and python to connect to a site. I then decided to add proxies to the whole process and use them to connect to the site. The proxies are scraped using Proxy Broker (python module). So I can get a lot of proxies scraped. I then save it to a text file and when I need to connect I randomly choose it from the text file. However here is where the problem arises. When connecting to the site the proxies sometimes don't work. Currently this is the code I am using:
...ANSWER
Answered 2018-Sep-08 at 13:14Well, I gave a look to the proxybroker documentation and I found that the best solution is to check built-in attribute proxy.is_working
:
QUESTION
A minor issue but I want to run docker containers in dev with docker run --rm
so that I don't have to remove them after I stop them, especially since I'm changing the command line parameters with virtually every run.
However my containers pump out lots of logging onto stdout
if I don't use docker run -d
.
Then I can't use --rm
anymore, because docker
complains:
ANSWER
Answered 2017-Dec-07 at 14:24I cannot reproduce this.
The following detaches fine and can be stopped just fine (resulting in removal, as required) in Docker version 17.09.0-ce, build afdb6d4
:
QUESTION
I'm having no luck putting a bare bones nginx reverse proxy in front of my java/tomcat app, which works fine on port 8080 . My browser gets back an empty response, and I see no logging or errors on the servers.
This is my nginx Dockerfile:
...ANSWER
Answered 2017-Nov-30 at 16:18The command to run docker coniatner should start with
QUESTION
I am trying to test the last version of Liferay (Liferay 7.0-ga4) and install it behind a reverse proxy (nginx). I am using docker and docker compose for testing purposes, and I create a dummy domain docker.domain.com
.
Liferay works fine if I access directly to its url and no reverse proxy is configured.
Also, I have success to install Liferay behind the nginx server if I use the root location:
...ANSWER
Answered 2017-Sep-13 at 14:39Seems that the problem was with the the trailing slash in proxy_pass. It is what makes a difference. Following this example, the nginx configuration file will be:
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install rproxy
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page