Running nextcloud through Nginx Proxy Manager requires some additional settings.
![](https://i0.wp.com/kulmosen.dk/wp-content/uploads/2023/03/Screenshot-2023-03-13-at-16.08.23.png?resize=443%2C446&ssl=1)
![](https://i0.wp.com/kulmosen.dk/wp-content/uploads/2023/03/Screenshot-2023-03-13-at-16.08.33.png?resize=426%2C229&ssl=1)
![](https://i0.wp.com/kulmosen.dk/wp-content/uploads/2023/03/Screenshot-2023-03-13-at-16.09.19.png?resize=427%2C474&ssl=1)
![](https://i0.wp.com/kulmosen.dk/wp-content/uploads/2023/03/Screenshot-2023-03-13-at-16.09.45.png?resize=425%2C611&ssl=1)
This last part is the most important because it make sure that the redirect for caldav and carddav works as intended.
client_body_buffer_size 512k;
proxy_read_timeout 86400s;
client_max_body_size 0;
location /.well-known/carddav {
return 301 $scheme://$host/remote.php/dav;
}
location /.well-known/caldav {
return 301 $scheme://$host/remote.php/dav;
}
location /.well-known/webfinger {
return 301 $scheme://$host/index.php/.well-known/webfinger;
}
location /.well-known/nodeinfo{
return 301 $scheme://$host/index.php/.well-known/nodeinfo;
}
Be First to Comment