me/env-docker
me/env-docker
1
1
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Rename example.com to proxy.example.com.

Browse Source
This commit is contained in:
Hyperling 2023-07-08 12:34:54 -07:00
parent a122f651ac
commit cb51b41fe3
1 changed files with 10 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
Config/ReverseProxy/config/conf.d/example.com → Config/ReverseProxy/config/conf.d/proxy.example.com
View File

@ -4,22 +4,22 @@
## Instructions ## ## Instructions ##
# Add this without the comment to your /etc/hosts to test that it is working, # Add this without the comment to your /etc/hosts to test that it is working,
# YOUR_DOCKER_SERVER_IP example.com # YOUR_DOCKER_SERVER_IP proxy.example.com
# If testing locally on a workstation, # If testing locally on a workstation,
# 127.0.0.1 example.com # 127.0.0.1 proxy.example.com
# Then to test, first start the container, # Then to test, first start the container,
# cd $DOCKER_HOME/Config/ReverseProxy && docker compose build && docker compose up -d # cd $DOCKER_HOME/Config/ReverseProxy && docker compose build && docker compose up -d
# Then from the system with the modified /etc/hosts, # Then from the system with the modified /etc/hosts,
# curl --insecure example.com # curl --insecure proxy.example.com
# You should see activity in the container log as well as the contents of the # You should see activity in the container log as well as the contents of the
# proxied website in the terminal, NOT example.com. If using a browser then you # proxied website in the terminal, NOT proxy.example.com. If using a browser then you
# should notice that the URL is still example.com but the website is correct. # should notice that the URL is still proxy.example.com but the website is correct.
# Force HTTPS # Force HTTPS
server { server {
listen 80; listen 80;
server_name example.com; server_name proxy.example.com;
# Redirect to a more secure protocol. # Redirect to a more secure protocol.
return 301 https://$host$request_uri; return 301 https://$host$request_uri;
@ -30,11 +30,11 @@ server {
server { server {
listen 443 ssl; listen 443 ssl;
server_name example.com; server_name proxy.example.com;
# The certs being used for the website. # The certs being used for the website.
ssl_certificate /etc/nginx/certs/example.com/fullchain.pem; ssl_certificate /etc/nginx/certs/proxy.example.com/fullchain.pem;
ssl_certificate_key /etc/nginx/certs/example.com/privkey.pem; ssl_certificate_key /etc/nginx/certs/proxy.example.com/privkey.pem;
# Send traffic to upstream server # Send traffic to upstream server
location / { location / {
@ -59,7 +59,7 @@ server {
# Or alternatively, do it like the force of HTTPS if not your server. # Or alternatively, do it like the force of HTTPS if not your server.
#return 301 https://website.name/$request_uri; #return 301 https://website.name/$request_uri;
# This should forward you from 'example.com' to a real site: # This should forward you from 'proxy.example.com' to a real site:
proxy_pass https://hyperling.com; proxy_pass https://hyperling.com;
} }