2023-07-05 18:09:06 -07:00
|
|
|
# 2022-10-05 Hyperling
|
|
|
|
# A dummy test file since true scripts are being kept private.
|
|
|
|
# This should help anyone understand how the project is being used.
|
|
|
|
|
2023-07-05 20:02:50 -07:00
|
|
|
## Instructions ##
|
|
|
|
# Add this without the comment to your /etc/hosts to test that it is working,
|
|
|
|
# YOUR_DOCKER_SERVER_IP example.com
|
|
|
|
# If testing locally on a workstation,
|
|
|
|
# 127.0.0.1 example.com
|
|
|
|
# Then to test, first start the container,
|
|
|
|
# cd $DOCKER_HOME/Config/ReverseProxy && docker compose build && docker compose up -d
|
|
|
|
# Then from the system with the modified /etc/hosts,
|
|
|
|
# curl --insecure example.com
|
2023-07-08 11:31:37 -07:00
|
|
|
# You should see activity in the container log as well as the contents of the
|
2023-07-05 20:02:50 -07:00
|
|
|
# proxied website in the terminal, NOT example.com. If using a browser then you
|
|
|
|
# should notice that the URL is still example.com but the website is correct.
|
|
|
|
|
2023-07-05 18:09:06 -07:00
|
|
|
# Force HTTPS
|
|
|
|
server {
|
|
|
|
|
|
|
|
listen 80;
|
2023-07-05 20:02:50 -07:00
|
|
|
server_name example.com;
|
2023-07-05 18:09:06 -07:00
|
|
|
|
2023-07-05 18:36:10 -07:00
|
|
|
# Redirect to a more secure protocol.
|
2023-07-05 18:09:06 -07:00
|
|
|
return 301 https://$host$request_uri;
|
|
|
|
|
|
|
|
}
|
|
|
|
|
2023-07-05 18:36:10 -07:00
|
|
|
# Serve Resource
|
2023-07-05 18:09:06 -07:00
|
|
|
server {
|
|
|
|
|
2023-07-05 20:02:50 -07:00
|
|
|
listen 443 ssl;
|
|
|
|
server_name example.com;
|
2023-07-05 18:09:06 -07:00
|
|
|
|
2023-07-05 20:02:50 -07:00
|
|
|
# The certs being used for the website.
|
2023-07-05 21:17:14 -07:00
|
|
|
ssl_certificate /etc/nginx/certs/example.com/fullchain.pem;
|
|
|
|
ssl_certificate_key /etc/nginx/certs/example.com/privkey.pem;
|
2023-07-05 18:09:06 -07:00
|
|
|
|
|
|
|
# Send traffic to upstream server
|
|
|
|
location / {
|
2023-07-08 11:31:37 -07:00
|
|
|
proxy_set_header Host $host;
|
|
|
|
proxy_set_header X-Real-IP $remote_addr;
|
2023-07-05 18:09:06 -07:00
|
|
|
proxy_set_header X-Forwarded-Proto https;
|
2023-07-08 11:31:37 -07:00
|
|
|
proxy_set_header X-Forwarded-For $proxy_add_x_forwaded_for;
|
2023-07-05 18:36:10 -07:00
|
|
|
|
|
|
|
## General format is PROTOCOL://SERVER:PORT. For example:
|
|
|
|
#
|
|
|
|
# If using a domain name:
|
|
|
|
#proxy_pass http://YOUR_SERVER_NAME:8080;
|
|
|
|
#
|
|
|
|
# If using an IP address:
|
|
|
|
#proxy_pass http://192.168.1.80:8080;
|
|
|
|
#
|
|
|
|
# If forwarding to an external source:
|
|
|
|
#proxy_pass https://website.name/URI;
|
|
|
|
#
|
2023-07-08 11:31:37 -07:00
|
|
|
# Or alternatively, do it like the force of HTTPS if not your server.
|
2023-07-05 18:36:10 -07:00
|
|
|
#return 301 https://website.name/URI;
|
|
|
|
|
2023-07-05 20:02:50 -07:00
|
|
|
# This should forward you from 'example.com' to a real site:
|
|
|
|
proxy_pass https://hyperling.com;
|
2023-07-05 18:09:06 -07:00
|
|
|
}
|
|
|
|
|
2023-07-05 18:11:49 -07:00
|
|
|
}
|