TARDIS Project

User Tools

Site Tools

Trace:
hosts:virtual_machines:web:userhomes_hosting

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
hosts:virtual_machines:web:userhomes_hosting [2025/02/09 17:46] – emily747hosts:virtual_machines:web:userhomes_hosting [2025/02/17 20:29] (current) – Say correct reverse proxies. Add a couple links merlin
Line 13: Line 13:
  
 This is totally possible by adding the domain and forwarding it manually to nginx. See the step-by-step below. Some steps require an admin, so please contact an admin if you would like this (we're friendly, I promise!). This is totally possible by adding the domain and forwarding it manually to nginx. See the step-by-step below. Some steps require an admin, so please contact an admin if you would like this (we're friendly, I promise!).
 +
 +Currently working examples of this include https://mathsoc.uk and https://www.emilymiller.xyz.
  
 1. (Admin required) Add the domain to the users account. For instance, "example.com" and "www.example.com" \\ 1. (Admin required) Add the domain to the users account. For instance, "example.com" and "www.example.com" \\
Line 20: Line 22:
 Further Note: wildcard domains aren't handled well by Caddy, so putting a wildcard domain will likely require extra configuration to make work. Roughly however, this should at least serve the site, albiet with a potentially broken SSL cert. \\ Further Note: wildcard domains aren't handled well by Caddy, so putting a wildcard domain will likely require extra configuration to make work. Roughly however, this should at least serve the site, albiet with a potentially broken SSL cert. \\
  
-2. Go into the console (console.tardisproject.uk) and select "Manage Endpoints".+2. Go into the console ([[https://console.tardisproject.uk|console.tardisproject.uk]]) and select "Manage Endpoints".
  
 3. Add a new proxy rule with the following settings. Note: You'll need to do this for each subdomain (which will usually be at least "example.com" and "www.example.com").  3. Add a new proxy rule with the following settings. Note: You'll need to do this for each subdomain (which will usually be at least "example.com" and "www.example.com"). 
Line 31: Line 33:
 **Where to proxy to:** **Where to proxy to:**
  
-Target IP: 192.168.0.14 (This is the internal IP address of the nginx server) \\ +Target IP: 192.168.0.14 (This is the internal IP address of [[hosts:virtual_machines:web:|hosts:virtual_machines:web]], which hosts [[https://git.tardisproject.uk/tardis/nix/-/blob/main/profiles/web/userhomes.nix|an nginx webserver which servers userhomes]]) \\ 
-Target Port: 8181 (This is the port nginx expecting traffic to come through on) \\ +Target Port: 8181 (This is the port where nginx is expecting traffic to come through on) \\ 
-Does the target expect HTTPS? No (SSL termination is handled seperately by caddy) \\+Does the target expect HTTPS? No (SSL termination is handled seperately by traefik) \\
  
 **Advanced** **Advanced**
Line 39: Line 41:
 Strip path prefix before sending to app? No \\ Strip path prefix before sending to app? No \\
 Redirect HTTP to HTTPS? Yes \\ Redirect HTTP to HTTPS? Yes \\
-Override the Host header: <your username>.tardis.ac (e.g. jdoe.tardis.ac) \\+Override the Host header: <your username>.tardis.ac (e.g. jdoe.tardis.ac, without this nginx won't know where to route the traffic) \\
  
  
hosts/virtual_machines/web/userhomes_hosting.1739123177.txt.gz · Last modified: 2025/02/09 17:46 by emily747