I have trouble setting up swag as a proxy on unraid

[Reikasa_]

Hello smart people,

 

I have unraid running on a server here. 
My plan is to have my instance of nextcloud accessible over http/https.
I have already setup a dyndns service, the necessary portforwarding and swag as a proxy to the point that I reach the swag startup page when I try to connect over my domain.
Now I struggle to forward that connection to my nextcloud instance... 
I tried following a few tutorials and I always think I edit all the necessary configs the right way, but I never managed to connect to nextcloud.
Sometimes I wouldn't be able to access nextcloud at all anymore and sometimes I couldn't access the swag page anymore because of a "502 bad gateway" error.

Any help is very much appreciated!

best regards

[Jarsky]

On 6/28/2021 at 7:02 AM, Reikasa_ said:

Hello smart people,

 

I have unraid running on a server here. 
My plan is to have my instance of nextcloud accessible over http/https.
I have already setup a dyndns service, the necessary portforwarding and swag as a proxy to the point that I reach the swag startup page when I try to connect over my domain.
Now I struggle to forward that connection to my nextcloud instance... 
I tried following a few tutorials and I always think I edit all the necessary configs the right way, but I never managed to connect to nextcloud.
Sometimes I wouldn't be able to access nextcloud at all anymore and sometimes I couldn't access the swag page anymore because of a "502 bad gateway" error.

Any help is very much appreciated!

best regards

 

So the Swag docker already comes with an example config for Nextcloud. 

Have you connected to the docker and gone to /config/nginx/proxy-confs and found the existing sample config?

You need to rename it from nextcloud.<domain>.conf.sample to nextcloud.<domain>.conf for Swag/Nginx to read it. Also check the variables are correct in the config. 

[Reikasa_]

On 6/29/2021 at 6:49 AM, Jarsky said:

 

So the Swag docker already comes with an example config for Nextcloud. 

Have you connected to the docker and gone to /config/nginx/proxy-confs and found the existing sample config?

You need to rename it from nextcloud.<domain>.conf.sample to nextcloud.<domain>.conf for Swag/Nginx to read it. Also check the variables are correct in the config. 

Yes I did try using that file.
I tried both renaming it as nextcloud.<insert my domain name>.conf and just nextcloud.subdomain.conf.
Of course I also edited the content according to tutorials I found online.
But I still only get to the swag config site that tells me I should set it up properly.

I'll attach the config file of swag.
I did not yet edit the nextcloud config, but from what I understand that should only matter for logging in, I should still get further than swag if it is properly setup.

[Reikasa_]

I managed to fix it by adding these two attached lines into the site config of swag under appdata/swag/nginx/site-configs/default

[Jarsky]

12 hours ago, Reikasa_ said:

I managed to fix it by adding these two attached lines into the site config of swag under appdata/swag/nginx/site-configs/default

 

Nice work 

I was going to point out that that nextcloud.conf points to an internal name of https://nextcloud in Swag, so there must be another proxy_pass configuration in a default/global config for configuring the actual hostname/ip 

[coreysmall]

On 6/30/2021 at 10:11 AM, Reikasa_ said:

I managed to fix it by adding these two attached lines into the site config of swag under appdata/swag/nginx/site-configs/default

What does the IP 192.168.178.47 reference for I have tried this with both the IP of the SWAG docker container and the Unraid server and it just stops working completely instead of the 502 error.