Asgart

Yes, basically what I did, was changing the container name of the 'swag' container to 'JulianSeidel'. I'm just gonna post a few screenshots here.. These are my 'swag' container settings: This is my 'nextcloud' container: Then I went into the appdata\swag\nginx\proxy-confs folder to edit the nextcloud.subdomain.conf file (while erasing the .sample to make it a .conf file): # 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' => 'https://nextcloud.your-domain.com/', # 'overwritehost' => 'nextcloud.your-domain.com', # 'overwriteprotocol' => 'https', # # Also don't forget to add your domain name to the trusted domains array. It should look somewhat like this: # array ( # 0 => '192.168.0.1:444', # This line may look different on your setup, don't modify it. # 1 => 'nextcloud.your-domain.com', # ), server { listen 443 ssl; listen [::]:443 ssl; server_name nextcloud.*; include /config/nginx/ssl.conf; client_max_body_size 0; location / { include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_app nextcloud; set $upstream_port 444; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port; proxy_max_temp_file_size 2048m; } } I also went into the appdata\nextcloud\www\nextcloud\config folder to edit the config.php file (I changed my personal data to xxx for this showcase): <?php $CONFIG = array ( 'memcache.local' => '\\OC\\Memcache\\APCu', 'datadirectory' => '/data', 'instanceid' => 'oc82pfr3kbbl', 'passwordsalt' => 'jlLdTzjYNONZ3/pf6skVd7YiwRTW/Z', 'secret' => 'D32AynuD7qIf5+CBT/KrckjYiiPICbVog96kxzQ8SJjnnhJo', 'trusted_domains' => array ( 0 => '192.168.178.46:444', 1 => 'nextcloud.xxx.net', ), 'dbtype' => 'mysql', 'version' => '21.0.0.18', 'trusted_proxies' => array ( 0 => 'JulianSeidel', ), 'overwrite.cli.url' => 'https://nextcloud.xxx.net/', 'overwritehost' => 'nextcloud.xxx.net', 'overwriteprotocol' => 'https', 'dbname' => 'nextcloud', 'dbhost' => '192.168.178.46:3306', 'dbport' => '', 'dbtableprefix' => 'oc_', 'mysql.utf8mb4' => true, 'dbuser' => 'nextcloud', 'dbpassword' => 'xxx', 'installed' => true, ); The subdomain is pingable, so I think that should not be the problem. The plex and emby docker are working fine with their own subdomains, but if I try to reach nextcloud, I'm always getting a "502 Bad Gateway nginx/1.18.0" error message.. I'm really at a loss here

Hi, that's not it. I created a custom bridge where swag, emby, plex and nextcloud are running on. The other dockers are working fine, just nextcloud just isn't working. It definitely is on the same custom bridge.

I'm having the exact same problem! SWAG is working for me with the emby and plex docker, but I can't get nextcloud to work. I'm always getting a "502 Bad Gateway" error. I tried it on different computers and on mobile, so it shouldn't be my router or browser causing this.. Does anyone have an idea how to fix this?