# /etc/nginx/sites-available/roundcube.conf
# need to be symlinked to /etc/nginx/sites-enabled/ and nginx -s reload (after removing default!)


### ganzer Block aus egroupware , weiss nicht ob für Roundcube benötigt
# redirects needs to use X-Forwarded-Proto too
#map $http_x_forwarded_proto $redirectscheme {
#    default $scheme;
#    https https;
#}
### Ende des auskomenntierten Blocks


# Anpassung für Roundcube, Infos von
# https://serverfault.com/questions/706694/use-nginx-as-reverse-proxy-for-multiple-servers

### port 80 nicht aktiv da nur Zugriff über SSL
#server {
#
#	server_name roundcube.beispiel.xyz;
#
#	# proxy into Roundcube container
#	location / {
#        proxy_set_header X-Real-IP $remote_addr;
#        proxy_set_header Host $host;
#        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
#        proxy_pass http://127.0.0.1:8081;
#    }
#}


server {

    server_name roundcube.beispiel.xyz; # managed by Certbot

	# proxy into Roundcube container
	location / {
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header Host $host;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_pass http://127.0.0.1:8081;
	}



    listen 443 ssl; # managed by Certbot
    ssl_certificate /etc/letsencrypt/live/egroupware.beispiel.xyz/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/egroupware.beispiel.xyz/privkey.pem; # managed by Certbot
    include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
    ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot

}

server {
    if ($host = roundcube.beispiel.xyz) {
        return 301 https://$host$request_uri;
    } # managed by Certbot


	listen 80 ;
    server_name roundcube.beispiel.xyz;
    return 404; # managed by Certbot


}