Tag Info

Hot answers tagged

3

There is nothing special in the server log which shows a problem at the site of nginx. But, you description clearly indicates a problem in the clients network, i.e. only clients in the same network are affected all clients in the same network are affected if client connects to another network while experiencing the problem, the problem no longer occurs ...


2

It is possible to do this job, but not just with a DNS entry. You need to have a firewall in front of the web server that is able to do a port forward/modification. Then a request to example.com/contact can before forwarded to port 5080 on your Apache server's internal IP address as it passes through the firewall, or a request to example.net/register could ...


2

Your problem is that you are using proxy_pass inside server block, which is not allowed. Try using: server { server_name Subdomain.domain.eu; location / { proxy_set_header X-Real-IP $remote_addr; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_pass http://10.0.2.33:80; ...


1

This will do what you are asking for create the following file /etc/nginx/sites-available/domain1.com with the following contents upstream backend1 { ip_hash; server 10.10.10.10; server 10.10.20.10; } server { listen 1.1.1.1:80; listen 1.1.1.2:80; server_name www.domain1.com; location / { proxy_pass http://backend1; ...


1

I suggest you to enable AJP connector in both Tomcat and Apache httpd. This binary protocol is dedicated for Java HTTP proxying. Using it may save you configuration time and effort and lower bandwith and resource requirement. Btw., <Proxy *> directive is irrelevant on reverse proxies.



Only top voted, non community-wiki answers of a minimum length are eligible