Nextcloud Bad Gateway

This intrigues me for sure. Before I go that crazy. I set up IIS on port 80 on my desktop. Theoretically then if I forward 80 to 80 any on both the DMZ router (FIOS providing the WAN) and the real router (USG) and got port 80 open is that progress?

So far, I have been stuck forwarding a port from the USG into the FIOS router and getting that router to forward it out to the world sadly.

Hey I got this ALMOST working by forwarding 80 and 443 back to the main router from the Verizon one. So, progress.

Only issue is the docker compose script huge RIGHT at the end after "Server ready" - everything looks to be running but the compose didn't end gracefully. Did I miss a step or a command on my compose up or compose.yml file?

I got it, thanks again for the post. I'm having a lot of other issues with Nextcloud regarding uploads and downloads of large files, but I am trying to work through all the manual config and issues that seem to need done here. I'm not really effectively seeing great logging yet so trying to turn all that on as well.

What happened with the docker-compose is just that it never quit at the end of the script, I just ended the ssh window and it was fine (instead of doing a CTRL-C which deleted all the containers).

All in all, things are up and running anyway. I just need to now figure out the speed issues and more importantly the manual config changes needed so that files larger than 1 GB that I am trying to share out via sharelinks don't fail at the recipient end. There must be a reason that's happening and a config change I am missing, even though I have added a lot of stuff from help guides on resolving such issues.

Thanks again for getting me this far, your post was the easiest and best to use I have seen to get all this running quickly.

I'll share this link here for anyone who stumbles upon my issue. This info helped me fix my issue with large file sizes. I believe it has to do with timeouts set on nginx either on the letsencrypt side or the nextcloud side.

https://help.nextcloud.com/t/2…tsenrcypt-unraid/71375/10

What is not mentioned in many tutorials for newbs (like me) is that these are 3 separate apps here, and all 3 have their own cofig files buried deep in the docker appdata folders. So if you are having trouble, make sure you are in the right config file for the right docker. This one is (1) nextcloud (2) mariadb and (3) swag. Both nextcloud and swag have some manual config file work to do to speed it up and fix some other issues, and I may tweak some more but I've learned that getting into these files and making some changes can be very helpful.

I think we just need to make sure we are clear with which dockers' configs are changed, you did a pretty good job at that in your walkthrough, I have seen some areas that just say "modify the nginx proxy config" instead of being very clear what the file path and filename would be, etc, that kind of stuff is always helpful!

KM0201, thank you again!

I think you did a good job. Plus there are so many permutations of server out there and they all have their issues. I am using OpenMediaVault which is seems has some of its own quirks.

I'm having a few issues that maybe you can clue me in on. I'm new to the world of port forwarding and I have a weird double router situation going on but I am having some strange issues with my local IP when I try and access nextcloud.

All I am trying to really do is access it locally, without having to use my DuckDNS, and that seems to be failing for some reason after running these container scripts. I am sure this is user error.

I figured I'd go to https://LOCALIP:457 and see my NextCloud admin backend. I just see a "welcome to your swag instance" page. I believe that also happens when I go to https://DUCKDNSADDRESS:457. I can't seem to find ANY way to get back to the nextcloud admin backend (only the standard settings screen you see as an admin USER if that makes sense).

I also figured I'd go to http://LOCALIP:80 or just https://LOCALIP and browse my nextcloud locally. That also doesn't work. This must be a port forwarding issue here.

Quote from KM0201

OK, here's how I do it. not saying it's the only way, it's just simple and should have you up and running in about 15min. Everything that starts with a # needs to be adjusted for your system and then the # erased. Nothing other than those lines need to be changed despite what you've seen in other tutorials. All of the below assumes you have a basic understanding containers and command line (config paths, data paths, PUID/PGID, changing directories, nano, etc.)

You can use this in docker-compose or in a stack in portainer (I'd recommend using a stack as it will show if you have formatting errors):

Code

version: "2"
services:
  nextcloud:
    image: ghcr.io/linuxserver/nextcloud:latest
    container_name: nextcloud
    environment:
      #- PUID=1000
      #- PGID=100
    volumes:
      #- /path/to/nextcloud/config:/config
      #- /path/to/nextcloud/data:/data
      - /etc/localtime:/etc/localtime:ro
    depends_on:
      - mariadb
    ports:
      - 450:443
    restart: unless-stopped
  mariadb:
    image: ghcr.io/linuxserver/mariadb:latest
    container_name: nextclouddb
    environment:
      #- PUID=1000
      #- PGID=100
      #- MYSQL_ROOT_PASSWORD=YOUR_MYSQL_PASSWORD
    volumes:
      #- /path/to/mariadb/config:/config
      - /etc/localtime:/etc/localtime:ro
    restart: unless-stopped
  swag:
    image: linuxserver/swag
    container_name: swag
    cap_add:
      - NET_ADMIN
    environment:
      #- PUID=1000
      #- PGID=100
      - DNSPLUGIN=duckdns
      - URL=duckdns.org
      #- DUCKDNSTOKEN=YOUR_TOKEN
      #- SUBDOMAINS=YOUR_SUB_DOMAIN
      - ONLY_SUBDOMAINS=true
      - VALIDATION=http
      #- EMAIL=YOUR_EMAIL
    volumes:
      #- /path/to/swag/config:/config
      - /etc/localtime:/etc/localtime:ro
    depends_on:
       - nextcloud
    ports:
      - 457:443
      - 91:80
    restart: unless-stopped

Display More

This first part doesn't seem absolutely necessary, but for some reason I could never get it to work right unless I set it up locally first. I'm sure it was something I'm doing, I just can't figure out what..

1. Create all the directories and make all adjustments you need in docker-compose (you might want to delete old directories from previous attempts if you've been at this several times), then deploy the stack/docker compose file. If you use this set up exactly, in your router you'll need to make sure port 457 is forwarded to 443 and port 91 is forwarded to 80 (note: 457/91 are internal ports, 443/80 are external)

2. When done, go to nextcloud UI (https://your.omv.ip:450 , must use https and accept security risk)

3. Enter an admin user/password

4. Click setup database then mysql database

user root

password (see docker-compose, line 24 above)

database name: nextcloud

localhost: nextclouddb

5. Click Finish (this will take a few minutes as it downloads apps and sets up the database, be patient)

Once you're logged in you can complete a basic setup of Nextcloud, or move on to set it up with duckdns subdomains.

6. Navigate to /config/swag/nginx/proxy-confs

7. nano nextcloud.subdomain.conf.sample

8. Change subdomain to duckdns subdomain name (ie.. yoursubdomain.*, line 20 below)

Code

## 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' => '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 yoursubdomain.*;

    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 443;
        set $upstream_proto https;
        proxy_pass $upstream_proto://$upstream_app:$upstream_port;

        proxy_max_temp_file_size 2048m;
    }
}

Display More

9. Save (Contrl x ) then Enter and and use backspace to erase the ".sample" extension. Hit enter then Y to save..

10. Restart swag container (docker restart swag)

11. Navigate to: /config/nextcloud/www/nextcloud/config

12. nano config.php

13. Under trusted domains array add your domain (you should see your local IP address there as 0), be sure to add it before the ),

Code

1 => 'yoursubdomain.duckdns.org', 

14. Add or edit the lines below, after the ), and before the );

Code

'overwrite.cli.url' => 'https://yoursubdomain.duckdns.org',
'overwritehost' => 'yoursubdomain.duckdns.org',
'overwriteprotocol' => 'https',

When you're done, your config.php will look something like this (11, 23, 24, 25 are the lines I added in. A couple of those lines will already be there.. so you can either edit them as appropriate or delete them and add them in at the end like I did, either way just make sure there are no duplicates and it looks similar to the below)

PHP

<?php
$CONFIG = array (
  'memcache.local' => '\\OC\\Memcache\\APCu',
  'datadirectory' => '/data',
  'instanceid' => 'oc3wozk6kai4',
  'passwordsalt' => '2snos3M0EllfFy1CQH0Lah6kOEPyFC',
  'secret' => 'it8C+qSyNcafTBLDp8nHQCAq9o/Fs9nUOgd/gYNFN5/Ro4pW',
  'trusted_domains' => 
  array (
    0 => 'YOUR_LOCAL_IP:450',
    1 => 'yoursubdomain.duckdns.org',
  ),
  'dbtype' => 'mysql',
  'version' => '20.0.6.1',
  'dbname' => 'nextcloud',
  'dbhost' => 'nextclouddb',
  'dbport' => '',
  'dbtableprefix' => 'oc_',
  'mysql.utf8mb4' => true,
  'dbuser' => 'oc_admin',
  'dbpassword' => 'YfPeqGJ8LlsOIkXpgiEtf3bejjLtUK',
  'installed' => true,
  'overwrite.cli.url' => 'https://yoursubdomain.duckdns.org',
  'overwritehost' => 'yoursubdomain.duckdns.org',
  'overwriteprotocol' => 'https',
  );

Display More

15. Save and close (Cntrl x then Y to save)

16. Restart the Nextcloud container docker restart nextcloud

17. Navigate to https://yoursubdomain.duckdns.org and log in.

This is optional, but once you're done and you can log in to your subdomain properly and securely... If you want to disable insecure access from your local network, go back to your docker-compose file or stack and make this adjustment under the "nextcloud" portion

Code

    ports:
      - 450:443

to this

    #ports:
      #- 450:443

Then redeploy the stack or docker-compose file and you'll no longer have local access.

You're done.

Display More

Wonderful tutorial, which I encountered quite late. Considering all the energy and time I spend, I slap myself why I haven't seen this post before.

Although I already had a working Nextcloud, I came across your simple tutorial and installed it from scratch on uSD to try it out.

I read many articles, watched many youtube, now I feel sorry for my lost time and energy.

This tutorial deserves a separate topic.

A treasure for very novice, rookies like me.

Please make this tutorial more visible!!!

Quote from macom

It already is

I already arrived from here

Hard question then.

I am inexperienced as I am using Nextcloud for the first time.

I cannot use it with the link https://subdomain.duckdns.org in the LAN. If I want to access Nextcloud in the LAN, I have to use the 192.168.1.36:450 connection.

Is this normal?

Quote from KM0201

Unless you want it that way... if you want to use a subdomain.... Go back and start at step 6 (since you seem to have it working locally).. and make sure your ports are forwarded in your router. (457 and 91 are internal, 443 and 80 are external)

I did these, I already have WAN usage.

I forwarded the ports.

If I turn off Wi-Fi on the phone, I get to the Nexcloud Clipboard.

But when I am in the LAN, the xxx.duckdns.org link directs me to the modem.

I have the same problem in macom 's tutorial and your tutorial. Of course if this is a problem

I would like to express my gratitude to macom m again, it helped me a lot. Nexcloud would have been completely out of my life if macom and Soma hadn't helped. Thanks again.