HTTP Routing: Difference between revisions
From Pumping Station One
Created page with "We have a reverse-proxy running for space.pumpingstationone.org. Contact the CTO if you would like a CNAME record added for yoursubdomain.pumpingstationone.org. https should..." |
No edit summary |
||
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
We have a reverse-proxy running for space.pumpingstationone.org. Contact the CTO if you would like a CNAME record added for yoursubdomain.pumpingstationone.org. https should be working for all listeners on :443, provided by wildcard SSL cert for *.pumpingstationone.org. Currently the reverse proxy is handled by nginx running on www1.ad.pumpingstationone.org. To create a vhost on the server, authenticate with www1 via your AD credentials and use sudo access to create /etc/nginx/sites-available/example.pumpingstationone.org. | {{mbox |type=warning |text=This information is out of date. [[IT Infrastructure|Up-to-date IT information can be found here]] }} | ||
We have a reverse-proxy running for space.pumpingstationone.org. Contact the CTO if you would like a CNAME record added for yoursubdomain.pumpingstationone.org. https should be working for all listeners on :443, provided by wildcard SSL cert for *.pumpingstationone.org. | |||
Currently the reverse proxy is handled by nginx running on www1.ad.pumpingstationone.org. To create a vhost on the server, authenticate with www1 via your AD credentials and use sudo access to create /etc/nginx/sites-available/example.pumpingstationone.org. | |||
upstream example { | upstream example { | ||
