Can't access GUI (Web or direct)


Go to solution Solved by Squid,

Recommended Posts

Hey all, I can't access my unraid server GUI anymore, from the web or directly.

 

Initially i thought it was a drive issue (as I saw errors). I've now tried removing all the drives, and booting in safe mode. Neither of these helps.

 

I'm not sure what changed, as I had been away for some months and the OS stopped responding to webgui when I was away (but the docker services were still running).

 

All I get when I try to access it is (last ~50 lines of the diagnostics syslog) :

Quote

May  4 15:29:24 NAS kernel: md: import_slot: 29 missing
May  4 15:29:24 NAS emhttpd: import 30 cache device: no device
May  4 15:29:24 NAS emhttpd: import 31 cache device: no device
May  4 15:29:24 NAS emhttpd: import flash device: sda
May  4 15:29:24 NAS root: Starting apcupsd power management:  /sbin/apcupsd
May  4 15:29:24 NAS emhttpd: read SMART /dev/sda
May  4 15:29:24 NAS apcupsd[2108]: apcupsd 3.14.14 (31 May 2016) slackware startup succeeded
May  4 15:29:24 NAS apcupsd[2108]: NIS server startup succeeded
May  4 15:29:24 NAS emhttpd: Starting services...
May  4 15:29:24 NAS emhttpd: shcmd (9): /etc/rc.d/rc.samba restart
May  4 15:29:27 NAS root: Starting Samba:  /usr/sbin/smbd -D
May  4 15:29:27 NAS root:                  /usr/sbin/nmbd -D
May  4 15:29:27 NAS root:                  /usr/sbin/wsdd
May  4 15:29:27 NAS root:                  /usr/sbin/winbindd -D
May  4 15:29:27 NAS emhttpd: shcmd (13): /etc/rc.d/rc.avahidaemon start
May  4 15:29:27 NAS root: Starting Avahi mDNS/DNS-SD Daemon:  /usr/sbin/avahi-daemon -D
May  4 15:29:27 NAS avahi-daemon[2160]: Found user 'avahi' (UID 61) and group 'avahi' (GID 214).
May  4 15:29:27 NAS avahi-daemon[2160]: Successfully dropped root privileges.
May  4 15:29:27 NAS avahi-daemon[2160]: avahi-daemon 0.8 starting up.
May  4 15:29:27 NAS avahi-daemon[2160]: Successfully called chroot().
May  4 15:29:27 NAS avahi-daemon[2160]: Successfully dropped remaining capabilities.
May  4 15:29:27 NAS avahi-daemon[2160]: Loading service file /services/sftp-ssh.service.
May  4 15:29:27 NAS avahi-daemon[2160]: Loading service file /services/smb.service.
May  4 15:29:27 NAS avahi-daemon[2160]: Loading service file /services/ssh.service.
May  4 15:29:27 NAS avahi-daemon[2160]: Joining mDNS multicast group on interface br0.IPv4 with address 10.10.10.10.
May  4 15:29:27 NAS avahi-daemon[2160]: New relevant interface br0.IPv4 for mDNS.
May  4 15:29:27 NAS avahi-daemon[2160]: Joining mDNS multicast group on interface lo.IPv6 with address ::1.
May  4 15:29:27 NAS avahi-daemon[2160]: New relevant interface lo.IPv6 for mDNS.
May  4 15:29:27 NAS avahi-daemon[2160]: Joining mDNS multicast group on interface lo.IPv4 with address 127.0.0.1.
May  4 15:29:27 NAS avahi-daemon[2160]: New relevant interface lo.IPv4 for mDNS.
May  4 15:29:27 NAS avahi-daemon[2160]: Network interface enumeration completed.
May  4 15:29:27 NAS avahi-daemon[2160]: Registering new address record for 10.10.10.10 on br0.IPv4.
May  4 15:29:27 NAS avahi-daemon[2160]: Registering new address record for ::1 on lo.*.
May  4 15:29:27 NAS avahi-daemon[2160]: Registering new address record for 127.0.0.1 on lo.IPv4.
May  4 15:29:27 NAS emhttpd: shcmd (14): /etc/rc.d/rc.avahidnsconfd start
May  4 15:29:27 NAS root: Starting Avahi mDNS/DNS-SD DNS Server Configuration Daemon:  /usr/sbin/avahi-dnsconfd -D
May  4 15:29:27 NAS avahi-dnsconfd[2170]: Successfully connected to Avahi daemon.
May  4 15:29:28 NAS avahi-daemon[2160]: Server startup complete. Host name is NAS.local. Local service cookie is 3087488982.
May  4 15:29:28 NAS avahi-daemon[2160]: Service "NAS" (/services/ssh.service) successfully established.
May  4 15:29:28 NAS avahi-daemon[2160]: Service "NAS" (/services/smb.service) successfully established.
May  4 15:29:28 NAS avahi-daemon[2160]: Service "NAS" (/services/sftp-ssh.service) successfully established.
May  4 15:29:29 NAS emhttpd: stale configuration
May  4 15:29:29 NAS emhttpd: shcmd (19): /etc/rc.d/rc.php-fpm start
May  4 15:29:29 NAS root: Starting php-fpm  done
May  4 15:29:29 NAS emhttpd: shcmd (20): /etc/rc.d/rc.nginx start
May  4 15:29:29 NAS root: Starting Nginx server daemon...
May  4 15:29:29 NAS ntpd[1914]: receive: Unexpected origin timestamp 0xe61c8db9.fc417f66 does not match aorg 0000000000.00000000 from [email protected] xmt 0xe61c8db9.c3a5daf6
May  4 15:29:33 NAS login: pam_unix(login:auth): authentication failure; logname=LOGIN uid=0 euid=0 tty=tty1 ruser= rhost=  user=root
May  4 15:29:35 NAS login: FAILED LOGIN 1 FROM tty1 FOR root, Authentication failure
May  4 15:29:44 NAS login: pam_unix(login:session): session opened for user root(uid=0) by LOGIN(uid=0)
May  4 15:29:44 NAS login: ROOT LOGIN ON tty1

 

Happy to include any other files from the diagnostics if needed.

 

Thank you everyone for the assistance

 

Edit: Its on Unraid 6.9.2 if that helps

 

 

Edited by CD99
Adding Unraid version
Link to comment
  • 2 weeks later...

Mine is on 6.9.2, and this part of the guide has no actual steps for what to do if you are not on 6.10.

 

To reiterate, the GUI is not accessible via web or on the server directly. The GUI also does not load even when trying safemode. I can however get to the command line

 

Steps I've tried:

1) Loading safemode

2) Removing all drives and just booting normally, safemode, etc

3) Copying all contents to a new thumbdrive and running that

 

This issue arose when I was away, so I can't say what happened. I do have auto update for docker containers set, but if this does mess it up, I could usually use safemode to disable / remove the offending docker / app. Unfortunately, this does not work.

Link to comment
  • Solution
2 minutes ago, CD99 said:

Mine is on 6.9.2, and this part of the guide has no actual steps for what to do if you are not on 6.10.

 

Quote

Unraid 6.9

While you wait for your Internet access to be restored, access the server with this URL:

  https://<server_ip> (note: https not http) or https://<server_ip>:<https_port> (if your https port is not the default of 443)

Your browser will bring up a warning that the SSL certificate does not match the url you are tryin to visit. It is safe to ignore this warning since you are are intentionally using the wrong url.

 

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.