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.

Unable to access GUI after update to 6.12.1

Featured Replies

I updated from 6.11 to 6.12.1. I cannot access the GUI. I connected my server to a monitor. It boots in "headless mode" and does not let me select option for GUI. I created a diagnostic log from the command line.

 

Thank you for your help!!!

 

margate-diagnostics-20230626-1607.zip

Please provide the output of the command:

cat /etc/nginx/conf.d/servers.conf

 

  • Author

Is there something I type to capture it to a text file? I am accessing it from command line on an attached monitor, not from my computer.

You can take a photo if you want : )

 

Or you can redirect the output to the flash drive like this:

cat /etc/nginx/conf.d/servers.conf > /boot/output.txt

Then the "output.txt" file will be in the root of the flash drive

  • Author

Not sure what changed, but now I can access the GUI from my laptop!

Not sure why it boots in "headless mode" and won't give my an option for GUI mode, but I assume that is unrelated.

 

root@Margate:~# cat /etc/nginx/conf.d/servers.conf
#
# Listen on local socket for nchan publishers
#
server {
    listen unix:/var/run/nginx.socket default_server;
    location ~ /pub/(.*)$ {
        nchan_publisher;
        nchan_channel_id "$1";
        nchan_message_buffer_length $arg_buffer_length;
    }
    location ~ /nchan_stub_status$ {
        nchan_stub_status;
    }
}
#
# Always accept http requests from localhost
# ex: http://localhost
# ex: http://127.0.0.1
# ex: http://[::1]
#
server {
    listen 127.0.0.1:80; # lo
    listen 127.0.0.1:3443; # lo
    listen [::1]:80; # lo
    listen [::1]:3443; # lo
    #
    include /etc/nginx/conf.d/locations.conf;
}
#
# Port settings for http protocol
# ex: http://tower  (IP address resolved via NetBIOS)
# ex: http://tower.local (IP address resolved via mDNS)
# ex: http://192.168.1.100
# ex: http://[::ffff:192.168.1.100]
#
server {
    listen 192.168.12.143:80 default_server; # br0
    listen 10.253.0.1:80 default_server; # wg0
    listen 100.111.171.68:80 default_server; # tailscale1
    listen [fd7a:115c:a1e0:ab12:4843:cd96:626f:ab44]:80 default_server; # tailscale1
    #
    location ~ /wsproxy/80/ { return 403; }
    include /etc/nginx/conf.d/locations.conf;
}
#
# Return 404 (Not Found) as default ssl action
#
server {
    listen 192.168.12.143:3443 ssl http2 default_server; # br0
    listen 10.253.0.1:3443 ssl http2 default_server; # wg0
    listen 100.111.171.68:3443 ssl http2 default_server; # tailscale1
    listen [fd7a:115c:a1e0:ab12:4843:cd96:626f:ab44]:3443 ssl http2 default_server; # tailscale1
    # Ok to use concatenated pem files; nginx will do the right thing.
    ssl_certificate         /boot/config/ssl/certs/Margate_unraid_bundle.pem;
    ssl_certificate_key     /boot/config/ssl/certs/Margate_unraid_bundle.pem;
    ssl_trusted_certificate /boot/config/ssl/certs/Margate_unraid_bundle.pem;
    #
    # OCSP stapling
    ssl_stapling off;
    ssl_stapling_verify off;
    return 404;
}
#
# Port settings for https using CA-signed cert
# ex: https://lan-ip.hash.myunraid.net
# ex: https://hash.unraid.net
#
server {
    listen 192.168.12.143:3443 ssl http2; # br0
    listen 10.253.0.1:3443 ssl http2; # wg0
    listen 100.111.171.68:3443 ssl http2; # tailscale1
    listen [fd7a:115c:a1e0:ab12:4843:cd96:626f:ab44]:3443 ssl http2; # tailscale1
    server_name 192-168-12-143.hash.myunraid.net 10-253-0-1.hash.myunraid.net 100-111-171-68.hash.myunraid.net fd7a-115c-a1e0-ab12-4843-cd96-626f-ab44.hash.myunraid.net;
    # Ok to use concatenated pem files; nginx will do the right thing.
    ssl_certificate         /boot/config/ssl/certs/certificate_bundle.pem;
    ssl_certificate_key     /boot/config/ssl/certs/certificate_bundle.pem;
    ssl_trusted_certificate /boot/config/ssl/certs/certificate_bundle.pem;
    #
    # OCSP stapling
    ssl_stapling on;
    ssl_stapling_verify on;
    #
    location ~ /wsproxy/3443/ { return 403; }
    include /etc/nginx/conf.d/locations.conf;

4 minutes ago, ejf513 said:

Not sure what changed, but now I can access the GUI from my laptop!

 

The problem I was looking for isn't there. All good now?

  • Author

Looks good. Not sure what happened, but thank you for the help!

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.