SWAG - LetsEncrypt + Reverse Proxy: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 25: | Line 25: | ||
#### Add overwriteprotocol => 'https', | #### Add overwriteprotocol => 'https', | ||
### [https://youtu.be/I0lhZc25Sro?t=1447 Swag\nginx\proxy-confs\nextcloud-subdomain Config] (video shows letsencrypt folder not SWAG) | ### [https://youtu.be/I0lhZc25Sro?t=1447 Swag\nginx\proxy-confs\nextcloud-subdomain Config] (video shows letsencrypt folder not SWAG) | ||
#### contents should be fine as is. save-as/rename without the '.sample' extension. | #### contents should be fine as is. save-as/rename without the '.sample' extension.<br/>Note: sample assumes you use 'nextcloud' as the subdomain name. If not, you need to update to the actually used name. | ||
## [https://youtu.be/I0lhZc25Sro?t=1108 sonnar SWAG config] | ## [https://youtu.be/I0lhZc25Sro?t=1108 sonnar SWAG config] | ||
*Todo | *Todo | ||
Latest revision as of 17:31, 29 January 2021
- Install
- Create custom docker network for containers
- Disable Docker Service temporarily
- Enable Docker Advanced View
- Preserve User Networks = yes
- Enable Docker Service
- Open unraid console and create "proxynet" with
- docker network create ''proxynet''
- Install SWAG
- Go to Apps tab and search for SWAG
- Install with the same "proxynet" Network Type you created earlier
- Follow the video and copy settings from your existing LetEncrypt container if any.
- HTTPS port should be set to the internal target value for the router's external 443 port forward.
- Setup Reverse Proxy configs
- NextCloud
- Nextcloud container changes
- Change Nextcloud container to use "proxynet" Network Type
- Change the HTTPS port to something different if it had previously been the target of the router's 443 port forward
- Update NextCloud config.php
- Add trusted domain
- Change overwrite.cli.url to https://nextcloud.your.domain
- Add overwritehost => 'nextcloud.your.domain',
- Add overwriteprotocol => 'https',
- Swag\nginx\proxy-confs\nextcloud-subdomain Config (video shows letsencrypt folder not SWAG)
- contents should be fine as is. save-as/rename without the '.sample' extension.
Note: sample assumes you use 'nextcloud' as the subdomain name. If not, you need to update to the actually used name.
- contents should be fine as is. save-as/rename without the '.sample' extension.
- Nextcloud container changes
- sonnar SWAG config
- NextCloud
- Todo
- Notes
- References