pad (HedgeDoc) und cloud (NextCloud) dazu
cloud braucht noch etwas Arbeit, insbesondere die Abslage der Daten in /data und die Keycloak-Anbindung.
This commit is contained in:
		
					parent
					
						
							
								06233d22d5
							
						
					
				
			
			
				commit
				
					
						dff8f0ee8b
					
				
			
		
					 10 changed files with 260 additions and 4 deletions
				
			
		|  | @ -0,0 +1,42 @@ | |||
| # partly generated 2022-01-08, Mozilla Guideline v5.6, nginx 1.17.7, OpenSSL 1.1.1k, intermediate configuration | ||||
| # https://ssl-config.mozilla.org/#server=nginx&version=1.17.7&config=intermediate&openssl=1.1.1k&guideline=5.6 | ||||
| server { | ||||
|     # Listen on a custom port for the proxy protocol. | ||||
|     listen 8443 ssl http2 proxy_protocol; | ||||
|     # Make use of the ngx_http_realip_module to set the $remote_addr and | ||||
|     # $remote_port to the client address and client port, when using proxy | ||||
|     # protocol. | ||||
|     # First set our proxy protocol proxy as trusted. | ||||
|     set_real_ip_from 172.31.17.140; | ||||
|     # Then tell the realip_module to get the addreses from the proxy protocol | ||||
|     # header. | ||||
|     real_ip_header proxy_protocol; | ||||
| 
 | ||||
|     server_name cloud.hamburg.ccc.de; | ||||
| 
 | ||||
|     ssl_certificate /etc/letsencrypt/live/cloud.hamburg.ccc.de/fullchain.pem; | ||||
|     ssl_certificate_key /etc/letsencrypt/live/cloud.hamburg.ccc.de/privkey.pem; | ||||
|     # verify chain of trust of OCSP response using Root CA and Intermediate certs | ||||
|     ssl_trusted_certificate /etc/letsencrypt/live/cloud.hamburg.ccc.de/chain.pem; | ||||
| 
 | ||||
|     # HSTS (ngx_http_headers_module is required) (63072000 seconds) | ||||
|     add_header Strict-Transport-Security "max-age=63072000" always; | ||||
| 
 | ||||
|     proxy_set_header Host $host; | ||||
|     proxy_set_header X-Forwarded-Host $host; | ||||
|     proxy_set_header X-Real-IP $remote_addr; | ||||
|     proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; | ||||
|     proxy_set_header X-Forwarded-Port 443; | ||||
|     # This is https in any case. | ||||
|     proxy_set_header X-Forwarded-Proto https; | ||||
|     # Hide the X-Forwarded header. | ||||
|     proxy_hide_header X-Forwarded; | ||||
|     # Assume we are the only Reverse Proxy (well using Proxy Protocol, but that | ||||
|     # is transparent). | ||||
|     # Also provide "_hidden" for by, since it's not relevant. | ||||
|     proxy_set_header Forwarded "for=$remote_addr;proto=https;host=$host;by=_hidden"; | ||||
| 
 | ||||
|     location / { | ||||
|         proxy_pass http://127.0.0.1:8080/; | ||||
|     } | ||||
| } | ||||
|  | @ -0,0 +1,42 @@ | |||
| # partly generated 2022-01-08, Mozilla Guideline v5.6, nginx 1.17.7, OpenSSL 1.1.1k, intermediate configuration | ||||
| # https://ssl-config.mozilla.org/#server=nginx&version=1.17.7&config=intermediate&openssl=1.1.1k&guideline=5.6 | ||||
| server { | ||||
|     # Listen on a custom port for the proxy protocol. | ||||
|     listen 8443 ssl http2 proxy_protocol; | ||||
|     # Make use of the ngx_http_realip_module to set the $remote_addr and | ||||
|     # $remote_port to the client address and client port, when using proxy | ||||
|     # protocol. | ||||
|     # First set our proxy protocol proxy as trusted. | ||||
|     set_real_ip_from 172.31.17.140; | ||||
|     # Then tell the realip_module to get the addreses from the proxy protocol | ||||
|     # header. | ||||
|     real_ip_header proxy_protocol; | ||||
| 
 | ||||
|     server_name pad.hamburg.ccc.de; | ||||
| 
 | ||||
|     ssl_certificate /etc/letsencrypt/live/pad.hamburg.ccc.de/fullchain.pem; | ||||
|     ssl_certificate_key /etc/letsencrypt/live/pad.hamburg.ccc.de/privkey.pem; | ||||
|     # verify chain of trust of OCSP response using Root CA and Intermediate certs | ||||
|     ssl_trusted_certificate /etc/letsencrypt/live/pad.hamburg.ccc.de/chain.pem; | ||||
| 
 | ||||
|     # HSTS (ngx_http_headers_module is required) (63072000 seconds) | ||||
|     add_header Strict-Transport-Security "max-age=63072000" always; | ||||
| 
 | ||||
|     proxy_set_header Host $host; | ||||
|     proxy_set_header X-Forwarded-Host $host; | ||||
|     proxy_set_header X-Real-IP $remote_addr; | ||||
|     proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; | ||||
|     proxy_set_header X-Forwarded-Port 443; | ||||
|     # This is https in any case. | ||||
|     proxy_set_header X-Forwarded-Proto https; | ||||
|     # Hide the X-Forwarded header. | ||||
|     proxy_hide_header X-Forwarded; | ||||
|     # Assume we are the only Reverse Proxy (well using Proxy Protocol, but that | ||||
|     # is transparent). | ||||
|     # Also provide "_hidden" for by, since it's not relevant. | ||||
|     proxy_set_header Forwarded "for=$remote_addr;proto=https;host=$host;by=_hidden"; | ||||
| 
 | ||||
|     location / { | ||||
|         proxy_pass http://127.0.0.1:3000/; | ||||
|     } | ||||
| } | ||||
|  | @ -1,6 +1,6 @@ | |||
| map $host $upstream_acme_challenge_host { | ||||
|     # Something like this should be here at some point: | ||||
|     # aes.ccchh.net 10.31.206.14:31820; | ||||
|     cloud.hamburg.ccc.de cloud-intern.hamburg.ccc.de:31820; | ||||
|     pad.hamburg.ccc.de pad-intern.hamburg.ccc.de:31820; | ||||
|     default ""; | ||||
| } | ||||
| 
 | ||||
|  |  | |||
|  | @ -15,9 +15,11 @@ events { | |||
| # Listen on port 443 as a reverse proxy and use PROXY Protocol for the | ||||
| # upstreams. | ||||
| stream { | ||||
|     resolver 212.12.50.158 192.76.134.90; | ||||
| 
 | ||||
|     map $ssl_preread_server_name $address { | ||||
|         # Something like this should be here at some point: | ||||
|         # aes.ccchh.net 10.31.206.14:8443; | ||||
|         cloud.hamburg.ccc.de cloud-intern.hamburg.ccc.de:8443; | ||||
|         pad.hamburg.ccc.de pad-intern.hamburg.ccc.de:8443; | ||||
|     } | ||||
| 
 | ||||
|     server { | ||||
|  |  | |||
		Loading…
	
	Add table
		Add a link
		
	
		Reference in a new issue