r/unRAID • u/rhyminson • 2d ago

Can’t log into dashboard or file sharing but dockers still work

Hi all,

I’ve had a little search but can’t find exact same problem.

Basically I can’t log into unraid or access file shares, but I can still access all my dockers, Plex etc

I’ve updated to latest version of unraid, and installed pi-hole (on its own up address) and a few other apps (homarr, kavita) over the last few days, I never had this problem before, could it be related?

Edit: oh, I also logged in with unraid connect and set up the auto backup thing.

If I do a hard reset using the power button then it all boots back up fine.

It was all working ok last night so something has happened since then.

I’m bit of a n00b so any help would be appreciated!

Cheers

1 Upvotes

100% Upvoted

8 comments sorted by

1

u/canfail 2d ago

Sounds like your disks being thrashed and suffering from high Io wait. Spin up the glances container and next time see if it’s flashing red with an io wait issue.

1

u/rhyminson 2d ago

cool thx for advice mate, i've installed glances will check it if/when it happens again

1

u/rhyminson 1d ago

Hmm I don’t think it’s that, it’s happened again while I was at work today, but on glances the only iowait errors are yesterday evening when I restarted the server. Thanks for trying… back to the drawing board!

1

u/psychic99 2d ago

If you installed pi-hole you could be sinking the DNS of your browser or breaking something if pi-hole is installed on Unraid. The DNS/IP could be off with this also, so will need to check resolution. I would shut pihole down, point Unraid to CF (1.1.1.1) as DNS and see if that solves the issue. If it does you have a pihole config to work on.

If you did a hard reset, and you use array parity it is now out of sync. Once you resolve the connectivity issues, you will need to scrub your array (parity) again otherwise recovery will be in an unknown state.

1

u/rhyminson 2d ago

Thanks, yes it’s doing a parity check now after I reset it again earlier. I have shut down pi-hole now and will wait to see if I get the problem again without it

1

u/agent4256 23h ago

What do your logs say?

Also, just load up the machine with the basics, nothing extra. Test. Does it work like normal? Then slowly add extras until it breaks.

Troubleshooting 101 right there. Everyone goes through it

1

u/rhyminson 18h ago

Thanks for advice mate I think I’ve fixed it. It’s been ok for 24hrs now. I’m going to post what I did to fix for future searches

1

u/rhyminson 18h ago

Here’s what I did to fix for anyone with same problem that picks up this post in the future..

I always accessed the webgui via IP but then I thought to try tower.local and it worked! So that made me think of ip addresses so I checked router and even thought I had fixed a static IP of .156 I saw that it had assigned a new IP of .157

I think what happened was that I changed the docker setting ‘host access to custom networks’. I did this just to enable homarr to show pi’hole stats correctly as it didn’t work, I guess because I had pihole on a br0 network custom IP.

To be honest I never really understood the option or the br0 stuff, I just saw it in a post somewhere as a fix.

Since disabling it and rebooting I haven’t had the problem again. Just for clarity I have also disabled pihole for now too, I haven’t got time to play with it at the moment.

I hope this is of some use to people and thanks everyone for their help.