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 GUI 403 error

Featured Replies

I have searched diligently for an answer to this problem, so please don't yell at me if this has a ridiculously easy solution.

 

I have been running an UNRAID server for several years now with relatively few problems. Recently, I've been unable to access the web configuration pages, but it hasn't worried me, since everything else seemed to work all right. I've attached a screenshot of the error response I get from it.

 

Today I noticed that my available disk space seemed to have dropped precipitously for no apparent reason, I decided to reboot the system and see if I could get things working again. I shut down via telnet, cleanly, I think. When it restarted, I still cannot access the web interface, and can find no way to start up the array without it.

 

Any information on getting the web interface back or starting the array from the command line would be greatly appreciated.

Screen_Shot_2014-08-03_at_8_03.45_PM.png.ccb3ffe161192e1a9e2d2e6e021f8472.png

See console commands in my sig. Restart and select SAFE-mode from the boot menu. Did you follow the procedure given on the console commands page to shutdown?

 

  • 2 weeks later...
  • Author

Thank you.

 

After editing my Go script with your suggestions and restarting in safe mode, I was able to access the WebGUI and found out I had a drive that had gone out. After replacing and rebuilding the drive in safe mode, I can once again access the WebGUI in standard mode.

  • Author

I finally realized what the problem was. I installed PlexConnect and re-routed emhttp to port 81.

 

Adding ":81" to the ip address in the browser clears up the problem.

 

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.