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.

Unraid management console behind nginx + authentik proxy pass openresty 500 Internal Server Error

Featured Replies

Title basically says it all. I understand opening remote access to the unraid management console is a no no but I am restricting access to it.

Everything runs as it should, nginx passes to authentik for authorization and then it loads the page, but I get a blank screen with Internal server error 500 openresty. 

My authentik install is on a separate server, but the nginx instance is running as a docker inside unraid. I have it using custom network eth0: and a static Ip and I've tried redirecting to unraid using its lan ip, using localhost and host networking, and the internal docker route to host (172.17.0.0). All result in the same error. 

  • 1 month later...

Found a solution?

  • 6 months later...

So this is my first reply but I figured out a solution to this issue.  What appears to happen is when you log into unraid, it uses a URL rewrite to the host name.  Why it happens when I have authentik setup, I really dont know... I dont have all the answers, I just have a workaround that I love.  

 

I went into unraid, management settings, then changed the Local TLD: to my domain name.  ie domain.com

My servers name is Unraid, so the Local access URLs: is now Unraid.Domain.com

 

I am using ubiquity so there is no DNS... so had to fix problem 2.  I installed a pihole but you could use the bind docker to setup a basic DNS server.  Pihole worked very smoothly for this and I wanted to build one either way.  I then went to the DNS option, and hostname is Unraid.domain.com and then obviously the local ip of my unraid server.

 

I then shut down my docker and vm services, went into the networking, changed my first DNS to the pihole, then second dns to an upstream dns server.

 

Turned on the docker services, powered on the pihole first, then powered on the rest of my Dockers to ensure they used the pihole as the primary DNS.

 

Then in NPM, I changed the forward hostname as Unraid.Domain.com. 

 

I think the main issue we are having has something to do with dockers being able to reach the hostname of the unraid server.  Its not on the docker network exactly.  Either way, this method worked very smoothly for me.  I really hope this helps. 

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...

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.