Jump to content

Nextcloud, Reverse Proxy, Lets Encrypt dns problems


reefdesign

Recommended Posts

Hi everyone,

 

I really need someones help on an issue im sure is something silly but im on day 10 of trying to get his figured out and im ready to hang myself!

 

Background:

i just found Unraid after being referrered by a friend and its awesome. Im wanting to setup a personal cloud.

I have a fresh install of Unraid 6.6.5 Trial Version with parity, array and cache drives all up and running. My server is headless and only has Unraid on it.

 

I have been trying to install and setup nextcloud using the following tutorials, following them verbatim:-

 

SpaceInvaderOne:  How to Setup Nextcloud on unRAID for your Own Personal Cloud Storage

                             How to Setup and Configure a Reverse Proxy on unRAID with LetsEncrypt & NGINX

 

CyanLabs: The Complete UnRAID reverse proxy, Duck DNS (dynamic dns) and letsencrypt guide

 

TechCoreDuo: How to install nextcloud on unRAID

 

I have tried each tutorial several times with completely fresh installs and I always get to the same point in all of them and then I hit the 'Wall'

 

That point is the issuing of the LetsEncrypt SSL certificate!

 

The log always comes back with an error that i have either a firewall or dns issue.

 

Here is what i have tried so far:

 

Tested my router forwarding using my desktop with a port listener and openportchecktool. On my desktop the ports are open, when i change to server ip the ports are not, even when unraid is up and running with dockers Duckdns, mariadb, Nextcloud and Let'sencrypt also running.

 

I have tried several Duckdns subdomains and even buying a domain from namecheap.com. When i search the subdomains using a dns lookup tool they all point back to my public ip.

 

So as i sit right now i have wiped everything clean, installed nextcloud, duckdns, mariadb and letsencrypt as per spaceinvaderone's tutorials and this is the letsencrypt error log:

 

 

Failed authorization procedure. reefcloud.duckdns.org (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://reefcloud.duckdns.org/.well-known/acme-challenge/b8jID0T2L1Hh__JALSPt2XB-etDFqRVk-ahbZvNSfaw: Timeout during connect (likely firewall problem), ormecloud.duckdns.org (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://ormecloud.duckdns.org/.well-known/acme-challenge/a2PGzSNc_u4Zr_1TIzyss0aGocG6bVQuaJzOeyjPQro: Timeout during connect (likely firewall problem)

 

 

Please can someone help my figure out what the simple issue is as a ive ploughed every forum, link and tutorial i can and im ready to call it a day and give Apple icloud money for extra storage!! I Don't want too!

 

 

Thanks in advance,


Richard

 

 

 


 

 

 

Link to comment

Ok so to help anyone out i managed to find the problem!

 

on my TP-Link router / Security tab / Remote Management tab 

 

The 'Web Management' port was set to 80 and blocking any traffic to unraid. I changed this to a different value and now i can use the 180-80 and 1443-443 port forwarding settings as described in spaceinvaderones tutorial!!

 

 

I knew it would be something simple!!!

Link to comment

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...