So after google’ing for 3 days i give up and ask the wise ones of this forum.
The problem is that when i try to access my nextcloud service from a duckdns subdomain, i get the folowing error in my browser: “502 Bad Gateway”. Jellyfin works super fine though, which is why I’ve included my swag config for it).
(just to show a config file of a container working with swag atm)
I’ve included the entire compose file, even though most of it isn’t relevant. But maybe you can spot some conflicts i can’t.
Note: I’m not using linuxserver/nextcloud, but rather nextcloud official.
- Raspberry Pi 4. 2GB connected to my isp router with cable.
- Raspberry Pi OS 32-bit
- Open Media Vault (docker installed and running from here with portainer)
Docker compose file is run as a stack in portainer.
I actually was able to get access from my duckdns subdomain once, by replacing port “8080” with “80” in the “nextcloud.subdomain.conf”, (which doesn’t really make sense since I’m exposing port 8080 in the compose file. Or does it? ) and adding the suggested settings from top of “nextcloud.subdomain.conf.sample” to “nextcloud config.php” as follows:
‘trusted_proxies’ => [‘swag’],
‘overwrite.cli.url’ => ‘https://nextcloud.hidden.duckdns.org/’,
‘overwritehost’ => ‘nextcloud.hidden.duckdns.org’,
‘overwriteprotocol’ => ‘https’,
I reverted the settings as it seemed slow and “not feeling right” since the port is wrong??? Again im not sure?
I don’t have any SSL certificates setup in nextcloud config, hence the “http” instead of “https” in the “nextcloud.subdomain.conf”.
Thank you in advance!
I am trying to access nextcloud through nextcloud.mysubdomain.duckdns.NOT-A-LINK-OMG
I have tried from Microsoft Edge (pc), Firefox (pc) and Firefox Android.