So I just changed my router.

The old one had a gateway of 192.168.1.1, but the newone 192.168.1.254. Otherwise everthing is about the same.

IP of the server was and still is 192.168.1.132. All my dockers work, plex, tautulli etc. (excluding nextcloud/letsencrypt)

 

So I can't access my webgui, when I enter 192.168.1.132 the url goes to  https://2b18d61e08b171a29b19d1282b7aa8ae2b4ab766.unraid.net:442/

Which it always did, or something like that at least, but now I get the error message 

This site can’t be reached

2b18d61e08b171a29b19d1282b7aa8ae2b4ab766.unraid.net’s server IP address could not be found.

 

• Try running Windows Network Diagnostics.

DNS_PROBE_FINISHED_NXDOMAIN

 

I have tried many browsers, clearing all cache but this always happen.

Does this have something to do with the lets encrypt certs?

I once had a problem with letsencrypt and my nextcloud and I couldn't run certbot renew, but it worked deleting /etc folder and restarting docker.

But I don't know what I can do for the unraid webgui

 

I have attached the tower diagnostics folder

I do have access to the server with ssh

 

Any help appreciated

tower-diagnostics-20180904-1934.zip

Edited September 4, 20187 yr by flokason

EDIT

 

got access when I entered this, so hopefully everything is alright:

 

https://192.168.1.132:442/

 

Edited September 4, 20187 yr by flokason

Very strange though
I can only access through https://192.168.1.132:442/

 

my virtual machines are missing

 

edit:

vdisk images still there so I can mount them

 

Still the issue regarding https and using 192.168.1.132 to directly access my server

 

and ofcourse nextcloud, probably same letsencrypt error

Edited September 4, 20187 yr by flokason

Hi,

One thing I do find a bit unusual is your network settings - in your diagnostics - config/network.cfg the gateway is set to be the IPADDR. I'm not sure how you had this working before but typically the GATEWAY should be your router IP.

I'd try adjusting that and see how it goes - can be done via the web gui (or from the command line you should just be able to edit the file /boot/config/network.cfg) - then reboot (or cycle network) and see if that makes it any better.

I do think you need to assess your Letsencrypt setup as  that's somehow playing a role here. Finally as the 192.168.1.254 router address is in my area associated with TELUS networking gear - I had quite the issue getting the host name to resolve after switching to Telus. Was fixed by manually adding to the routers name/route page.

Hope this is somewhat useful,

Del

Thanks for taking a look,

 

This resulted since I had the older router fix the IP to 192.168.1.132, and the newer one is rather simple (its from my ISP)

So I had to manually set the IP address in the unraid server to get this IP, as I use it in my config documents, I rather have it at this IP.

 

So when changing from DHCP to static, I did this mistake.

I have fixed that, then my fixcommon problems told me to add a DNS, and now my network config file looks like this:
 

# Generated settings:
IFNAME[0]="br0"
BONDNAME[0]="bond0"
BONDING_MIIMON[0]="100"
BRNAME[0]="br0"
BRSTP[0]="no"
BRFD[0]="0"
BONDING_MODE[0]="1"
BONDNICS[0]="eth0"
BRNICS[0]="bond0"
PROTOCOL[0]="ipv4"
USE_DHCP[0]="no"
IPADDR[0]="192.168.1.132"
NETMASK[0]="255.255.255.0"
GATEWAY[0]="192.168.1.254"
DNS_SERVER1="8.8.8.8"
DNS_SERVER2="8.8.4.4"
USE_DHCP6[0]="yes"
DHCP6_KEEPRESOLV="no"
SYSNICS="1"

I gave up, I think that router was crap, so I turned it in

Back with using my ISP old router as modem for my VDSL and Unifi USG as a router

You might need to config that router  to allow DNS passthrough for provisioning.  If you go to    Settings   >>>   Identification    >>>  Management Access   and turn on the    Help      function.  Now look at the help at the bottom of the page for instructions for several popular makes.    Before is a post into a thread--- a portion of which was devoted  to this problem:

 

      https://forums.unraid.net/topic/61265-what-router-are-you-running/?page=3&tab=comments#comment-637221

 

 

I have selected this particular post because you mention the Unifi USG.   Most of the inexpensive consumer routers do not provide this protection and allow the redirection of DNS which, as I understand it, is a security hazard.