• Posts

  • Joined

  • Last visited

Everything posted by SNReloaded

  1. Hello! I was trying to use the Caddyv2 container for ssl authentication, but I was having issues with that (mostly that it would start up, but immediately shut down.) I was try to go with caddy due to it being suggested on the official site: Is there a guide for configuring this on unraid instead of a standard Unix system? or is a different technology suggested for Unraid than on other devices? Thanks!
  2. I'm really trying here, & I've spent the last half hour trying to figure out how to create a custom docker network. I looked through the entirety of the docker faq, & it was not described there. I did set nextcloud's docker image to use 443, & I changed proxy-confs upstream to use 443. I set custom: br0 to use, & I tried to do that as well for SWAG, but then I got this docker run error root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='swag' --net='br0' --ip='' -e TZ="America/Chicago" -e HOST_OS="Unraid" -e 'TCP_PORT_80'='1880' -e 'TCP_PORT_443'='443' -e 'EMAIL'='' -e 'URL'='' -e 'SUBDOMAINS'='home,' -e 'ONLY_SUBDOMAINS'='true' -e 'VALIDATION'='http' -e 'DNSPLUGIN'='' -e 'EXTRA_DOMAINS'='' -e 'STAGING'='false' -e 'DUCKDNSTOKEN'='' -e 'PROPAGATION'='' -e 'PUID'='99' -e 'PGID'='100' -v '/mnt/user/appdata/swag':'/config':'rw' --cap-add=NET_ADMIN 'linuxserver/swag' 4006ab65315419844b517497e8efa997b2e6ff31ded83a9197708da1d0afe837 /usr/bin/docker: Error response from daemon: Address already in use. This makes sense that the IP is already in use, but I'm not understanding how to get both swag & nextcloud to use the docker network
  3. Here's the docker run (it would have been faster to just say "edit the config & it'll give the run command") SWAG: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='swag' --net='bridge' -e TZ="America/Chicago" -e HOST_OS="Unraid" -e 'EMAIL'='' -e 'URL'='' -e 'SUBDOMAINS'='home,' -e 'ONLY_SUBDOMAINS'='true' -e 'VALIDATION'='http' -e 'DNSPLUGIN'='' -e 'EXTRA_DOMAINS'='' -e 'STAGING'='false' -e 'DUCKDNSTOKEN'='' -e 'PROPAGATION'='' -e 'PUID'='99' -e 'PGID'='100' -p '1880:80/tcp' -p '18443:443/tcp' -v '/mnt/user/appdata/swag':'/config':'rw' --cap-add=NET_ADMIN 'linuxserver/swag' 1eb3775caaf9f7ab02460256f1579bb3ce6e34d1174f318cfcee9dd775e67091 Nextcloud: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='nextcloud' --net='bridge' -e TZ="America/Chicago" -e HOST_OS="Unraid" -e 'PUID'='99' -e 'PGID'='100' -p '444:443/tcp' -v '/mnt/user/nextcloud/':'/data':'rw' -v '/mnt/user/appdata/nextcloud':'/config':'rw' 'linuxserver/nextcloud' 22e325a33923bd38a0e9e96159c43bbb20351efa7bcd948abdc4337ccce2d5fa
  4. I changed the ports because I was getting an error with certbot about the port already being in use (80/443), so I switched to 1880/18443 to be out of range of "commonly used ports". Also, I know what a docker run command is when using the terminal, but I've never seen the docker run command myself from unraid. How do I go about getting the docker run command?
  5. Hello. I'm trying to get the reverse proxy for the Nextcloud docker container working through swag. I was following the steps located at for setup. However, after I'm done, I'm still getting a 502 bad gateway. Any help would be appreciated. I am including both the swag config & the nextcloud config below nextcloud.subdomain.conf ## Version 2020/12/09 # make sure that your dns has a cname set for nextcloud # assuming this container is called "swag", edit your nextcloud container's config # located at /config/www/nextcloud/config/config.php and add the following lines before the ");": # 'trusted_proxies' => ['swag'], # 'overwrite.cli.url' => '', # 'overwritehost' => '', # 'overwriteprotocol' => 'https', # # Also don't forget to add your domain name to the trusted domains array. It should look somewhat like this: # array ( # 0 => '', # This line may look different on your setup, don't modify it. # 1 => '', # ), server { listen 443 ssl; listen [::]:443 ssl; server_name home.*; include /config/nginx/ssl.conf; client_max_body_size 0; location / { include /config/nginx/proxy.conf; resolver valid=30s; set $upstream_app nextcloud; set $upstream_port 18443; set $upstream_proto https; proxy_pass $upstream_proto://$upstream_app:$upstream_port; proxy_max_temp_file_size 2048m; } } nextcloud's config.php <?php $CONFIG = array ( 'memcache.local' => '\\OC\\Memcache\\APCu', 'datadirectory' => '/data', 'instanceid' => 'oczev557ynye', 'passwordsalt' => 'wmc1ZRU+NWpNcgcYuvHtj8inWjqPou', 'secret' => '61yA7Ruh4yWk39ykw7EUZ9L2PcApyvYSdhYVn75Tf1/0A0m1', 'trusted_domains' => array ( 0 => '', 1 => '', 2 => 'praemunio:444' ), 'dbtype' => 'mysql', 'version' => '', 'overwrite.cli.url' => '', 'dbname' => 'nextcloud', 'dbhost' => '', 'dbport' => '', 'dbtableprefix' => 'oc_', 'mysql.utf8mb4' => true, 'dbuser' => 'nextcloud', 'dbpassword' => 'nextcloudROOT', 'installed' => true, 'filesystem_check_changes' => 1, 'trusted_proxies' => ['swag'], 'overwrite.cli.url' => '', 'overwritehost' => '', 'overwriteprotocol' => 'https', ); Also, I have a DD-WRT enabled router, with port-from being 80/443, & port-to being 1880/18443. The cert validation did succeed with this. I've tried running nextcloud with both port 443 & 444 for the config in unraid. Any help would be greatly appreciated! Edit: As a followup to this, I now have no access to nextcloud whatsoever. I'm tempted to just drop the swag redirect, & just tell people "yes, it's really safe, trust me"