Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Web Interface becomes unavailable after 2-4 days

Featured Replies

Been running unRAID 5.0.4 for a couple of months, and I've always had this wierd issue. 2-4 days after a restart the web interface becomes completely unavailable, but a reboot fixes it. Not something I want to be doing every couple of weeks since my fileserver is pretty much serving up files through Plex and FTP 24/7/365.

 

I´m also running unMenu and that keeps on responding on :8080 just fine for weeks and months.

 

I´m a bit lost - What's the first thing I should take a look at?

Are you running any plugins? Some have been know to cause issues with the web browser. When this happens, try connecting to the web interface with a different browser?

 

The next time it happens, post a syslog. Also, go to console or telnet and

ps aux | grep emhttp

You should get a line like

root      2697  0.0  0.0  89128  3464 ?        Sl  Sep05  0:18 /usr/local/sbin/emhttp

If you don't then the web interface is not running anymore. Most likely got killed because other processes needed more memory. You might try searching the forums for "oom adjust".

 

  • Author

This is the output:

 

root    30242  0.0  0.0  2204  640 pts/0    S+  22:41  0:00 grep emhttp

 

I'm pretty much not running any plugins beside unMenu and some minor email notification scripts configured for alerts. My Hyper-V cluster handles everything else, the unRaid machine is just a fileserver. It's nothing special, C2Q LGA775 setup, but 8GB of DDR3 should be enough for a basic FS role?

 

I'd be surprised if it were running out of mem.

That line is just the result of running the command I gave you. It shows that command is a running process with the characters "emhttp" in it. So there is not another line? That means the web interface is not running.

 

emhttp getting "OOMed" has been a pretty common problem over the years. Search the forum for "oom adjust" for a possible workaround.

 

Also see here for an important hint about searching.

  • Author

No, nothing underneath that line. I´ll look into the oom adjust and see where it gets me, thx.

I have this exact same issue.  Please let me know if you find a fix.

 

 

I have this same issue.  I'm searching for possible answers as well.

Archived

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

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.