Jump to content
Sign in to follow this  
Dataone

[SOLVED] Can't access WebGUI after changing OS

2 posts in this topic Last Reply

Recommended Posts

Posted (edited)

I have moved from Ubuntu 18.10 to Arch and since then I can't access the WebGUI no matter what network settings I try, even though they are the exact same as my other os. I also have this problem with accessing the GUI from my phone. The only difference I can think of would be a different hostname, old os was 'Desktop', new is 'desktop', unRAID is 'tower'. But I'm not sure why that would prevent me from connecting.

 

I am on the same subnet, with the same gateway and DNS server. All docker containers are up and running perfectly, renaming media etc. I can access my media shares perfectly as well as telnet into unRAID.

 

Connecting via ip or dns name, https or http, all don't connect.

 

Here is my network.cfg:

IFNAME[0]="br0"
BRNAME[0]="br0"
BRSTP[0]="no"
BRFD[0]="0"
BRNICS[0]="eth0"
PROTOCOL[0]="ipv4+ipv6"
USE_DHCP[0]="no"
IPADDR[0]="192.168.1.101"
NETMASK[0]="255.255.255.0"
GATEWAY[0]="192.168.1.1"
DNS_SERVER1="192.168.1.1"
DNS_SERVER2="192.168.1.99"
DNS_SERVER3="1.1.1.1"
USE_DHCP6[0]="yes"
DHCP6_KEEPRESOLV="no"
SYSNICS="1"

unRAID 'ip route show':

default via 192.168.1.1 dev br0 
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 
192.168.1.0/24 dev br0 proto kernel scope link src 192.168.1.101

'route -n':

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         192.168.1.1     0.0.0.0         UG    0      0        0 br0
172.17.0.0      0.0.0.0         255.255.0.0     U     0      0        0 docker0
192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 br0

My desktop 'ip route show':

default via 192.168.1.1 dev enp3s0 proto static metric 100 
192.168.1.0/24 dev enp3s0 proto kernel scope link src 192.168.1.102 metric 100 

ifconfig: (for br0, docker, eth0)

br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.101  netmask 255.255.255.0  broadcast 0.0.0.0
        inet6 fe80::4c95:31ff:fe3d:4cc7  prefixlen 64  scopeid 0x20<link>
        inet6 2404:4408:236a:aa00:1509:ac99:5ec1:8215  prefixlen 64  scopeid 0x0<global>
        ether 9c:5c:8e:93:8b:cb  txqueuelen 1000  (Ethernet)
        RX packets 820541813  bytes 402619340055 (374.9 GiB)
        RX errors 0  dropped 106436  overruns 0  frame 0
        TX packets 1194694226  bytes 1363144801785 (1.2 TiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

docker0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 172.17.0.1  netmask 255.255.0.0  broadcast 172.17.255.255
        inet6 fe80::42:2eff:fe17:3f3e  prefixlen 64  scopeid 0x20<link>
        ether 02:42:2e:17:3f:3e  txqueuelen 0  (Ethernet)
        RX packets 909545881  bytes 1021521312878 (951.3 GiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 827668033  bytes 408534550513 (380.4 GiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth0: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST>  mtu 1500
        inet6 fe80::9e5c:8eff:fe93:8bcb  prefixlen 64  scopeid 0x20<link>
        ether 9c:5c:8e:93:8b:cb  txqueuelen 1000  (Ethernet)
        RX packets 872217122  bytes 420008831240 (391.1 GiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 1407785475  bytes 1382880782155 (1.2 TiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 20  memory 0xf7c00000-f7c20000  

I don't know much about networking, but I have a feeling broadcast shouldn't be 0.0.0.0? I've searched quite a lot on the forums and internet to no avail even though this question has been asked a lot.

 

Cheers

 

Diagnostics attached

 

tower-diagnostics-20190317-1312.zip

Edited by Dataone

Share this post


Link to post

Fixed after disabling https, even though both didn't work on arch and it did on ubuntu. Maybe bad certificates. Please mark solved

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this